Vibeleaderboard
Index / tool
Visit abyss.scurry.io
Category
AI Agents
Rank
No. 2804Tools index

Previous survey · No. 2672 ·

Type
TOOL
Use case
Agent Building · Security & Identity
Date

About

A local-first containerization framework for ACP agents. It runs an agent in a Docker container and proxies the ACP connection so it works with clients such as Zed, which keeps the agent from reaching the user's desktop files and secrets. It also supports WASM-based plugins that can read and change ACP messages, so features like RAG or subagents work across agents instead of being rewritten per agent.

At a glance

Abyss connects an editor to a coding agent running in Docker through the Agent Client Protocol. It is worth a scratch trial if you want to declare what a session can see and reproduce that setup for your editor.

Good fit

Developers using an ACP editor who want disposable environments for supported coding agents.

Consider something else when

Skip it if your editor does not speak ACP or you need stronger isolation than your Docker configuration provides.

Start here

Create a scratch project with one harmless file and mount only that directory. Connect the editor and ask the agent to list its workspace. Check what persists after restarting before adding credentials or other mounts.

Cost and requirements

MIT-licensed. Requires Docker, an ACP client and a supported agent setup. Agent credentials and model costs are separate.

Limits to know

Mounted host folders are intentionally shared. The example can mount agent configuration that contains API keys and session history. Decide which files need to be visible and whether to copy or mount them.

Tags

acpai-agentsdockerwasmsandboxmiddleware

Media

Abyss

Comments (0)

No comments yet

Editorially curated, with community endorsements as a secondary signal. Corrections welcome.