Skip to content

Add broader client onboarding recipes beyond Claude and Codex #4

@AlainDor

Description

@AlainDor

Context

Claude and Codex are the first supported adapter surfaces. External users will still ask how Mimir fits with other local agent/MCP clients such as Cursor, VS Code, Windsurf, and future MCP-capable tools.

Scope

Add a public onboarding matrix that distinguishes supported, experimental, and out-of-scope clients. For each supported/experimental path, show install verification commands and the relevant librarian boundary.

Acceptance Criteria

  • Docs explain the supported status of Claude, Codex, MCP stdio, and any additional clients without overstating support.
  • Each recipe includes mimir doctor and the relevant mimir setup-agent doctor or MCP verification command.
  • Unsupported clients are clearly marked as not yet supported instead of silently implied.
  • No recipe bypasses governed draft submission or canonical write validation.

Guardrails

This should not weaken the adapter-mediated-agent invariant. New client support must enter through explicit adapters, MCP, or setup artifacts, never raw canonical writes.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationenhancementNew feature or requesthelp wantedExtra attention is needed

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions