Launching today
Farol
The macOS terminal that shows which coding agent needs you
21 followers
The macOS terminal that shows which coding agent needs you
21 followers
Farol is a macOS terminal for running Claude Code and Codex in parallel. A sidebar shows which agent is working, which is waiting for you and which is done, and the menu bar shows it from any app. Each task gets its own git worktree, started from a prompt, a GitHub issue or a Jira ticket. Review the diff, commit, push and open the PR in the same window. Built on libghostty, so it reads your Ghostty config. Free and MIT licensed. No account, no telemetry.
Free
Launch Team
EneyProactive AI for Mac. Free test, 20,000 credits.
Promoted
@lucaasnp_ Congrats on the launch! The pain point you described is so real for anyone running multiple Claude Code sessions at once.
Loving the commitment to native Swift, libghostty, no telemetry, and native git worktree integration.
separate worktrees solves the file-conflict half of running agents in parallel, but not the half that actually bites me: two tasks that touch the same API contract or shared schema from different worktrees, where neither agent can see the other's change until someone opens both diffs side by side at merge time. does Farol do anything to flag "these two active tasks touched overlapping files or symbols" before you're staring at a nasty rebase, or is that still on the human to catch by reading both PRs?
@galdayan Good question, and you're right that worktrees only solve part of it. Farol doesn't flag overlap between tasks yet, so today that's still on you reading both diffs.
What does help: the review panel shows everything a session changed since it left main, so comparing two tasks is two clicks, not two PRs side by side. And when a rebase does stop, there's a three-column conflict resolver built in.
Next on the roadmap is letting agents see each other's sessions, so one can check what another is changing before it touches a shared schema. Since Farol already tracks each session's changed files, a "these two tasks touch the same file" warning could be a natural addition.
@lucaasnp_ a file-level warning would catch most of it honestly, that's a cheap check and probably 80% of the real cases. the harder version is two agents editing different files that both call the same function signature, where there's no file overlap at all but the contract still breaks. probably not v1 material, but worth keeping in mind that "same file" and "same symbol" are different bars and the second one is where the actually nasty bugs hide.