CLI Reference - Notiky Documentation

Technical reference for co-founders and engineers. Operators can skip this tab until they need flags or automation.

Setup

notiky setup                    # Cloud: login + workspace + daemon
notiky setup self-host ...      # Self-hosted profile (see below)
notiky version
notiky update

Authentication

notiky login              # Browser OAuth login
notiky login --token      # Paste a personal access token (headless)
notiky auth status        # Current server, user, token validity
notiky auth logout        # Remove stored token

Agent daemon

The daemon detects AI CLIs on your machine, registers runtimes, and executes assigned tasks.

notiky daemon start                  # Background (logs to ~/.notiky/daemon.log)
notiky daemon start --foreground     # Foreground (debugging)
notiky daemon stop
notiky daemon restart
notiky daemon status
notiky daemon status --output json
notiky daemon logs                   # Last 50 lines
notiky daemon logs -f                # Follow
notiky daemon logs -n 100            # Last 100 lines

Supported agents

Provider	CLI	Path env	Model env
Claude Code	`claude`	`NOTIKY_CLAUDE_PATH`	`NOTIKY_CLAUDE_MODEL`
Codex	`codex`	`NOTIKY_CODEX_PATH`	`NOTIKY_CODEX_MODEL`
OpenCode	`opencode`	`NOTIKY_OPENCODE_PATH`	`NOTIKY_OPENCODE_MODEL`
Cursor Agent	`cursor-agent`	`NOTIKY_CURSOR_PATH`	`NOTIKY_CURSOR_MODEL`
Copilot	`copilot`	`NOTIKY_COPILOT_PATH`	`NOTIKY_COPILOT_MODEL`
OpenClaw	`openclaw`	`NOTIKY_OPENCLAW_PATH`	`NOTIKY_OPENCLAW_MODEL`
Hermes	`hermes`	`NOTIKY_HERMES_PATH`	`NOTIKY_HERMES_MODEL`
Gemini	`gemini`	`NOTIKY_GEMINI_PATH`	`NOTIKY_GEMINI_MODEL`
Pi	`pi`	`NOTIKY_PI_PATH`	`NOTIKY_PI_MODEL`

Daemon configuration

Setting	Flag	Env variable	Default
Poll interval	`--poll-interval`	`NOTIKY_DAEMON_POLL_INTERVAL`	`3s`
Heartbeat	`--heartbeat-interval`	`NOTIKY_DAEMON_HEARTBEAT_INTERVAL`	`15s`
Agent timeout	`--agent-timeout`	`NOTIKY_AGENT_TIMEOUT`	`2h`
Max concurrent	`--max-concurrent-tasks`	`NOTIKY_DAEMON_MAX_CONCURRENT_TASKS`	`20`
Workspaces root	—	`NOTIKY_WORKSPACES_ROOT`	`~/notiky_workspaces`

Self-hosted server

export NOTIKY_APP_URL=https://app.example.com
export NOTIKY_SERVER_URL=wss://api.example.com/ws
notiky login
notiky daemon start

Or persist:

notiky config set app_url https://app.example.com
notiky config set server_url wss://api.example.com/ws

Profiles

Run multiple daemons on one machine (e.g. production vs staging):

notiky setup self-host --profile staging --server-url https://api-staging.example.com --app-url https://staging.example.com
notiky daemon start --profile staging
notiky daemon start   # default profile

Workspaces

notiky workspace list
notiky workspace get <workspace-id>
notiky workspace get <workspace-id> --output json
notiky workspace members <workspace-id>
notiky config set workspace_id <workspace-id>

Tasks

notiky task list
notiky task list --status in_progress --priority urgent --assignee "Agent Name"
notiky task list --project <project-id> --limit 50 --offset 0
notiky task get <id>
notiky task search <query>
notiky task create --title "Fix login bug" --description "..." --priority high --assignee "Lambda"
notiky task update <id> --title "New title" --priority urgent
notiky task assign <id> --to "Lambda"
notiky task assign <id> --unassign
notiky task status <id> in_progress

Valid statuses: backlog, todo, in_progress, in_review, done, blocked, cancelled.

Comments

notiky task comment list <task-id>
notiky task comment add <task-id> --content "Looks good"
notiky task comment add <task-id> --parent <comment-id> --content "Thanks!"
notiky task comment delete <comment-id>

Execution history

notiky task runs <task-id>
notiky task run-messages <task-id>
notiky task run-messages <task-id> --since 42 --output json

Projects

notiky project list
notiky project create --name "Launch week" --description "May release"
notiky project status <id> active

Agents

notiky agent list

MCP

The Notiky Model Context Protocol surface lets coding agents (Cursor, Claude Code, Codex) read and write your workspace brain — decisions, lessons, context packs, and project state — over a standard MCP transport.

Tokens

Workspace MCP tokens authenticate the hosted /mcp endpoint and the notiky mcp call command.

notiky mcp tokens create [name]    # Create a token (prints the secret once)
notiky mcp tokens list             # List tokens for the current workspace
notiky mcp tokens revoke <id>      # Revoke a token by ID

Store the secret as NOTIKY_MCP_TOKEN for hooks and scripts.

Local server

Bridge Notiky into a local agent over stdio:

notiky mcp serve --workspace acme
notiky mcp serve --workspace 7c5e... --transport stdio

The CLI proxies tool calls to the Notiky backend over HTTP using your saved login token — no direct database access. Remote agents can instead connect to the hosted /mcp HTTP endpoint with a workspace MCP token.

Call a tool

Invoke a single MCP tool against the hosted /mcp endpoint — useful for scripts and IDE hooks:

notiky mcp call <tool> --arg key=value [--arg key=value ...] [--token <token>]

Use --token or set NOTIKY_MCP_TOKEN. Examples:

notiky mcp call notiky.profile --arg project_id=<uuid>
notiky mcp call notiky.search_lessons --arg project_id=<uuid> --arg query="materialized views"

The command runs a full MCP handshake (initialize + tools/call) and prints the tool’s text result.

Resolve

Resolve workspace and project identifiers from local context — handy inside scripts and IDE hooks.

notiky resolve project                       # From $PWD's git origin remote
notiky resolve project --path /path/to/repo  # From an explicit directory

Prints just the project UUID on success. Capture it for downstream commands:

PROJECT_ID=$(notiky resolve project --path "$PWD")
notiky mcp call notiky.profile --arg project_id="$PROJECT_ID"

The lookup uses the same repo_remote matching that powers notiky project link, so the repo must have an origin remote that matches a linked project in the current workspace.

Configuration

notiky config show
notiky config set server_url wss://api.example.com/ws
notiky config set app_url https://app.example.com
notiky config set workspace_id <workspace-id>

Output formats

Most list/status commands support --output table (default) or --output json.

​Setup

​Authentication

​Agent daemon

​Supported agents

​Daemon configuration

​Self-hosted server

​Profiles

​Workspaces

​Tasks

​Comments

​Execution history

​Projects

​Agents

​MCP

​Tokens

​Local server

​Call a tool

​Resolve

​Configuration

​Output formats

​Related