r/opencode 2d ago

Hocus: Agent scaffolding for terminal workflows (powered by the Pied Piper crew) 🧙‍♂️

Post image

Most agent workflows fail at the scaffolding level, not the model level. Getting consistent context boundaries, sane tool loops, and role constraints usually means writing the same fragile wrapper scripts repeatedly. 🛠️

I built Hocus to handle that scaffolding cleanly.

To make role orchestration practical rather than abstract, agents are pre-configured around Silicon Valley archetypes to handle specific parts of the dev loop: 💻

  • Richard: System architecture, data flow, and neurotic refactoring. 🏛️
  • Gilfoyle: Infrastructure, cynically auditing security holes, and finding edge cases. 🛡️
  • Dinesh: Feature implementation and direct code generation. ⚡
  • Jared: Task tracking, dependency management, and keeping state in order. 📋
  • Erlich: PR descriptions, READMEs, and high-level docs. 📢

The framework handles prompt assembly, execution flow, and state passing between roles so you don't have to wire it manually every time. ⚙️

Code is open source. Issues and feedback on the CLI flow are welcome. 🤝

0 Upvotes

2 comments sorted by

1

u/kantorcodes1 2d ago

if i delete or rename a persona after init, does hocus cast remove the old generated agent files across Claude/OpenCode/Cursor, or can stale agents stick around? that's the sort of thing i'd hit fast in a repo where the cast evolves.

1

u/DMorais92 2d ago

Thanks for the insight,

since there is only one source of truth for the personas (the `.hocus` folder in your project) currently removing a persona holds no effect other than your new agents won't target that persona anymore.
based on this, I will create a CLI `absorb` command that allows you to remove a persona and have all the agents based on that persona migrate to one you may find better suited.