Repository navigation
Description
Tracking issue. PR #677 shipped MCP-only adapters for 5 new agents (Warp, Cline, Continue, Zed, Droid). MCP is the lowest-common-denominator wrapper. It flattens agentmemory's 8 skills + 4 commands + 12 hooks into "just tools" and loses the slash-command + skill-autoload semantics each agent's native surface provides.
This issue tracks the per-agent native-surface audit results filed in #703–#707.
Per-agent breakdown
| Agent | Native surfaces we missed | Effort | Issue |
|---|---|---|---|
| Warp | Already scans .claude/skills/. Zero work, just verify + document |
trivial | #703 |
| Continue | prompts: + rules: keys in config.yaml (we wrote only mcpServers:) |
medium | #704 |
| Cline | .clinerules/ directory for rules |
small | #705 |
| Zed | Auto-loads .clinerules / AGENTS.md. Covered by the Cline / cross-agent rules adapter |
trivial | #706 |
| Droid | .factory/skills/<name>/SKILL.md. Same format as Claude Code skills |
small | #707 |
Cross-cutting finding
The skills format is converging. Warp, Factory.ai, and (post-v1.4.0) Zed all scan some variant of <dir>/skills/<name>/SKILL.md with name: + description: YAML frontmatter. agentmemory's existing 8 Claude Code skills are portable to all three with zero rewriting. Only the install path differs.
Suggests a shared helper rather than 5 near-identical adapters:
// src/cli/connect/skills-installer.ts
function installSkillsTo(rootDir: string, layout: "claude-style" | "warp-merged"): voidinstallSkillsTo("~/.factory/skills/", "claude-style")for DroidinstallSkillsTo("~/.warp/skills/", "claude-style")for Warp (when not relying on.claude/skills/autoload)- Future: same helper for Zed v1.4.0+
AGENTS.md is similarly cross-cutting. Cline, Zed, Factory, and most modern agents auto-load it. A single writeAgentsMd() would replace per-agent rules adapters for Cline + Zed (and possibly others).
What's genuinely not portable
Hooks. PreToolUse / PostToolUse / SessionStart / etc. are essentially a Claude Code exclusive. Of the 5 agents in PR #677, none have a public hook API. Continue has model interceptors but not a tool-event hook bus. We should be explicit in README that hooks are a Claude-Code-only surface and stop implying they're available everywhere.
Suggested order of attack
- Native audit: Warp auto-discovers .claude/skills/ for free #703 Warp. Verify + README. Zero new code. Lands today.
- Native audit: Droid skills use Claude SKILL.md format, install all 8 #707 Droid. Copy skills into
~/.factory/skills/. Tiny new adapter on top of existing MCP. ~80 LOC. - Native audit: Cline missing .clinerules/agentmemory.md #705 Cline + Native audit: Zed auto-loads via Cline / AGENTS.md fallback #706 Zed. Combined
AGENTS.md/.clineruleswriter covers both. - Native audit: Continue config missing prompts: and rules: keys #704 Continue. Biggest, write
prompts:+rules:properly. Last because most invasive.
Each lands as its own PR. No bundled-mega-PR. Small reviewable diffs.
Not in scope here
- New agent additions beyond the 5 PR feat(connect): Warp + Cline + Continue + Zed + Droid adapters (5 new) #677 covered.
- Goose (already deferred in PR feat(connect): Warp + Cline + Continue + Zed + Droid adapters (5 new) #677. YAML config needs a yaml parser dep).
- Env-var interpolation across all 16 adapters (pre-existing concern, separate issue).
Activity
rohitg00 commentedon May 28, 2026
Update:
npx skills addsubsumes 4 of 5 issuesFinding:
npx skills add rohitg00/agentmemoryalready works out of the box. Just tested:skills@1.5.9(by vercel-labs) reads.claude/skills/*/SKILL.mdfrom any git repo and installs to the calling agent's native skill directory. Its keyword list covers 4 of the 5 agents from PR #677:warp,cline,continue,droid. (Plus 45+ others.)Reframed plan
npx skills add rohitg00/agentmemory -a warpprompts:+rules:adapternpx skills add rohitg00/agentmemory -a continue.clinerules/writernpx skills add rohitg00/agentmemory -a cline.factory/skills/installnpx skills add rohitg00/agentmemory -a droid.zed/skills/adapteragentmemory connectvsnpx skills addare complementaryagentmemory connect <agent>writes the MCP server config so tools are available.npx skills add rohitg00/agentmemory -a <agent>installs skills so the agent knows when/how to use the tools.Both needed for full integration. The skills CLI install is what we were going to hand-roll in 4 separate adapters; offloading to vercel-labs/skills saves ~600 LOC of per-agent file-tree manipulation and tracks new agents automatically as the upstream keyword list grows.
What still needs to ship
agentmemory connect <agent>to print the matchingnpx skills addhint after a successful MCP wire. No subprocess spawn — keepsconnectdeterministic + offline-capable; users run the install themselves.skills@1.6.x+to add Zed support.feat(connect): print 'npx skills add' hint after successful wire (#709)
feat(connect): print 'npx skills add' hint after successful wire (roh…