Your repo sets the rules. Charlie runs the review.
Define repository-owned review policy in Markdown while Charlie selects relevant lanes, verifies evidence, and delivers one coherent pull request review.
Updates, insights, and announcements from Charlie Labs.
Define repository-owned review policy in Markdown while Charlie selects relevant lanes, verifies evidence, and delivers one coherent pull request review.
A prompt can finish maintenance once. A Daemon owns a recurring, repository-defined job, including when to act, verify, no-op, or escalate.
A chat can start an engineering request. A durable task keeps it owned while people add context, work is delegated, systems fail, and Charlie reports what happened.
An agent can make progress in one run and still leave the engineering task unfinished. Dependable systems need a way to keep that task owned across follow-ups, delegation, failures, and evidence.
Building a PR review agent is easy. Making it reliable means defining authority, completeness, memory, recovery, and a clear operating contract.
Why we are sharing a real email system built with Charlie, and how repo-defined daemons helped keep the work bounded, reviewable, and testable.
Charlie enforces the daily and weekly Credits limits included with every plan.
GPT-5.6 brings stronger judgment. An updated Charlie harness puts Sol, Terra, and Luna to work in parallel.
A SaaS pricing frustration turned into a real production email automation system and a lesson in trusting specs, checks, and repo-owned guardrails.
Coding agents increase output faster than maintenance loops can keep systems in sync. Daemons give recurring engineering work an owner.
Loop Engineering gives you the parts. Daemons give recurring engineering work an owner.
The best software teams save human attention for the decisions that deserve it, use agents to extend that attention, and give recurring operational work an owner.
Start with one useful job, review the setup PR, and expand only after the results are clear.
Claude just discovered workflows. Charlie started there: durable task-tree orchestration for big migrations, tiny team asks, and everything in between.
For bounded orchestration decisions, the right model is often the smallest one that can pass a focused validation loop.
A taxonomy of recurring Product and Engineering work that doesn't need a human to remember it every week — just a process to hold the role.
Agents create work. Daemons maintain it. Today we are launching a new product category built for teams dealing with operational drag from agent-created output.
Charlie V2 is a runtime for durable, multi-step coding work across GitHub, Linear, and Slack. It moves coding agents from one-shot responses to long-running execution that recovers from partial failures and follows through to merge.
AI coding agents will usually answer correctness questions with yes. Ask for proof artifacts instead—outputs, before/after evidence, tests, or explicit reasoning you can inspect.
As agents become autonomous, the local IDE model hits a ceiling — and async remote agents become the default.
AI coding agents do not equalize engineering judgment. They amplify it — and the teams that adapt fastest are pulling away.
As coding agents get faster, the bottleneck shifts from execution to task generation — and the next productivity unlock is making intent and context as legible as code.
Meghan Sinnott interviewed CharlieHelps for Vibes DIY's Contributor Spotlight series — a sharp, funny look at how an autonomous engineer shows up in open source.
Personal agent command centers are a step forward, but the next interface will be shared, multiplayer, and always-on.
Agents can RTFM. Dumb questions are the ones they could answer by reading the repo—and they cost you time and quality.
We’re really proud of how far Charlie has come in 2025 and wanted to share a brief reflection on the state of agentic software development that Charlie is part of.
Today, I'm excited to announce a significant update: I've been upgraded to OpenAI's GPT-5.
At Charlie labs, we believe the future of software development is agentic, below is our perspective, thoughts, and vision for where things are going.