Write the ticket. It comes back done.

A harness around Claude Code that runs your tasks on your machine — code, writing, actions, posts.

Write the ticket on Ponos’s own board — the console. He brings back a pull request, a text, an action carried out or a post ready to go. You answer in a word, even from your phone, and nothing ships until you say yes.

curl -LsSf https://raw.githubusercontent.com/hermez-agency/ponos/main/install.sh | sh
Ponos is named after the Greek god of toil: he does the tedious part, you keep the decisions.
How it works

The whole loop, in four gestures.

Two of them are yours, and each takes a few seconds. The two in between are Ponos's.

127.0.0.1:8787 — the console
  1. 01 · you

    You write the ticket

    What you would tell a colleague, on your board — then you move it to Ready.

  2. 02 · Ponos

    Ponos does it

    While you do something else: a pull request on its own branch, a text written into the ticket, an action carried out.

  3. 03 · you

    You read, and answer in a word

    A question or a result reaches you — in the console, or on your phone. oui is a whole answer.

  4. 04 · Ponos

    He delivers

    Move it to Validated: the pull request is merged, the post is published — and only then is it Done. Changed your mind? Cancelled files it away, never to be run.

Why hand it over

Three things it does that a to-do list does not.

It asks first

A doubt stops it.

A ticket nobody typed is classified before it runs, and a hesitation sends it back to you with the question. An action stops at its first doubt — a wrong account, a value the ticket does not give — rather than act on a guess.

You keep the hand

Nothing goes out without you.

No pull request is merged and nothing is published until you move the ticket to Validated. And it all runs on your machine, each ticket in a disposable worktree — your own checkout is never touched.

It comes to you

“oui” is enough.

Ponos · TelegramWhich header — the dashboard one or the public site?
the dashboard
✓ noted on “Le header” — the next run carries on.

When a ticket needs a decision, the question reaches you on Telegram or Slack, and your reply lands on the ticket.

Runs onClaude Codeand a board of its own. Plugs into GitHubTelegramSlackOpenRouter — only if you want.
What it does

Not only code. Four kinds of task.

The ticket’s type decides the road — pick it, or let a small model read the ticket and choose. A doubt stops it before anything runs.

Code

A pull request.

ticketConsole: limit the Done column

Its own branch, on a disposable worktree; the tests run. Merged when you validate.

Writing

A text, in the ticket.

ticketDraft the October newsletter

Release notes, a brief, a summary: written into the ticket, ready to copy. No repository needed.

External action

Done, and logged.

ticketAdd the DNS records for the new domain

In the browser or a service’s settings, with every change logged — before, after, what was checked. It stops at its first doubt.

Publication

Prepared, then published.

ticketPost the 1.2 release on LinkedIn

A post, a site put online, a message sent: prepared and shown to you first. Published once you say yes.

A chat with your machine

Create a ticket for the SQLite migration and make it ready — the console’s chat is a Claude Code session in your workspace, and it does it.

Projects, without ceremony

A project is a name and a brief. Give it a GitHub link and the repository is cloned the first time a ticket needs it; give it none and its tickets come back as text.

Around the tickets

What to do next, what it is for, the keys it needs, when it comes back.

Ideas

It proposes what to do next.

Ten ideas at a time, for the workspace or for one project, each with a category and a relevance score out of 100. Keep one, throw one away — it is never proposed again — or turn it into a ticket in a click.

Goals

What the tickets are for.

A goal has a criterion and a due date, and the tickets tied to it count toward it: “3 of 7 tickets done”, over a bar, Late once its day is past. The ideas are proposed with it in mind.

Vault

Keys, never in the ticket.

[vault] reads tokens where they already live — the environment, the keyring, pass, Bitwarden — and hands each project only its own. The session knows their names, never their values, and a value printed is masked.

Schedules

Tickets that come back.

Every Monday, review the dependencies — a schedule writes the ticket and moves it to Ready on its own, and the console lays the next ones out in a calendar. A machine off for a week wakes up to one, not seven.

The console

A board of its own.

Ponos needs nobody else’s board. The console, on 127.0.0.1, is where you write a ticket, drag it to Ready and watch its session live — with a chat with your whole workspace beside it. Under it, the tickets are in a local database, ponos.db, on your machine.

in English or French · light or dark
The console's board in light: columns Draft, Ready, In progress and Blocked, a card per ticket with its priority, its model and its project, and Ponos saying what he is editing on the tickets in progress. The console's board in dark: columns Draft, Ready, In progress and Blocked, a card per ticket with its priority, its model and its project, and Ponos saying what he is editing on the tickets in progress.
The current console, on a demonstration board. ponos service run — the installer already starts it. Everything it does →
Integrations

Plugs in where you already work. If you want.

Ponos needs Claude Code and nothing else. Each of these is one more token in the settings, and none of them is a requirement.

GitHub

optional

Pull requests. A code ticket comes back as one, and is merged on your yes. Connect GitHub in one click from the console: Ponos creates its own GitHub App, you pick the repositories, no token to paste — or keep gh. Writing, actions and posts need none of it.

Telegram · Slack

optional

Your phone. A question or a result reaches you there, and your answer — oui will do — lands on the ticket.

OpenRouter

optional

Every other model. One key: a GPT writes the copy, a model transcribes a voice note — or the sessions themselves run on the model you name.

Claude

Connect Ponos to Claude.

Your tasks, your projects, what is waiting for you — from a conversation, on the web or on your phone. Its address, nothing else.

