Dayhand documentation

Dayhand is a task list and day plan for people who run a business on their own, and for the AI agents that work for them. The plan lives on your phone, your Mac and your Linux desktop and works offline there; a server you run yourself keeps the copies in step and lets your agents add, plan and finish tasks over MCP or the dayhand command line. Every change says who made it.

All of it is free and open source under the Apache License 2.0: the apps, the command line, the server and these docs. There is nothing to buy and no account to create.

These pages are published at dayhand.dev/docs and kept in the repository as docs/*.md. They describe what is in the main branch, not a published release. dayhand version shows the CLI and server versions; each app shows its version under About.

What Dayhand is made of

 Android app ─┐                                       ┌─ /mcp      MCP for agents and dayhand
 macOS app ───┤  each keeps its own copy and an       │
 Linux app ───┤  outbox of changes, works offline ──> │  /api/v1   REST API, webhooks, import
              │                                       │
 dayhand ─────┤  command line and dayhand ui ───────> │  /auth     phone pairing and app sign-in
 AI agents ───┘  MCP, or dayhand with --json ───────> │  /cal      read-only calendar feed
                                                      └─ your own Dayhand server (Convex)

• The plan. Tasks with a day and an optional time, repeats, checklists, labels, links, reminders and a note. One task can be the now task, with a note of where you stopped. Today shows what is overdue, the now task, today and what you finished today; the board has three columns (to do, in progress, done); deleted tasks wait 30 days in the trash. Every task has a number (#42) that is never given to another task.
• The apps. Android, macOS and Linux each keep the plan on the device, work offline and queue changes to send to the server in order when it can be reached. The command line (dayhand) and terminal UI (dayhand ui) need the server; they do not keep an offline plan or queue changes.
• The server. There is no hosted Dayhand service. You run the backend yourself: on your computer with one command, or on your own free Convex account (your own server). The Android, macOS and Linux apps also work with no server at all.
• The agents. Any MCP client, or any agent that runs shell commands, works on the same plan with its own key. Its changes are signed agent: <name>. Tasks can carry acceptance criteria and a plan, agents claim tasks for a while and finish them with proof (agents).
• You in charge. Agents ask before risky steps and you answer on the phone, one switch pauses every agent, a policy per key allows, asks for or denies each tool, work nobody asked for waits in an inbox, and a health report shows what needs a look.

Where to start

What exists and what is planned

Everything in these pages can be built and run from the source today. For package and download availability, see Install.

Pages that describe a planned piece say so where it matters, and give no command for it.

Help and feedback

Dayhand is a personal open source project (Apache-2.0) with no hosted service and no support promise. Issues on GitHub are for bugs you can reproduce and for feature ideas. Security problems go privately, never in an issue: see security.

The project was called Helm until backend 0.9.0 and CLI 0.10.0, and some old names keep working with a warning (renamed from Helm). The repository moved from maiarowsky/helm to maiarowsky/dayhand; the old addresses redirect.