new Just shipped: overcli 0.24.5. overgo workers run as a user of their own, can sit in a Slack channel and answer, and the console has a new look. what’s new ↓
codelions three tools · one philosophyGitHub

[ codelions ] · desktop tools for people who live in terminals

Over your tools.
Not instead of them.

Three open-source desktop apps that sit over what you already use — your agent CLIs, your repos, your database servers — and never take ownership of any of it. Plus overgo, which puts overcli on a server for your whole team.

3 apps + 1 server · Apache 2.0 · macOS · Windows · Linux

overgofor your team · alpha

overcli, for your whole team — on your own server.

Workers, teams and processes everyone in the org can ask from Slack, a web console or Claude. Each worker’s manager approves; processes carry work from team to team.

One container you run yourself. Free, open source, alpha.

self-hosted · Slack · MCPOpen overgo →
SLACK · # productMAMaya @overgo add an export button to the reports pageTRTriage Triage has this. Builder will take it.BUBuilder Its next step pushes code. Lionel, OK?Approve for this runBUBuilder Branch pushed. Open a pull request.#escalations → Reproduce → Fix → Ship the hotfix? → Tell the customer

[ philosophy ] · what all three share

Three rules every app keeps.

01Over, not instead

overcli drives the official CLIs. overgit keeps none of its own data inside .git. overdb is read-only until you say otherwise. Stop using any of them and nothing breaks.

02Your own logins

The AI in all three runs through CLIs you already have installed — overcli drives claude, codex, gemini, copilot and ollama; overgit and overdb use claude, codex and gemini. No API keys, no new bill.

03Built in the open

Apache 2.0, source on GitHub, a changelog entry for every release. Every claim on this site can be checked in the code.

[ latest ] · what just shipped

The latest from all three.

Highlights from each changelog.

[ who ] · the makers

Built by a father and son.

“It started as a way to spend time building something real together — Owen learning how a production app actually comes together, Lionel getting to teach by doing instead of explaining in the abstract.”

That's why the decisions look the way they do: they were chosen to be explainable, not just clever.

@lionelfarr · @owenlfarr

[ faq ]

Frequently asked questions.

Why does Codelions exist?

Because a father and son wanted to build something real together. Codelions is how Lionel and Owen Farr collaborate: Owen learning how a production app actually comes together, Lionel teaching by doing instead of explaining. The tools are what came out of it, free and open source — and every decision in them was chosen to be explainable, not just clever.

Who are these tools for?

Engineers who already live in CLIs and want to read the source, read the diffs, and uninstall cleanly. If you'd rather have a hosted black box, these aren't for you — and that's fine.

What does it cost?

Nothing. Overcli, overgit and overdb are free and open source under Apache 2.0. Overcli drives the agent subscriptions you already pay for — your Claude Pro plan, ChatGPT plan, gcloud credentials, or Copilot seat. No API keys to provision, no per-seat pricing, no new invoice.

Is there any telemetry?

None in the app. No analytics and no crash reporting; the only call out is an update check against GitHub Releases. Conversation history is files on disk you can open in any editor. You can verify all of that in the source — that's rather the point.

Can we use this at a company?

Yes. Apache 2.0 covers commercial use, and because everything runs locally against your own credentials there's no vendor in the path of your source code. The apps build from source if your security team would rather compile them itself.

What platforms are supported?

macOS, Windows, and Linux. macOS builds are Developer-ID signed and notarized, so they open on a double-click. Windows isn't code-signed yet, so SmartScreen may still warn. Building from source is one npm run dist away.

Who builds Codelions?

Lionel Farr and his son Owen Farr. The note from the two of them above explains more about why the tools look the way they do than any feature list would.