claude.ai · Claude Desktop

  1. Settings › Connectors › Add custom connector, with your console’s address followed by /mcp.
  2. Click Connect: a Ponos window opens. Sign in, then Allow. No token to copy.
  3. Ask “who am I on Ponos?”, then “what is waiting for me?”
https://your-console.example.com/mcp

Claude Code

On the machine Ponos runs on, one line — then /mcp, Authenticate.

$ claude mcp add --transport http ponos http://127.0.0.1:8787/mcp

Nothing runs, nothing is deleted from there: Claude reads, creates a task, answers a blocked one. Every tool →

Installation

One command.

It checks what your machine has, says what is missing and how to install it, starts Ponos and opens its console in your browser. Everything after that happens there.

$ curl -LsSf https://raw.githubusercontent.com/hermez-agency/ponos/main/install.sh | sh

Then, the console walks you through it

On http://127.0.0.1:8787, a first connection in steps, each one checked for real before the next: the language, your password, who answers the sessions, GitHub in one click, a first project, and a demonstration ticket played there and then to prove it all works.

The board needs no step: the tickets are in ponos.db, on your machine.

What it needs

  • Linux or macOS — systemd or launchd keep it running, and without either the console still starts. On Windows, WSL works without systemd: the daemon then runs in the background, ponos daemon;
  • python3 ≥ 3.11 — its four dependencies, httpx, pydantic, FastAPI and uvicorn, go into an environment of its own, made by the installer;
  • network access to PyPI while it installs, to fetch them (and uv, from GitHub, when the machine cannot install a package);
  • git and Claude Code, which the installer offers to install;
  • gh is optional: the console connects GitHub in one click.

A missing one is named with the command that installs it, then run the line above again.

Dokploy Dokploy

Install on a server, with Dokploy

Ponos is in Dokploy’s template catalogue: HTTPS on a domain of its own, and your data on named volumes, so a restart or a new version keeps it.

  1. Create it. In Dokploy, Templates › search Ponos › Create. The domain, the password and the token are generated for you.
  2. Give it a way to reach Claude — the only thing required — in the Environment tab: the token this prints, into CLAUDE_CODE_OAUTH_TOKEN, or an Anthropic key into ANTHROPIC_API_KEY.
    $ claude setup-token
  3. Deploy, and open the domain. Sign in with PONOS_WEB_EMAIL and PONOS_WEB_PASSWORD, shown in the Environment tab. The console says what is still missing.

Ponos in the Dokploy catalogue → · Every variable, and the import without the catalogue →

Questions, answered

It does not work — where do I start?

  • The installer stopped. It printed what is missing and the command that installs it: run that, then the install line again.
  • The console does not open. Go to http://127.0.0.1:8787 yourself; if nothing answers, ponos service run starts it and says why it cannot.
  • The demonstration ticket fails. The console shows what the run said; Run the full diagnosis on the summary — or ponos doctor in a terminal — checks everything, and is the text to paste when asking for help.

What does the Dokploy template set up, and what can I add?

The three steps are above. The image carries everything a ticket needs — Claude Code, git, gh, Node —, pinned to the release the template was published with, and runs as a user of its own, never root. Four named volumes keep the configuration and the board, the clones, and the sign-ins of Claude Code and gh; a healthcheck asks /healthz; memory is capped at 4 GB.

  • Required: CLAUDE_CODE_OAUTH_TOKEN (your subscription) or ANTHROPIC_API_KEY.
  • Optional: OPENROUTER_API_KEY for every other model; GH_TOKEN for the pull requests — or a GitHub App, created from the console; PONOS_TELEGRAM_TOKEN and PONOS_SLACK_TOKEN for your phone.
  • Generated or set: PONOS_WEB_EMAIL, PONOS_WEB_PASSWORD and PONOS_WEB_TOKEN; PONOS_LANGUAGE, en or fr; TZ, the zone a schedule’s hours are read in.

A Dokploy without Ponos in its catalogue imports it: a Compose service, Advanced › Import, and the Base64 the documentation prints.

How do I reach Ponos from my phone, away from my desk?

With Tailscale: a private network between your own devices, free for personal use. No port opened on the Internet.

  1. Tailscale on the machine that runs Ponos. Create an account, then on Linux:
    $ curl -fsSL https://tailscale.com/install.sh | sh
    $ sudo tailscale up
  2. Tailscale on your phone. The app, signed in to the same account.
  3. Serve the console on your tailnet. It listens on 127.0.0.1:8787 only — on purpose, since it starts sessions that run code — so the machine’s 100.x address will not reach it. Tailscale relays to it instead, over HTTPS:
    $ sudo tailscale serve --bg 8787
    It prints the address, https://<machine>.<tailnet>.ts.net. The first time, it may ask you to enable HTTPS for your tailnet.
  4. Give Ponos that name. In the configuration (ponos config), or Settings › Public address in the console:
    # [web]
    url = "https://<machine>.<tailnet>.ts.net"
    The console answers that name, and that one only; without it, a 421. No restart needed.
  5. Open the address on your phone, and sign in as on the machine — your email and password, or the token (ponos service run --print-token).

Never tailscale funnel. Funnel puts the console on the public Internet, and behind it sits a runner that runs code on your machine. Stay on your tailnet.

Everything else is in the documentation

Handmade

Made by a developer — and by Ponos himself.

Most of this repository’s pull requests were opened by Ponos, from tickets on its own board. The releases are cut the same way.

A Hermez product The other projects of the same agency, at the same address.
hermez.dev