🤖 Building the operating system for agent work.

I'm a software engineer based in San Francisco, founder of Compozy — where we build CompozyOS, a local-first operating system for agent work. Plug in the agent CLIs you already use (Claude Code, Codex, Gemini CLI, Cursor) and they become a team: they split the work, hand tasks to each other, run automated jobs and loops, and share one project memory. You steer everything from the browser.

Before AI ate everything, I spent a decade shipping open-source developer tools — Docz (23.6k+ ⭐), react-adopt (1.7k+ ⭐), reworm (1.5k+ ⭐), and a long tail of React, JS, and tooling libraries. I've also shipped Rust systems work — notably contributing to FuelLabs/data-systems, the official data-streaming libraries for the Fuel Network. Today, most of my work lives at the intersection of agents, local-first runtimes, and developer experience.

If you only have a minute, these are the projects I'd point you to first:

• 🎼 compozy — CompozyOS: a local-first OS for agent work. One daemon owns sessions, tasks, loops, memory, permissions, automation and tools. (2.4k+ ⭐)
• 🧩 skills — My curated collection of 132 agent skills for Claude Code and compatible assistants. (570+ ⭐)
• 📚 kb — Build topic-based knowledge bases from code, URLs, files and YouTube. Obsidian-compatible vaults, zero cloud deps.
• 📓 skeeper — Version PRDs, tech specs, ADRs and AI plans in a sidecar Git repo — without polluting your main PRs.
• 🔁 codex-loop — Keep Codex tasks running until they actually finish — by time, rounds, or independently confirmed goal.

The core thesis: AI agents are powerful but unreliable on their own. They need a place to live — durable state, permissions, peer discovery, knowledge, and quality gates — to turn one-shot generations into shippable software. That's CompozyOS, built in the open at @compozy.

🔀 Merged in July 2026. Compozy (orchestration) and agh (the local-first agent runtime with durable sessions and agent-to-agent networking, 180+ ⭐) converged into a single product. Orchestration alone wasn't enough — an agent needs the whole machine around it. The agh repo is archived; everything it did now ships inside compozy v0.3, and the peer protocol lives on as compozy-network/v0.

What's inside

• 🗄️ Work survives the terminal — sessions and Loop runs belong to the daemon, not to a client window
• 🎛️ One state, several surfaces — web shell, CLI, HTTP/SSE, UDS, MCP and native tools read the same runtime
• 🔐 People stay in control — approvals, permissions, run state, artifacts and agent activity stay inspectable
• 💻 Local-first by default — one Go binary and SQLite-backed stores; remote access is explicit, via the Gateway
• 🧩 Built to extend — agents, skills, capabilities, hooks, bridges and extension kits with a published Go/TS SDK
• 🕸️ Compozy Network — sessions discover peers, exchange typed messages, delegate work and close it with receipts

curl -fsSL https://compozy.com/install.sh | sh
compozy install && compozy daemon start
compozy session new --agent general --name first-run

Quality loops & QA

Knowledge & spec tooling

Distribution & experiments

A selection of projects I'm best known for from my pre-AI life. Several are archived or in maintenance mode, but they shipped to a lot of people.

• Shipping the CompozyOS v0.3 beta — daemon, web shell, extensions, Gateway, and the Compozy Network protocol
• Running multiple agent instances concurrently as a daily driver — and learning what breaks
• Teaching 3,000+ devs how to actually work with agents, and writing about agentic engineering
• Sponsoring open-source builders I rely on (@raphamorim)

• 𝕏 / Twitter — @pedronauck (personal) · @compozyai (product)
• 🌐 Website — compozy.com · 📖 Docs — compozy.com/docs
• 📦 Orgs — @compozy · @doczjs

_{📍 San Francisco · 🇧🇷 → 🇺🇸 · Coffee-powered · Always shipping}