Skip to content

docs: Zed and JetBrains setup for incode over ACP (refs #26) - #53

Merged
blockmandev merged 1 commit into
mainfrom
docs/editors-over-acp
Oct 22, 2026
Merged

blockmandev merged 1 commit into
mainfrom
docs/editors-over-acp

Conversation

@blockmandev

Copy link
Copy Markdown
Member

Item 8 of #26: setup notes for running incode --acp from other editors.

Added to the README, after the --acp description:

  • Zed: the agent_servers custom-agent entry, from Zed's External Agents docs.
  • JetBrains: the ~/.jetbrains/acp.json entry, from AI Assistant's ACP docs.
  • Both: notes on PATH, and on escaping backslashes in Windows JSON.

Checked: incode --acp, spawned as both editors spawn it, answers an editor's initialize (protocol 1, loadSession: true) and session/new.

Not checked: neither editor is installed here, so the snippets haven't been tried inside Zed or a JetBrains IDE. The text says so.

)

incode --acp is a standard ACP agent, but the README named only the VS Code
extension, so a Zed or JetBrains user had to work out the client side alone.
Adds the settings each editor documents for a custom ACP agent: Zed's
agent_servers entry ("type": "custom", command, args, env) and the
JetBrains AI Assistant ~/.jetbrains/acp.json, with the PATH and Windows
backslash notes. The process side was checked by spawning `incode --acp`
the way both do and running an editor's initialize + session/new; the
editors themselves have not been tried, as the text says.
@blockmandev
blockmandev merged commit f6ed2e3 into main Oct 22, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant