Currently, the CTO, DevOps, and Research agents in our Paperclip instance run on claude_local (Claude Code CLI). We want to migrate these to hermes_local to leverage Hermes as the execution/orchestration layer with Kimi as the default model, while preserving Paperclip workflow compatibility.
Goals
1. Use Hermes as execution/orchestration layer — replace claude_local adapter with hermes_local for target agents
2. Use Kimi as default model — configure migrated agents to default to kimi-k2.5 (or available Kimi model)
3. Preserve Paperclip workflow compatibility — maintain issue assignment/review flows, checkout semantics, and activity logging
4. Maintain issue assignment/review flows — ensure agents can still self-assign, comment, and transition issues through Paperclip API
5. Stabilize automatic workflow completion — verify end-to-end runs complete without hanging or silent failures
6. Keep existing agents functional during migration — no downtime for CEO, Security, Backend, Frontend, QA, Data, Marketing agents
Current State
- hermes_local adapter is already registered as a built-in type in server/src/adapters/builtin-adapter-types.ts
- hermes-paperclip-adapter package provides the server-side execution, session codec, and skill sync
- UI already has hermes-local adapter config fields and icon components
- Hermes adapter supports supportsLocalAgentJwt: true, supportsSkills: true, requiresMaterializedRuntimeSkills: false
- Hermes adapter does NOT support supportsInstructionsBundle: true (unlike Claude)
Proposed Changes
1. Agent config migration — update agent records in DB (or seed scripts) to switch adapterType from claude_local → hermes_local
2. Model profile mapping — ensure Kimi model is available in hermesModels list or via detectModel()
3. Config field mapping — map instructionsFilePath (Claude) → hermesCommand / promptTemplate (Hermes) where applicable
4. Environment variable injection — verify PAPERCLIP_API_KEY and PAPERCLIP_RUN_ID injection works for Paperclip API auth
5. Testing — run end-to-end workflow: create issue → assign to migrated agent → verify run completion → verify comments/state transitions
Acceptance Criteria
- [ ] CTO agent runs on hermes_local with Kimi model
- [ ] DevOps agent runs on hermes_local with Kimi model
- [ ] Research agent runs on hermes_local with Kimi model
- [ ] Issue assignment, checkout, comment, and state transition flows work unchanged
- [ ] Existing non-migrated agents (CEO, Security, Backend, Frontend, QA, Data, Marketing) remain on claude_local and functional
- [ ] End-to-end test run completes successfully for at least one migrated agent
- [ ] PR linked to this issue with full verification steps
Risks
- Hermes adapter does not support instructionsBundle — agents relying on bundled SOUL.md/HEARTBEAT.md/AGENTS.md may need config adjustment
- hermesCommand path resolution differs from Claude Code CLI — may need explicit path config per agent
- Model detection fallback — if Kimi is unavailable, need graceful fallback or explicit model ID in config
Currently, the CTO, DevOps, and Research agents in our Paperclip instance run on claude_local (Claude Code CLI). We want to migrate these to hermes_local to leverage Hermes as the execution/orchestration layer with Kimi as the default model, while preserving Paperclip workflow compatibility.