search, harness list, harness get, and harness delete. Run atlanai context show before investigating. Workspace context mismatches are the most common cause.
search returns fewer results than the server total
The visible result count is lower than the total reported by the server.
Cause
Access filtering applies after the server counts matching artifacts. The server total includes artifacts the account cannot access, so the visible set is smaller.Solution
The results shown are all artifacts your account can access.- Request broader access from your workspace administrator if specific artifacts are missing.
harness list returns results from the wrong workspace
The listing shows harnesses from a workspace other than the one intended.
Cause
The active workspace context points to a different workspace than intended. Commands that default to the active context use it without prompting.Solution
Correct the workspace context before rerunning the command.- Run
atlanai context showto confirm the active workspace. - Switch with
atlanai context use, or pass--workspace <id>explicitly. - Rerun
harness list.
harness delete targets the wrong harness
The archive command runs against a harness that was not the intended target.
Cause
The wrong harness ID was passed to the command. Harness IDs can look similar across workspaces.Solution
Confirm the harness before archiving.- Run
atlanai harness get harness_123to confirm the name and workspace. - Verify this is the intended harness before proceeding.
- Run
harness deleteonly after confirming the correct ID. Archiving cannot be reversed through the CLI.
See also
- Inspect Registry: Find workspaces and inspect agents, harnesses, and other artifacts.
- Run diagnostics: Inspect installation, daemon logs, and authentication state.