Blog
Signed review capsules, AI-assisted changes you can verify, and the engineering behind the CLI and the cloud. No announcements-only filler.
3 min readReleases
The first public release, described the way we would want a vendor to describe theirs: every command and cloud route that works end to end, every one that prints a message and exits, and the order we plan to close the gaps.
4 min readWorkflows
The expensive part of agent-assisted work is the context you rebuild at every boundary: human to agent, agent to human, Tuesday to Thursday. A handoff pattern built on one sealed review per Arc, and where transcript tools fit next to it.
3 min readWorkflows
A forty-file diff across four packages is four reviews wearing one trench coat. How PatchArc detects workspace scopes from ten layouts, how classification works, and how to declare scopes and ownership yourself.
4 min readEngineering
A walk through the capsule format as patcharc 0.2.0 writes it: the ZIP layout, why it is stored uncompressed, what the manifest signs, and each check verify performs on your machine and again in the cloud.
4 min readEngineering
Six sections, computed from commits, files, scopes, and your own notes, with no model in the loop. How each section is derived in 0.2.0, where the heuristics are honest placeholders, and why that design makes the capsule verifiable.
4 min readComparisons
Three vendors, three different things called privacy. A plain reading of what CodeRabbit, Greptile, and Sourcery publish about retention, what bring-your-own-key changes and does not change, and how PatchArc stores a provider key.
5 min readGuides
An agent made forty commits while you were in a meeting. Here is how to turn that into a record a reviewer can verify offline, using only Git and a CLI, and what the record does not cover yet.