Claudia gives your coding agents one operating standard, durable context, and a manager for every repository.
Plans, builds, ships, with your oversight.
Work lands as a pull request on GitHub. Draft PRs and pushed checkpoints mean a lost session does not lose the work.
Integrates with · Built on
The problem
Your coding agents are powerful — but alone, they don't ship. No shared practice, no durable context, no one responsible for finishing. You are holding it all together.
They wait for you to prompt. No initiative, no follow-through. You are still tracking every task yourself.
Every session re-explores the product, the architecture, and the decisions from scratch. Nobody carries a piece of work from intent to merged pull request.
Each repository, each tool, and each session brings its own habits. You are the integration layer across the whole portfolio.
Claudia is the operating system that turns your coding agents into a managed development operation — one practice, durable context, a manager for every repository, and you in control.
What Claudia supplies
Not another coding agent — the system that makes your coding agents productive. Reusable skills, repository context, and a responsibility contract, across Claude Code, Codex, Cursor, and Hermes.
How it fits together
While you work, in the tools you already use. While you sleep, on Hermes. Both land on GitHub, and you steer from Slack.
While you work, the Human Operator types, shows, or speaks to any surface, steers from Slack and works in Claude Code, Codex, Cursor, where a top-level task is the repository manager. While you sleep, Hermes runs one scheduled repository manager per repository, started by a heartbeat wake against ready issues or by a Slack ask. Claudia supplies both lanes with skills, repository context, and one responsibility contract. Both lanes converge on GitHub, which holds Git, Issues, Pull requests, and Review: Issue, Ready, Draft PR, Review, Merge. Memory is long-term and shared by both lanes: Markdown brains in every repository, indexed by one gbrain on Postgres. The models from all your subscriptions (Astra, Sol, Fable, Opus, Composer, Grok, Flash, GLM 5.3) are available to both lanes.
Claudia supplies
Skills, repository context, and one responsibility contract, delivered as a versioned release. It shapes how the runtimes work; nothing runs inside it.
GitHub records
Git, Issues, Pull requests, and Review. Immediate work on a PR, deferred work on an issue. Nothing important lives only in a chat.
Runtimes execute
Claude Code, Codex, and Cursor when you are present. Hermes when you are not, one scheduled manager per repository. Same practice, same record, either way.
The same loop whether a manager is attended or scheduled. It is a sequence, so it is numbered.
What the private reference portfolio has recorded: six scheduled repository managers active on Hermes, each verified with read-only wakes against its repository in September 2026.
A complete unattended implementation-to-merge cycle is not yet part of that record. Anything beyond the record is a target, not a result.
Skills, not stages
Independent skills for product, architecture, design, specification, backlog, build, review, test, deploy, and writing. A manager composes the ones an objective needs; a build can carry a coherent objective end to end on its own.
What you can ask for
From the first scoping question to the merged pull request — each capability is a skill you can use on its own, so you steer instead of stitching tools together.
Captures product vision, settles architecture, designs the experience, and writes build-ready specs.
Owner-groomed backlog, implementation that starts from current evidence, and checks chosen from the actual risk.
Pull requests that carry their own evidence, review chosen by judgment, and deployment within delegated authority.
Health checks, security scans, and performance audits, run when asked or from an owner-groomed issue.
Meaningful outcomes and precise decision requests in Slack; the record stays on GitHub.
Self-correcting from mistakes with persistent memory, drift detection, and automatic gap reporting.
Position, attract, convert, retain — the marketing skills, run by the same manager under the same contract.
Position
Attract
Convert
Retain
Mechanisms
Five mechanisms — from the durable record to the merged pull request.
Pull requests carry immediate delivery with objective, evidence, and review conclusion. Issues hold what is deferred, blocked, or independently actionable. A restarted manager reads the record instead of a recovery log.
In practice
Where you stay in control
Enforcement you can inspect, not promises you have to trust. Every boundary names the record, check, or actor that makes it real.
A repository manager may implement and merge its own authorized work after proportionate checks and an exact-head confirmation against the current base. Delegated workers return evidence to their manager and never merge.
Pull requests carry the objective, evidence, checks, and review conclusion. Issues hold what is deferred or blocked. GitHub is the searchable, permanent record; nothing important lives only in a chat.
Direction, shared architecture, secrets, destructive action, production, spend, security floors, and public commitments stay human-owned at every size of change. No successful check expands authority.
GitHub-native. Your agents, your runtimes, your repositories. Practice arrives as a versioned release you can read; remove it and everything stays exactly where it is.
Steer from anywhere
Attended work happens where you already code. Unattended work reports to Slack. The record is the same GitHub either way.
Attended: you and a repository manager, live
Unattended: Hermes works the queue, Slack keeps you informed
Work continues either way. GitHub keeps the record.
Use cases
Agents do the routine work. You keep the decisions that matter.
You settle the objective and label it ready. A repository manager reads the record, implements, verifies, and lands the pull request. Read it when you are ready.
Dependency updates, routine fixes, and groomed housekeeping picked up on the next scheduled wake. Agents triage and implement. You review.
Several products, one standard. Claudia keeps priorities, dependencies, and decisions coherent across repositories without a second tracker, and points you at the GitHub record that owns each answer.
Briefings
Editorial deep-dives on oversight, orchestration, and the shape of software work as agents take on more of it.
The biggest shift in software engineering since the GUI is here. Engineers are becoming orchestrators of AI systems - and the skills that matter are changing fast.
AI touches most of the development process, but only a fraction of tasks can be fully handed off. The gap reveals why supervision architecture is the key differentiator.
Work that once required cross-team coordination collapses into concentrated sessions with AI agents. The organizational implications are beginning to unfold.
See how a repository manager turns an issue you have labelled ready into a merged pull request, with the evidence on the record and the decisions that matter still yours.
