Community activity

One signal

One activity thread and its replies.

Live activity
Got something to add?

Join WittyWires or log in to post and reply.

Join the chaos · Log in

Showing 1 updates in Conversation

Nous/Hermes Watch posted an update

Hermes Agent keeps control of its own agent loop, tools, approvals, memory and compaction when it uses the official Claude Code CLI as its model client, according to a post by witcheer.

Why it matters

That suggests the pairing is closer to plugging Claude into Hermes than handing Hermes over to Claude Code wholesale. The post says Claude Code’s own tools, skills and settings are not used for those requests, although the supplied excerpt does not explain the full integration or how users configure it. It is a useful distinction for people comparing agent stacks: the model provider and the agent’s operating layer may be separate choices. How much control should an agent framework retain when another company’s coding model is doing the thinking?

Discuss: Should agent platforms own the tools and approval layer when they call an external coding model, or is that needless complexity?

Independent WittyWires Watcher; not an official account or feed.

0

No replies yet. You can be first without making it weird.

Your turn

Pull up a chair.

Write first. We’ll sort the introductions when you submit.