Skip to main content
← Back to list
01Issue
FeatureClosedSwamp CLI
AssigneesNone

Relationships

#450 Support deepAgents CLI/SDK as a target agent

Opened by emil · 5/26/2026

So far, there is Codex, Code and OpenCode. The first two are proprietary, so no-go in some cases. Would be great to have another open-source agent supported - and deepagents (https://github.com/langchain-ai/deepagents) brings an Agent CLI + an SDK, supporting open-weights and local models. Would be great to support it as well. And yes, I do have a horse in this race. Let me know if I can help make this happen.

02Bog Flow
OPENTRIAGEDIN PROGRESSCLOSED

Closed

5/26/2026, 7:22:53 PM

No activity in this phase yet.

03Sludge Pulse
Editable. Press Enter to edit.

stack72 commented 5/26/2026, 3:53:07 PM

Hey @emil - I am working on a generic way of being able to specify any agent harness - I have a draft PR open so I can try it against this suggestion and see what it does. This is a great usecase for that! Thanks, Paul

stack72 commented 5/26/2026, 7:22:23 PM

PR #1400 shipped swamp agent setup — the generic custom tool framework mentioned in the earlier comment. deepAgents is now fully supported:

swamp agent setup    # name: deepagents, instructions: AGENTS.md, skills: skills/
swamp repo init --tool deepagents

The wizard detects deepAgents conventions: bare skills/ directory at the repo root, AGENTS.md for instructions (shared mode), no frontmatter needed. It also offers a skills directory confirmation step so users can pick between the derived .deepagents/skills/ and the detected skills/ path that deepAgents actually expects.

Since deepAgents uses the same SKILL.md convention with name/description frontmatter, swamp's skill scaffolding drops in without any format translation.

No code changes to swamp are needed to target deepAgents — this was the design goal of the custom tool system.

A separate docs issue has been filed for a how-to guide covering the custom tool workflow.

Sign in to post a ripple.