Workspace context
Workspace context
Prompt-first procedure: Describe the outcome you want in your agent conversation. The agent should select and load the appropriate AIWG assets, explain material changes, request any needed approval, and report verification evidence. Exact commands and flags appear only in the CLI reference.
AIWG uses `WORKSPACE.md` as the canonical, provider-neutral project context. Put concise project conventions and links in its marked Project Context section. Keep detailed policies, runbooks, hooks, and quickrefs in linked files. Do not place credential values in context files.
The load order is:
1. provider/system/organization instructions; 2. root `WORKSPACE.md`; 3. generated `AIWG.md` discovery and routing; 4. linked or provider-native subtree files within their declared scope.
the agent-owned init operation, the agent-owned new operation, the agent-owned use operation, the agent-owned refresh operation, and the agent-owned regenerate operation maintain the graph through one implementation. the agent-owned doctor operation reports missing links, loops, duplicate or conflicting directives, possible credentials, registration errors, and managed-bootstrap drift.
Existing projects
Legacy `CLAUDE.md`, `AGENTS.md`, `AGENTS.override.md`, `WARP.md`, `.hermes.md`, and Copilot layouts remain supported. Migration is explicit:
Use AIWG to complete this documented outcome: Legacy CLAUDE.md, AGENTS.md, AGENTS.override.md, WARP.md, .hermes.md, and Copilot layouts remain supported. Migration is explicit
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.The linked regenerate branch combines that adoption with deterministic project extraction and generated context in one transaction:
Use AIWG to complete this documented outcome: The linked regenerate branch combines that adoption with deterministic project extraction and generated context in one transaction
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.It extracts only stable local evidence (package metadata, README purpose, toolchain files, standard commands, test/architecture paths, and CI workflow names) into a replaceable managed block inside the protected operator region. Manual content around that block is preserved.
Audit reports exact duplicates separately from ambiguous positive/negative conflicts and identifies root versus nested scope. Apply refuses possible credential values and unresolved conflicts by default. Provider-only material moves to `.aiwg/context/providers/` with source path and checksum attribution. Transactions and recoverable preimages live under `.aiwg/context-migrations/`. Reapplying a completed migration is a no-op.
Provider loading contract
| Surface | Mechanism | Result |
|---|---|---|
| Claude Code | native `@WORKSPACE.md`, then `@AIWG.md` | supported |
| Codex | `AGENTS.md` explicit read directive; native root-to-CWD hierarchy remains | supported |
| GitHub Copilot CLI | native `@` imports in repository instructions | supported |
| Cursor | explicit directive in `AGENTS.md`; provider rules retain native scope | supported |
| Factory | explicit directive in hierarchical `AGENTS.md` | supported |
| OpenCode | `opencode.json` `instructions` registration | supported |
| Warp | explicit directive in `WARP.md`/`AGENTS.md`; nested rules retained | supported |
| Windsurf / Devin surfaces | explicit `AGENTS.md` direction; native `.windsurf`/`.devin` rules retained | degraded pending a verified include primitive |
| Hermes | `.hermes.md`/`AGENTS.md` direction plus on-demand AIWG MCP reading | degraded |
| OpenHuman | host-dependent `AGENTS.md` direction | degraded |
| OpenClaw | no verified project-local startup loader | degraded, no automatic claim |
The authoritative dated details and source URLs live in the provider definition registry. A plain Markdown link is never presented as automatic loading.