# ivar

> ivar mounts the repos your feature spans into one directory — real git worktrees on the same branch, opened by one Claude Code, OpenCode or OMP session. Single Rust binary, local-only.

## Overview

- [Changelog](https://ivar.run/docs/changelog.mdx): Recent ivar releases. The full history is on GitHub.
- [Quickstart](https://ivar.run/docs/quickstart.mdx): Install ivar, create a hall, explore it in a discovery session, and deliver a first feature from Claude Code, OpenCode or OMP.
- [What is ivar](https://ivar.run/docs/what-is-ivar.mdx): The idea behind ivar — a hall of real git worktrees, one view directory per feature, and one agent session across every repo a change touches.

## Guide

- [Review and delivery](https://ivar.run/docs/guide/delivery.mdx): Read the change across repos in one workspace, then push it or land it — preview first, apply against the fingerprint you reviewed.
- [Discovery](https://ivar.run/docs/guide/discovery.mdx): Understand the problem before committing to a change — a read-only session that can graduate into a feature, once and only deliberately.
- [Execution](https://ivar.run/docs/guide/execution.mdx): Run an approved Plan through a provider-native coordinator while Ivar records a durable, provider-neutral Run Receipt.
- [Features and scope](https://ivar.run/docs/guide/features.mdx): Create the feature a change belongs to, see which repos are writable, and promote another one the moment the work reaches further than you thought.
- [Code graph](https://ivar.run/docs/guide/graph.mdx): Index every repo in the hall into one local graph, and let agents ask it for source, callers and blast radius instead of grepping and reading file by file.
- [Write guards](https://ivar.run/docs/guide/guards.mdx): How ivar enforces read-only boundaries across repos — the filesystem layer, the tool guard decision, and per-provider wiring.
- [Hall upkeep](https://ivar.run/docs/guide/hall-upkeep.mdx): Keeping the hall honest from inside the harness — reconciling against ivar.json, listing what is registered, and authoring the setup script a fresh worktree needs.
- [Planning](https://ivar.run/docs/guide/planning.mdx): The three approval gates and the stable R-*, N-* and OP-* identifiers that make an approved Plan a checkable execution boundary.
- [Sessions](https://ivar.run/docs/guide/sessions.mdx): The commands that open, reattach to and close the directory your agent works in — and the guard that decides what it can write.
- [Overview](https://ivar.run/docs/guide/mcp.mdx): Declare MCP servers once in your hall manifest, sync configs across all coding agent providers, and manage authentication workflows cleanly.
- [Authentication](https://ivar.run/docs/guide/mcp/oauth.mdx): Complete end-to-end guide to MCP OAuth authentication, credential separation, provider flows, and token lifecycle across Claude Code, OpenCode, and OMP.
- [Figma](https://ivar.run/docs/guide/mcp/integrations/figma.mdx): Adding Figma MCP to ivar.json, authenticating across providers, and handling allowlist requirements.
- [Linear](https://ivar.run/docs/guide/mcp/integrations/linear.mdx): Configure the canonical Linear MCP server in ivar.json, synchronize provider configurations, and authenticate via public-client Dynamic Client Registration (DCR).
- [Claude Code](https://ivar.run/docs/guide/mcp/providers/claude-code.mdx): Setting up, authenticating, and running MCP servers in Claude Code with Ivar.
- [OMP](https://ivar.run/docs/guide/mcp/providers/omp.mdx): Setting up, authenticating, and running MCP servers in OMP with Ivar.
- [OpenCode](https://ivar.run/docs/guide/mcp/providers/opencode.mdx): Setting up, authenticating, and running MCP servers in OpenCode with Ivar.

## Providers

- [Claude Code](https://ivar.run/docs/providers/claude-code.mdx): What a Claude Code session materialises, the init flag that makes it the hall's provider, and how /ivar-discovery runs there.
- [OMP](https://ivar.run/docs/providers/omp.mdx): What an OMP session materialises, pre-tool hooks, and the extension that registers ivar commands and completes feature names.
- [OpenCode](https://ivar.run/docs/providers/opencode.mdx): What an OpenCode session materialises, the init flag that makes it the hall's provider, and how /ivar-discovery runs there.

## Reference

- [CLI overview](https://ivar.run/docs/reference/cli.mdx): What every ivar command has in common — the machine-readable contract, colour handling, and the command groups.
- [ivar feature](https://ivar.run/docs/reference/feature.mdx): The feature lifecycle on the command line — create, promote, execute, deliver, integrate, close and prune.
- [Glossary](https://ivar.run/docs/reference/glossary.mdx): Every term ivar uses, one short definition each, covering the model, sessions, planning, delivery and hall health.
- [ivar graph](https://ivar.run/docs/reference/graph.mdx): Graph commands — index, explore, callers, impact, affected tests, the viewer, the MCP server and its tools.
- [ivar hall](https://ivar.run/docs/reference/hall.mdx): Commands that create a hall and keep a checkout in line with ivar.json — init, sync, status, doctor, repo and provider.
- [Limitations](https://ivar.run/docs/reference/limitations.mdx): Where ivar's guard stops, and what ivar does not isolate or coordinate for you.
- [MCP servers](https://ivar.run/docs/reference/mcp.mdx): Declaring MCP servers in ivar.json, how sync spells them for each provider, and why a hall's servers can hold their own accounts.
- [ivar session](https://ivar.run/docs/reference/session.mdx): Session commands — start, connect, convert, stop, prune and relay, and the read-only guard they set up.
- [ivar skill](https://ivar.run/docs/reference/skill.mdx): Authored, external, and materialised across harnesses — how hall and personal skill roots work, how to install from external URLs, and how to keep them in sync.

## Blog

- [One feature, three repos: a walkthrough](https://ivar.run/blog/one-feature-across-multiple-repos.mdx): Promote the API and web app, discover the shared types need a change too, and deliver all three pull requests from one feature.
- [One repo, many agents: parallel features from a Figma prototype](https://ivar.run/blog/parallel-features-single-repo.mdx): Split a large prototype into subfeatures, run one agent per slice on its own branch with Figma MCP ready, and ship it as one pull request.
- [A code graph for agents that spans repos and parallel features](https://ivar.run/blog/code-graph-across-repos-and-features.mdx): Why ivar indexes the hall once and layers each feature on top, what the agent gets back from one query, and what that did to token use in a benchmark.
- [The context problem nobody solved: AI agents across multiple repos](https://ivar.run/blog/ai-coding-agent-multiple-repos.mdx): An agent is good inside one repo and blind between them. Five workarounds, and where all of them stop.
- [Configure Figma MCP for OpenCode in one step](https://ivar.run/blog/figma-mcp-opencode.mdx): Ivar materialises the Figma MCP server config into every session automatically. No manual setup, no token management, no per-repo duplication.
- [How ivar helps non-technical teams work across multiple repos](https://ivar.run/blog/ivar-non-technical-workflow.mdx): You don't need to write code to benefit from ivar. It gives product managers, designers, and tech leads visibility into a multi-repo codebase — and lets AI agents do the heavy lifting.
- [Git worktrees are great. They stop at the repo boundary.](https://ivar.run/blog/git-worktree-multiple-repositories.mdx): Everything the worktree posts get right, and the question that comes after it.