# Compatibility Acceptance DotAIOS supports agent hosts, not every model or chat product. A support claim must identify the host that reads local files or invokes the MCP server. ## Evidence levels Every client is measured at four separate levels: 1. **Configured:** DotAIOS wrote, linked, or printed the expected client files. 2. **Discoverable:** the client's current official documentation says it can discover that path or MCP server. 3. **Invoked:** the bounded probe launched the client process. The process may still fail because of authentication, entitlement, or another client error. 4. **Produced:** the client returned the unique marker from the generated context, linked skill, or deterministic MCP tool result. Configured is never a synonym for produced. Public support requires a reproducible receipt with `produced=yes`. Manual file upload or pasted text is reported as manual context supplied, never connected. ## Release tiers ### Tier 1: native context, release-tested These hosts have first-class DotAIOS context paths. A release may name them as tested only when the current release has a fresh invocation receipt. | Host | Configured surface | Discoverability check | Invocation check | |---|---|---|---| | Claude Code | `~/.claude/CLAUDE.md`, global and project skill links | Start a fresh session and confirm `/context` lists `~/.claude/CLAUDE.md`, then confirm its managed block names the AIOS folder | Run `dotaios skills probe --client claude-code --run --json`; pass only when `produced=yes` | | Codex | `~/.codex/AGENTS.md`, `.agents/skills` | Start from a disposable project and inspect the loaded instruction chain | Run `dotaios skills probe --client codex --run --json`; pass only when `produced=yes` | | Cursor | Project `AGENTS.md`, project skill links | Open the attached project and confirm the root instructions are active | Ask a fresh project agent to return a disposable marker; preserve the transcript or screenshot | The bridge points at the AIOS folder and does not import it, so `~/aios/AGENTS.md` is deliberately absent from `/context`. Its presence there would mean the host had expanded an `@` reference and loaded the whole folder into every session, which is the condition this check exists to rule out — not evidence of a pass. The live probe requires the relevant client to be installed and authenticated. An authentication or entitlement failure is a limitation receipt, not a pass. ### Tier 2: documented adapter, receipt required These hosts have a documented path, but DotAIOS does not yet claim the same automated invocation coverage as Tier 1. | Host | Adapter | Required acceptance evidence | |---|---|---| | Gemini CLI | `~/.gemini/GEMINI.md`, `.agents/skills` | Google ended Gemini Code Assist for individual accounts, so the CLI exits with `IneligibleTierError` and cannot produce a receipt on such an account. Re-test only on an account that still has access. | | Antigravity IDE | Global skills under `~/.gemini/config/skills`, project skills under `.agents/skills`; optional MCP in `~/.gemini/config/mcp_config.json` | Confirm the skill or MCP server appears, then return a unique skill marker or deterministic `read_working_context` value | | Hermes | Global `skills.external_dirs` in `~/.hermes/config.yaml`; no bundled project target | Invoke a disposable global skill only after a safe bounded host mode exists; until then keep invocation and production unverified | | Kimi Code CLI | Shared `~/.agents/skills`; optional MCP in `~/.kimi-code/mcp.json` | Confirm a DotAIOS skill or the `dotaios` MCP server appears, then invoke one and preserve the output | | OpenCode | Shared `~/.agents/skills`; optional MCP at `mcp.dotaios` in `~/.config/opencode/opencode.json` | Confirm the skill or MCP server appears, invoke one deterministic DotAIOS capability, and preserve the output | Hermes project-local configuration is not a Tier 2 surface. Hermes reads `$HERMES_HOME/config.yaml`, while `dotaios attach` does not set that selector or install a launcher. A checkout-local file is therefore not discovery evidence. Re-entry requires an owned selector contract, a version/capability policy for relative path semantics, a safe host mode that does not auto-bypass approvals, a bounded receipt that proves the selected host loaded and invoked the expected skill, and one resolver shared by production attachment, health inspection, and the probe. Do not remove the `Gemini` entry from `packages/core/src/agents.json` as part of demoting Gemini CLI. Antigravity carries `bridge: null` and receives its context only because that entry writes `~/.gemini/GEMINI.md`, which is Antigravity's own documented global rules file. Deleting the entry would silently strip Antigravity's entire context layer. Antigravity's current documentation publishes exactly two skill discovery paths — workspace `/.agents/skills/` and global `~/.gemini/config/skills/` — and DotAIOS writes both. Older notes here claimed the IDE read `~/.gemini/antigravity/skills` and treated `~/.gemini/config/skills` as an Antigravity 2.0-only root; that was wrong, and skills projected to the former reached nothing. Separately versioned surfaces such as the CLI (`~/.gemini/antigravity-cli/skills`) are still uncovered. Promoting Antigravity to Tier 1 requires confirming the roots the installed version actually reads and adding an invocation probe; none exists today. The MCP path is unresolved for the same reason. `dotaios mcp install --dry-run --agent antigravity` prints `~/.gemini/config/mcp_config.json`, which is what this table and `docs/mcp.md` state. On at least one machine running the IDE surface that file is empty and the runtime instead reads `~/.gemini/antigravity/mcp_config.json`. Confirm which one your installed version reads before relying on either. Do not change the printed path without evidence from more than one machine. Use `dotaios mcp install --dry-run --agent ` for the client-specific MCP fragment, including OpenCode. The command does not edit client configuration. `dotaios connect opencode --dry-run` previews the managed OpenCode setup instead. ### Manual context only Ordinary ChatGPT, Claude, Gemini, Kimi, or other browser chats cannot read a local `~/aios` folder by themselves. Generate `dotaios brief --compact`, attach or paste it, and label the result manual context supplied. A hosted product with an explicitly configured remote connector is a different integration and must be tested under that connector's own security and approval model. The local stdio adapter is not remotely reachable. ### Model through host only Kimi K2, Kimi K3, and Z.ai GLM are models, not shared-context integration surfaces by themselves. Moonshot AI or Kimi and Z.ai are providers. Name the compatible host that runs the model, such as Kimi Code CLI, Claude Code, Cline, Hermes, or OpenCode. Do not claim native K3, Z.ai, or GLM support without a tested host-level path. ## Release gate For every client named in launch copy: 1. Record the client version and operating system. 2. Record configured paths or the MCP configuration hash. 3. Link the official documentation that establishes discoverability. 4. Run a fresh unique-marker or deterministic-tool invocation. 5. Store the receipt with `configured`, `discoverable`, `invoked`, and `produced` separate. 6. Downgrade the public claim when `produced=yes` cannot be reproduced. Official sources, last reviewed 2026-07-28: - Claude Code memory, skills, and MCP: , , and - Codex instructions, skills, and MCP: , , and - Gemini CLI context, skills, and MCP: , , and - Cursor rules, skills, and MCP: , , and - Antigravity IDE skills and MCP: and - Kimi Code CLI instructions, skills, and MCP: , , and - OpenCode skills and MCP: and - Kimi K3 and Z.ai provider-through-host evidence: and