DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to put a guard proxy between Zed and an ACP agent with Jev Guard

Wrap an ACP agent in Jev Guard so permission requests cover terminal and file writes.

Who it is forA developer who runs an ACP-compatible coding agent inside Zed and wants approval requests for terminal and file writes.

The problemAn ACP agent can ask to create terminals or write files through the editor, and the editor alone does not score each call for risk or injected content.

The outcomeTerminal creation and file writes raise a permission request, and reads and terminal output are flagged when they contain injected text.

What you need first

  • Node.js and npm, to install the jev-guard package or run the install commands
  • One provider key: a TypeSafe key from console.typesafe.ai, a vck_ Vercel AI Gateway key, or an sk-or- OpenRouter key
  • The coding agent you want to guard, installed on the same machine

Steps

  1. Run npm i -g jev-guard
  2. Run jev-guard key "…" with your provider key
  3. In Zed settings, add an agent_servers entry whose command is node and whose args include the path to src/cli.js, then acp, --, and your agent command
  4. Start a session in Zed and confirm a permission request appears for a terminal or file write

Prompt for your agent

Configure a Zed agent_servers entry in <settings-file> that runs the jev-guard acp proxy around <agent-command>, following the leepokai/jev-guard ACP example. Report the final JSON and confirm the proxy is the command that starts the agent.

Caveat. The README says the proxy only sees traffic that passes through the client, so tools the agent runs on its own are not covered.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page