What to work on now
AWR indexes project Markdown / YAML into queryable state. This page shows work in progress, ready to claim, waiting, and blocked.
This viewer does not edit authoritative sources or advance work status. It is not an agent client or a replacement for CLI or MCP.
Queues
AWR groups work into four queues: current means someone is working on it; ready means prerequisites are satisfied; waiting means a reply or prerequisite is pending; blocked means work cannot proceed. Start with blocked and waiting to find what is holding up progress.
Structural gaps
These are missing goals, plans, or work structures in the sources. Completing the source definitions allows AWR to reassess which work is ready.
Runtime operations to inspect
These operations were interrupted and their outcomes are unknown. AWR neither guesses nor retries automatically. Use awr recovery inspect to inspect the outcome before proceeding.
Active sessions
These are conversations the runtime currently has open. Each row is one AWR session, not a host chat id. Packaged 0.4.0 hides this panel when the command is unsupported.
Recent events
Append-only history from awr event history. Summaries only; full payloads stay behind event show. The panel is hidden when the command is unsupported.
Connection
This viewer runs an awr command for each action rather than reading the database directly. Copy any displayed command into a terminal to inspect the same result. Agents access the same state through MCP.
awr-mcp --project …
These five agent-facing read tools use disposable in-memory snapshots without changing persisted project state.
Raw JSON (inspect field mappings here)
Work items
Select a row to inspect its goal, acceptance criteria, and blockers. State comes from indexed sources, not a separate task system.
List
| Work | Title | Queues | Source status | Owner | Claim | Diagnostic codes | Revision |
|---|
Details
Acceptance criteria are copied verbatim from sources. Completion binds every criterion to supporting evidence, so paraphrasing would break that correspondence.
Raw JSON
Compile a context packet
Choose a work item and budget. AWR collects the required rules, acceptance criteria, blockers, and source quotations into a bounded packet for the agent.
Parameters
Match CLI optionsThese four parameters map to awr context compile; the command below updates as you type. work selects the task; goal selects its goal, with the project default when empty; budget limits rendered tokens and must fit required content; intent describes what you plan to do.
Packet size
All three values come from this compilation: required content cannot be omitted, included content is what the agent will read, and the budget is your limit. When included content approaches the limit, check the completeness panel for omissions.
Packet contents
Completeness
The token budget is a hard limit. AWR reports omitted optional source quotations. Incomplete required facts need resolution before the agent proceeds; a larger budget only resolves budget-related gaps.
Rendered packet
The complete context the agent will readRaw JSON
Team Web collaboration loop
My Projects → parallel overview, cards/list and detail. Cookie web entry (not bearer-in-page). Shared server facts, authz and idempotent receipts with CLI/MCP.
Raw JSON
Mainline navigation
Read-only scope, cross-dependencies, accounting, blockers and concrete outcome edges. Team Web writes are available in the Team Web view (WS-044).
Scope selectors
Read-only entryAccounting & blockers
Mainline graph
Edges are concrete task outcomesAgent guidance
Compatible short guidanceRaw JSON
Sources
Project sources that AWR treats as authoritative. Freshness other than fresh means the source changed after indexing. Reindex before relying on the stale projection.
Files
| Path | Domain | Role | Freshness | Revision |
|---|
awr intake inspect --json
Status definitions
- fresh
- The source is indexed and has not changed since. This is the normal state.
- stale
- The file changed after indexing. The projection is stale, and reads may return
SourceStale。 - Domain
- Sources are grouped by purpose: goal, plan, rules, and work ledger.
- Role
- A domain can have multiple sources;
primaryidentifies the primary one. - Sources rejected by rules
- A common cause is a suspected credential value. Expand the row for its location and repair guidance. AWR never echoes the matched value.