from art school to ai agents.
join me for a chat with @devon__kelley about the state of agents and building startups in SF.
sheโs solving the biggest hurdle in AI: agents break in the real world.
DN #2: Art School to AI Infra - The Future of Agents (w/ Devon Kelley)
Links ๐ https://t.co/pNOgrbyUhO
The `claude -p` subprocess approach still works. You just can't let any OpenClaw-branded strings reach the API.
It's a cat-and-mouse game. They'll likely add new fingerprints. The fix is knowing how to find them: binary search the system prompt, test each half with `claude -p --append-system-prompt`.
the Claude Code workaround might work short term but you're still burning tokens on tasks that don't need a frontier model. I had the same problem and ended up just routing by task type. low reasoning stuff goes to cheap models, Sonnet only when it actually needs it. cut my burn 75% :)
Ouch, Claude tokens are expensive when paying for them as extra usage
Trying to configure OpenClaw to use Claude Code instead of doing things directly through the API
I believe that should effectively emulate using Claude a code directly and have it included in Pro subscription
this is the future of saas:
one backend with two front doors.
one for humans. one for their agents. same building.
your users click buttons. their agents call your api. both do the same things.
why:
1. agents are the new power users. people are already wiring claude code, codex, and openclaw into their workflows. if your product doesn't have an api, you're invisible to them.
2. no drift. one canonical api layer means one source of truth. ui and api never diverge. you must support agent to support human.
3. skills is the new distribution. when your api works with any agent, agents find their way in themselves. your product becomes a tool for their agent, not a tab a human have to visit.
build for both from the start.
@rishpoddar@elvissun@posthog Love the tool call visualization thatโs cool! Are you not using adaptive routing as well? Your agents would avoid most of the issues youโre having to fix/optimize