Once I started running several Claude Code sessions in parallel, my problem stopped being the code. It was keeping track: which session was stuck on a permission prompt, which one had finished twenty minutes ago, and what each one had actually changed.
So I built
Factorai
, a desktop app where the session is the unit of work instead of the file:
It runs the real claude and codex CLIs in a real terminal, with your own login. Nothing is reimplemented.
You see at a glance which session is working and which one is waiting on you.
The diff, the commit graph and a search across every past conversation sit next to the terminal.
Routines: schedule a prompt to run on its own (nightly triage, dependency checks…).
On the “built with AI” question, upfront: yes, it’s built with Claude Code, mostly inside Factorai itself. What keeps it from being slop is in the repo: 69 ADRs, specs written before the code, and a 12-step quality gate every PR has to pass (oxlint, strict tsc, clippy with -D warnings, unit and Playwright tests). It’s all public, so judge for yourself.
It’s MIT and local-only: no account, no telemetry, no paid tier, and none planned. It’s a community project, not a startup. It runs on macOS, Linux, and Windows through WSL 2.
It’s still early. A few senior engineers use it daily, and fixes land on an alpha channel before stable. I’d really like to know what breaks or what’s missing from your workflow.
Test it, give it a try and give me feedback!
GitHub:
https://github.com/Nightbr/factorai
Site:
https://factorai.build/
PS: I had some real fun building the website too, give it a look
submitted by
/u/Nightb21
Originally posted by u/Nightb21 on r/ClaudeCode