jackin status
Show a fleet overview — workspaces, instances, and agents
Synopsis
jackin status [WORKSPACE [INSTANCE_ID]] [OPTIONS]Three-level fleet overview. Each level reveals more detail; the default view always fits one screen.
jackin ps is an alias for jackin status.
Levels
Level 0 — workspace summary
jackin statusOne row per workspace. Shows instance count and running/stopped state. No branch, PR, or agent detail at this level.
jackin'
fleet status
workspace instances state
──────────────────────────────────────────────────
myproj 3 3 running
backend-api 2 2 running
infra-tools 3 2 running · 1 stopped
3 workspaces · 7 instances running · 1 stopped
jackin status <workspace> show instances
jackin status <workspace> <id> show full detail
jackin status --detail include per-instance agent countsLevel 1 — instance list
jackin status <WORKSPACE>One row per instance in the workspace. Shows role, state, and PR number.
myproj 3 instances · 2 running
instance role state uptime pr
─────────────────────────────────────────────────────────
jk-k7p9m2xq the-architect running 2h 14m #142
jk-x3n1q8vz agent-smith running 47m #138
jk-p2q8r5v agent-smith stopped — —Level 2 — instance detail
jackin status <WORKSPACE> <INSTANCE_ID>Full detail for one instance: branch, PR, CI status, and the per-agent codename table.
jk-k7p9m2xq myproj / the-architect running
branch feat/auth-refactor
pr #142 Refactor JWT authentication layer
url https://github.com/acme/myproj/pull/142
ci ✓ passing
codename agent provider started exited status
───────────────────────────────────────────────────────────────
badger claude anthropic 10:15:02 — active
falcon claude anthropic 10:32:15 — activeAgent data comes from jackin-capsule agents inside the running container. Stopped instances show agents —. Instances whose capsule socket is not yet reachable show agents pending.
Options
| Option | Description |
|---|---|
--detail | At Level 0, adds an agent-count column by querying each running container (adds latency proportional to fleet size). At Level 1, adds the full per-agent table rows. |
--state <running|stopped> | Filter by instance state at any level. |
--filter <KEY=VALUE> | Filter by agent type at any level (e.g. --filter agent=claude). |
--format <human|json> | Output format. json is always fully expanded regardless of level. |
--debug | Enable diagnostic tracing. |
JSON output
--format json always returns the complete workspace → instance → agent tree regardless of which level was requested:
{
"schema_version": "v1",
"workspaces": [
{
"workspace": "myproj",
"instances": [
{
"instance_id": "jk-k7p9m2xq",
"role": "the-architect",
"state": "running",
"branch": "feat/auth-refactor",
"pull_request": {
"number": 142,
"title": "Refactor JWT authentication layer",
"url": "https://github.com/acme/myproj/pull/142",
"ci_status": "passing",
"ci_failing_check": null
},
"agents": [
{"codename": "badger", "agent": "claude", "provider": "anthropic",
"started_at": "2026-06-04T10:15:02Z", "exited_at": null,
"status": "active", "is_self": false}
]
}
]
}
]
}Examples
# Fleet summary
jackin status
# Instances in a workspace
jackin status myproj
# Full detail for one instance
jackin status myproj jk-k7p9m2xq
# Include agent counts at Level 0
jackin status --detail
# Filter running instances only
jackin status --state running
# Machine-readable fleet snapshot
jackin status --format json | jq '.workspaces[].instances[].state'Related
jackin load— launch an agent into an isolated containerjackin doctor— run pre-flight health checks- Parallel agent coordination — how agents use codenames to self-organise