A provider vs Pacwich

A headless, provider-agnostic agentic loop. Every piece, memory, model, tools, stop conditions, sits behind a swappable interface. Streaming by default, one dependency,...

Monorepo tooling that works on top of Bun, npm, and pnpm workspaces, with a CLI and TypeScript API.

About A provider

A headless, provider-agnostic agentic loop. Every piece, memory, model, tools, stop conditions, sits behind a swappable interface. Streaming by default, one dependency, runs anywhere. The pieces to build your own agent: your Jarvis, your Cortana, your Samantha. The loop never writes to a screen, it emits one typed AgentEvent stream, so a trace is just data. Scrub the same run and watch three front ends rebuild in lockstep. One pass through the loop, seam by seam, each is just a field on runAgent() .

About Pacwich

Monorepo tooling that works on top of Bun, npm, and pnpm workspaces, with a CLI and TypeScript API. This package is the continuation of the original, now deprecated, bun-workspaces package. bun-workspaces users can expect minimal to no changes on average. CLI global install: Your pacwich command will still resolve to a local install when available. bun add -g pacwich # Print help for installing completions pacwich completion # Attempt to automatically install completions for your shell pacwich completion install Local install: Note the pacwich command works in your package.json scripts even without a global install.