Connecting an agent to the rest of your stack — editors, CI, issue trackers — and the failure modes nobody documents.
Connecting an AI coding agent to the rest of your stack — the editor, CI, the issue tracker — is usually five minutes of configuration and two failure modes nobody documents. The failures are almost always about credentials or about the agent acting on stale state.
Each page here gives the wiring, then the part that breaks. We include the specific error text where we have seen it, because the error text is what you will actually search for.
Where an integration is genuinely not worth setting up, that is the conclusion.
An integration that connects is not an integration that works. Every page here ends with a check that proves the thing actually did something, not just that the handshake succeeded.
Most integration failures are a token with the wrong scope, an environment variable that exists in your shell but not in CI, or an expiry nobody noticed. Check those three before anything else.
Agents act on what they last read. An integration that caches aggressively will produce confident work against a repository state that no longer exists.
ralph wiggum claude code plugin — what it means for a repo with real invariants, not a demo.
obsidian mcp server — what it means for a repo with real invariants, not a demo.
notion mcp claude code — what it means for a repo with real invariants, not a demo.
linear mcp claude code — what it means for a repo with real invariants, not a demo.
jira mcp claude code — what it means for a repo with real invariants, not a demo.
cursor vscode — what it means for a repo with real invariants, not a demo.
cline vscode — what it means for a repo with real invariants, not a demo.
claude code xcode — what it means for a repo with real invariants, not a demo.
claude code vscode — what it means for a repo with real invariants, not a demo.
claude code slack — what it means for a repo with real invariants, not a demo.
claude code neovim — what it means for a repo with real invariants, not a demo.
claude code marketplace — what it means for a repo with real invariants, not a demo.
claude code jetbrains — what it means for a repo with real invariants, not a demo.
claude code intellij — what it means for a repo with real invariants, not a demo.
claude code github integration — what it means for a repo with real invariants, not a demo.
claude code github actions — what it means for a repo with real invariants, not a demo.
claude code frontend-design plugin — what it means for a repo with real invariants, not a demo.
claude code emacs — what it means for a repo with real invariants, not a demo.
claude code docker — what it means for a repo with real invariants, not a demo.
claude code browser extension — what it means for a repo with real invariants, not a demo.