Skip to main content

CLI

The day-to-day Agent Tick commands are status-update, steering, and sanction. Use install when you want Agent Tick to configure supported local coding-agent integrations; use config when you only need to save or inspect the server URL and agent_... token.

Examples use the agent-tick binary. If it is not on your PATH, run one-off commands with npx @self-deprecated/agent-tick <command> or install the package globally first.

Configuration​

Primary hosted setup is the prompt-based skill from Quick Start. Manual configuration:

npx @self-deprecated/agent-tick install

Sign in and save a local token without installing hooks:

npx @self-deprecated/agent-tick login

For self-hosted servers or CI, create an Agent Token in the Personal Console and save it locally. Use config show to inspect the saved server and masked token:

agent-tick config --server https://tick.example.com --token agent_...
agent-tick config show

Status updates​

Send non-blocking progress:

agent-tick status-update --state working --next "Run tests" "Finished edits; validating now"

Recommended states: working, waiting, blocked, done, failed. Use --notify and --importance only when the update should be eligible for future push behavior.

Steering​

Ask a human to choose from bounded options:

agent-tick steering \
  --title "Which rollout?" \
  --choice canary="Canary" \
  --choice blue_green="Blue/green" \
  --choice cancel:deny="Cancel"

Steering is bounded input: Agent Tick returns only one of the choices supplied by the caller. Include a deny/escape option when a bad state is possible.

Choice flags add mobile-visible cues:

agent-tick steering \
  --title "Which fix?" \
  --choice small="Small targeted fix" \
  --choice rewrite="Rewrite subsystem" \
  --choice stop:deny="Stop" \
  --choice-flag small=favorite

Sanctions​

Create a Sanction Request before a specific action. This records the command as reviewer context and does not run it:

agent-tick sanction \
  --title "Run migration?" \
  --body "Run the migration against the staging database." \
  --command "./migrate-staging.sh"

Include a local command in the Sanction Request by putting the command after --:

agent-tick sanction --title "Run migration?" -- ./migrate-staging.sh

Authorized actions execute locally in the agent environment, not on Agent Tick servers or phones.

MCP adapter​

Run the local stdio MCP adapter from an MCP-capable agent configuration:

agent-tick mcp

The adapter uses the same saved CLI config/token and exposes Agent Tick tools for status updates, steering, and sanctions.

Resolve a pending Request​

If a local caller created a Request it no longer needs, resolve it by ID:

agent-tick abandon req_123