Why it matters
Your app is the IDE gives ForkMesh a concrete mechanism for ForkMesh acting as the IDE surface for Claude Code context and diffs. The desktop app speaks the Claude Code IDE protocol: run claude in a repo and it connects to ForkMesh for diff views and selection context, just like an editor extension.
AI coding only helps when the agent can work in a real repository without trampling human state or hiding what it did. In ForkMesh, your app is the IDE addresses that need at the feature level, keeping the behavior close to the repository instead of buried in a detached hosted layer.
How ForkMesh handles it
ForkMesh handles your app is the IDE through the same split it uses across the product: ForkMesh runs agents beside the repository, capturing transcripts, branches, diffs, prompts, usage, questions, and handoffs in the desktop app.
The behavior is intentionally narrow: The desktop app speaks the Claude Code IDE protocol: run claude in a repo and it connects to ForkMesh for diff views and selection context, just like an editor extension. Humans keep control of instructions, answers, review, and merge decisions.
Where it fits
Use your app is the IDE when agent work should be reviewable, resumable, and connected to the same repo UI humans use.
It pairs with the rest of AI agents, built in because Your app is the IDE keeps ForkMesh acting as the IDE surface for Claude Code context and diffs connected to the repository, its signatures, and the nodes that serve it.