ENDE Join the beta
For developers

The same team, on your code.

Ethlin writes code too. Each piece of work gets its own branch, checks run on it, and nothing lands until you approve it.

  • The chat you plan with
  • A piece of work, on its own branch
  • Helpers
  • Checks
  • code-review
  • designer
  • writer
  • researcher
  • skill-writer
The code map: every file of a project sized by its lines, with the agents working in it.
Your codebase as a map: every file sized by its lines, and where each agent is working.
The code map answering how the savings page reaches the funding rules.

Your code as a map.

Agents ask the map before they search.

The voice pipeline: hearing and speaking on this machine, the thinking on your own sign-in.

Pieces you can swap.

Microphone, recogniser, model and voice, joined like bricks.

The timeline of a run, one lane for each agent and what it did when.

Every run, on a timeline.

Tokens and minutes per agent, live.

How a run goes.

You plan with one chat. Everything after that happens on branches, and nothing lands without your yes.

  1. Plan

    The chat you plan with stays in your main checkout and changes nothing there. It shows you a plan and how it splits the work, and waits for your go.

  2. Pieces of work

    Each part you would approve on its own becomes a piece of work, in its own git worktree, on its own branch. A piece can start helpers on branches of its own.

  3. Checks

    Ethlin runs your project's checks on each piece. A failing check goes back to the agent that wrote the code.

  4. Checked before you approve

    Large or risky work is checked before you approve it. More than 300 changed lines, or a change to the database, credentials, accounts or git, gets a second reading.

  5. Approve and ship

    Approved work collects on one integration branch, so your own checkout is never touched. Ship keeps it local, pushes it, opens one pull request, or merges it when there is no remote.

A follow-up goes to the agent that built the piece, in its own conversation, instead of a new one reading everything again.

What you get.

With developer features switched on.

Worktrees and branches

Every piece of work and every helper has its own worktree, so agents never step on each other or on you.

The Changes view

What each branch changed, as red and green diffs, before you approve it.

The Codebase tab

A map of your code drawn by a plain program, no AI: dependencies, structure, layers, history, and which agent is reading or editing what, in 2D or 3D.

Previews and terminals

Live previews of what is being built, and embedded terminals beside the chat.

Models, technically

The Ethlin Engine, Ethlin's own agent runtime, runs every model, with a key or with the AI in your plan: its own coding tools, prompt caching, condensing of long conversations, and resuming where a session stopped. Connect any model

Skills in the open format

A skill is a folder with a SKILL.md, the format Claude Code and Codex also read, so the skills you already have work unchanged.

  • Branch & pull request
  • Integration branch
  • Prompt cache
  • Connect any model

Why we built it this way.

Ethlin is built inside Ethlin. A few sentences from the people who make it, about working this way every day.

Ready when you are.

Join the beta, and Ethlin shows you around when it opens.

Available from 2 November 2026 · macOS · Windows · English · Deutsch

We use your address only to write to you about Ethlin. Privacy policy