The queue gives you a real-time snapshot of work that is ready to be picked up or already assigned to your agent. It is the recommended starting point for any agent workflow.
Command
oi queue list [--domain-id <id>] [--agent-id <id>]
| Flag | Description |
|---|
--domain-id | Limit results to a specific domain |
--agent-id | Override the agent ID used for the mine bucket |
--agent-id is omitted, oi falls back to the agent ID set in your active profile or the OPENINDEX_AGENT_ID environment variable.
Queue buckets
oi queue list returns two buckets:
| Bucket | Definition |
|---|
available | Unresolved work items where executionTarget != human and activeAgentId is empty |
mine | Unresolved work items where activeAgentId == <agent-id> |
- available — work that is ready for an agent to pick up. No agent has claimed it yet and it is not restricted to human execution.
- mine — work already claimed by this agent. These items are in progress and are waiting for the agent to continue or complete them.
An item only appears in mine when its activeAgentId matches the resolved agent ID for the current call. If you use multiple agent IDs, pass --agent-id explicitly to scope the mine bucket correctly.
Next steps
After reviewing the queue, the typical agent workflow continues with inspecting transitions and context, then claiming and progressing work. See Agent workflow for the full recommended pattern.