Readit NewsI was surprised this wasn’t already supported. Does anyone know what made this difficult, or why it took this long to ship?
On expanding beyond Claude: there’s no concrete plan right now since we built this around Claude, but we’re very open to it. If you have a preferred CLI (e.g., Codex, OpenCode, or something else), feel free to open an issue in the repo. Or just describe your use case here and I will do it :)
Regarding branches: the tool does not pollute your working branch. Each session lives on a separate “session” branch that contains all prompts and operations. Your normal working branch stays clean.
When you end a session, you’re prompted to either:
merge the code changes into your working branch, or
discard them.
If the video or README didn’t make this clear enough, I’d appreciate the feedback I’ll update the docs accordingly.
And even though it doesn’t actually get full sudo access, giving an LLM permission to edit files without being able to track exactly what it’s doing still feels risky.
What really stands out is that everything lives in Git. Designs sit next to the code they relate to, with versioning, history, and collaboration handled by tools developers already use. This avoids a lot of the friction Figma had for years, where design history, branching, and reviews were either missing or awkwardly bolted on later.
If Sketch -> Figma was about moving design to the browser, Pencil feels like the next step: treating design as a first-class, versioned artifact in the developer workflow.
Curious how designers and engineers here think about Git-based design workflows, and where this approach might fall short compared to Figma.