Building agents without harness engineering

Re:Building agents without harness engineering by sidhusmart on Thursday June 11, 2026 @05:16PM (#48496532)

But isn’t that the same as using Claude agent sdk minus maybe the memory features? What I mean to say is that you could pick the latest one and switch when another better one rolls out?

We’re using Claude agent sdk right now to rollout an internal agent factory. We haven’t hit the memory issue yet but I do use Hermes as a personal agent and can see where it fits you.

[ Parent | on HN ]

Re:Building agents without harness engineering by rajit on Thursday June 11, 2026 @05:35PM (#48496754)

Good question. There a few differences between our approach and shipping an agent with the Claude agent sdk.

1. Our approach has cron-based or trigger-based automations built-in. Building automations with claude agent sdk requires setting up separate infrastructure.

2. Our approach has self-learning built-in. Building a feature like "dreaming" https://docs.openclaw.ai/concepts/dreaming with claude agent sdk also requires setting up separate infrastructure.

3. Our approach decouples the harness and the compute, which lets developers enforce a stricter security boundary, while claude agent sdk ships with the harness, shell, and filesystem in one process https://platform.claude.com/cookbook/claude-agent-sdk-07-hos....

4. Our approach does not vendor lock developers.

You could pick the latest harness and then switch when another better one rolls out. Our bet is that a developer's time is better spent speaking to their customers than switching harnesses.

[ Parent | on HN ]