Editor front: present a boxed agent to Zed and other ACP editors (wicket acp)

Open
#67 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
rust
Domain
backend, desktop

Research direction

Start with design §14.1.5 and research 21 §§3.3–3.5, then review issue #22 for related work. The issue leaves the project directory model and change flow open, so those decisions need resolving before implementation; done means wicket acp safely relays ACP to a boxed agent with the listed capability filtering, identity, prompt, and escalation behavior.

Written by the indexing model from the issue text.

Description

enhancement

Why. People want to work with an agent from their editor (Zed, JetBrains, Neovim, Emacs) while it actually runs in a wicket box, as wicket wrap does for Remote Control. Piping ACP straight through would be dangerous: Zed's terminal/create handler runs the agent's commands on the user's machine without its own check.

What: wicket acp, an ACP agent the editor launches (ChannelKind::AcpFront).

  • It relays to the boxed agent, filtering what the editor offers: it drops the editor's fs and terminal capabilities, MCP servers, env, _meta and extra roots, and maps paths between the editor's project and the box.
  • Agent prompts are shown to the human with once-options only. Escalations are announced in the editor but decided only in wicket: a wicket-only URL elicitation opens the console's passkey page.
  • The editor user's identity comes from the connection (the local user, or wicket's own sign-in), never from ACP's clientInfo.
  • Channel caps: {observe, message, control: interrupt only, answer_agent_prompts, decide_escalations: false}.
  • Design §14.1.5 describes it. For ACP-capable agents, this is the preferred remote UI when a zone's labels rule out a vendor session.

Open question. What is the editor's project directory for a boxed session: an extracted view, a read-only mirror, or a mount at the same path? And how do the agent's changes flow back?

Refs. research 21 §3.3–§3.5; design §14.1; #22.

Dominant language
Rust
Stars
0
Forks
0
Avg merge
1h 43m
Merged PRs (30d)
190

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from public/wicket

All issues in public/wicket

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.