Building on top of Codex or Claude locally?

You probably don’t want to keep rewriting the same glue for:

model pickers, chat/plan mode, supervised vs full-access, approvals, session resume, tool activity streams, and provider quirks.

I’ve been working on  \`@ouim/agentkit\`: a host-side TypeScript SDK for local agent runtimes.

It gives you one builder-facing API for:

* opening and resuming sessions

* switching models

* chat/plan controls

* supervised / auto-edit / full-access modes

* approvals and user-input prompts

* normalized activity events for agent UIs

It sits above Codex app-server / Claude runtime glue, so you can build the product instead of maintaining adapters.

If you’re building agent UIs, review tools, desktop wrappers, or internal workflows on top of the Codex/Claude CLIs, I’d love to hear what controls or events you need most.

GitHub: https://github.com/thezem/AgentKit

----

I'm also Looking for a few maintainers / design partners for agentkit.

The goal is not “yet another agent framework.”

The goal is narrower: a stable host-side SDK for local agent runtimes like Codex and Claude.

We’re focused on the layer app builders actually fight with:

* session lifecycle and resume

* model and runtime controls

* approvals and user prompts

* normalized event streams

* provider discovery

* escape hatches when raw provider detail matters

Important boundary: this is not trying to replace orchestration, event stores, replay systems, or app-owned UI state. It’s the runtime substrate underneath those.

If you care about SDK design, local agent infrastructure, runtime contracts, or making Codex/Claude-based tooling less fragile, I’d love contributors who want to shape this early.