151–160 of 200 posts
I feel I’ve been left behind because all I use is Agents.md / Claude.md and Project.md. No skills, no tools. Everything I want my agent to do is specified in those two files. I also have a particular directory and file structure for things like scripts and sources which is indexed in the mds.
Does anyone have a suggestion for a harness that is good at handoff? When I say handoff, I mean: * handoff from a terminal CLI to webui (on a phone)? * handoff from one team member, to another? * handoff from one communication modality, like writing a prompt in a TUI, to email? * handoff from one model to another, or one provider (openrouter)( to another (llama.cpp) Does such a thing exist? I used to think that a PR…
Open core is here: https://github.com/gofixpoint/amika
We're designing it like a meta-harness actually. The goal is to let users put any agent(s) (Claude, Codex, Pi, OpenCode) on a sandbox on any computer (local, K8S pod, cloud VPS, sandbox provider, etc.)
And then be able to interact with the agent(s) from anywhere: terminal, phone, web, or load them into the Codex, Claude, or Cursor apps
Yapped a bit about this "multi-surface" agents idea last week: https://x.com/dbmikus/status/2087993214246469639
Under the hood, I think of part of our tech like mashing together Tailscale and Firecracker.
The edges are rough right now, but if you kick the tires, I appreciate any feedback! (my email is dylan@amika.dev)
And besides what we're building, there are cool projects like Amp Orbs, YC's QM harness, etc.
Does anyone have a suggestion for a harness that is good at handoff? When I say handoff, I mean: * handoff from a terminal CLI to webui (on a phone)? * handoff from one team member, to another? * handoff from one communication modality, like writing a prompt in a TUI, to email? * handoff from one model to another, or one provider (openrouter)( to another (llama.cpp) Does such a thing exist? I used to think that a PR…
The session is "just" the raw chat history in it's entirety (human and agent) and can be disseminated as such. This is what enables swapping between models, you simply send the whole context. Not sure how others do it, but opencode stores sessions in a sqlite db and you can extract them and share them as needed. https://opencode.ai/docs/cli/#export Pro-tip: Building your own extremely minimal harness takes about 15m…
apparently its an easy way to get on HN, seems like a great blogspam target
A harness is the thing that turns sloppotron spew into action. That's... pretty much it. LLMs are still "just" token prediction algorithms, but you can coax them into outputting things that look like commands. The harness figures out which bits are supposed to be commands, executes them, and feeds the output back into the context of the LLM. They also have prompts of their own to guide LLM behavior.
It’s private and I charge for it and I am always looking at the list of skills and agents people create (I’ve never copied anyone else’s stuff) and so far I like mine better.
It makes me roughly 20x faster at building systems and Claude itself closes gaps in my knowledge like networking and cloud devops.
If you’re serious about producing quality code, it’s my belief that a strong harness is the best way.
There are articles about it from Fowler and Redhat.