Kristian WindandClaude Opus 5 dff86dd23d feat(api): projects, sections, tasks, quick add, views and live sync
Completes the MVP surface: project and section CRUD, task CRUD with
sub-trees, drag-and-drop ordering, the quick-add endpoint over the
natural-language parser, Today and Upcoming, search, sharing with roles,
an activity log and a WebSocket for live updates.

Permission checks are route middleware rather than a first line in each
handler, so an endpoint is guarded by where it sits instead of by the
author remembering. Anything the caller may not see answers 404, never
403 — a 403 confirms the thing exists. Visibility is enforced inside the
list query, so another user's project cannot be reached by filtering or
searching at it.

Ordering is a float, so a drop writes one row instead of renumbering the
list. When repeated drops into one gap exhaust the precision, the
section is spread out again and the move retried — in a separate
transaction, since the attempt that discovered the problem rolls back.

The connection pool is not 1: a single connection makes the pool a lock,
and a query run while an earlier result set is still open then waits for
a connection it is itself holding. The store now closes its rows before
querying again, and the pool leaves that mistake slow rather than fatal.

Co-Authored-By: Claude Opus 5 <[email protected]>
2026-08-16 23:44:55 +02:00

verdande

Self-hosted tasks and projects, shared with the people you share the work with.
One binary, SQLite inside it, deployed as a Rune in Yggdrasil Panel.


Verdande is one of the three Norns — the one who spins that which is becoming. Not what has been, and not what is fated to be: the thing you are in the middle of. Which is what a to-do list is.

Status

Early. The foundation is built and tested; the API and web interface are being written. See What works today.

Why this exists

Todoist Pro, self-hosted, on your own hardware, with your own data — and with the integrations that a hosted product will not build for you: a real CalDAV server, a mail-to-task address, and an MCP endpoint so Claude can work your task list directly.

What it does

  • Quick add that reads what you type. betal moms i morgen kl 10 p1 #Firma @regnskab becomes a task called "betal moms", due tomorrow at 10:00, priority 1, in Firma, labelled regnskab. Danish and English, mixed freely in one line.
  • Projects, sections, sub-tasks, labels, saved filters. List, board and calendar views.
  • Sharing. Internal users are created by an admin; anyone else joins through an invite link sent to their email. Owner, editor and viewer roles.
  • Live sync. A change made by somebody else appears without a refresh.
  • Recurring tasks as RRULE (RFC 5545), reminders, comments and attachments.
  • Standards, not homegrown formats. iCalendar and CalDAV, ICS feeds, OAuth2 with PKCE, OpenAPI 3.1, MCP, Web Push, Argon2id.
  • A PWA that works on a phone, installable, with swipe gestures and offline reading of what it has already cached.

What works today

Area State
SQLite schema, migrations, WAL Done, tested
Full-text search, Danish-aware Done, tested
Quick-add parser (Danish + English) Done, tested
Argon2id passwords, tokens, TOTP, recovery codes Done, tested
Project roles and permission checks Done, tested
HTTP server, health check, static hosting Done
REST API under /api/v1 Next
Web interface Next
Sharing, realtime, import/export, integrations Planned — see the roadmap

Search finds grøn when you type gron, because Unicode does not consider ø an accented o and a Danish-first app that cannot do this is broken for its own users.

Running it

As a Rune in Yggdrasil Panel

  1. Runes → Carve a rune (upload) and pick rune/verdande.yaml.
  2. Create a server from it.
  3. Set Public address to the address you will actually reach it on. verdande cannot work this out for itself — the host port is not chosen until the server exists — and invite links, password resets and calendar feeds are all built from it. {{PUBLIC_URL}} is the default and is usually right.
  4. Point the SMTP settings at your mail server. Leave the host blank and verdande shows invite links in the app instead of emailing them, which is fine for a single user and no use at all for sharing.
  5. Start it, open the URL, create the first account. That account is the admin.

With Docker directly

docker run -d --name verdande \
  -p 8080:8080 \
  -v verdande-data:/data \
  -e VERDANDE_BASE_URL=https://todo.example.dk \
  ghcr.io/kristianwind/verdande:latest

From source

go run ./cmd/verdande

Listens on :8080 and puts its data in /data, so for local work set VERDANDE_DATA_DIR somewhere writable:

VERDANDE_DATA_DIR=./data VERDANDE_DEV=true go run ./cmd/verdande

A plain go build produces the API without the web interface — the frontend is embedded only when built with -tags embedweb, so a clean checkout compiles without a Node toolchain installed.

Configuration

Everything is an environment variable; there is no config file. A Rune has nowhere to put one that the operator would ever see.

Variable Default What it does
VERDANDE_BASE_URL http://localhost:8080 The public address. Invite links, password resets and ICS feeds are built from it.
VERDANDE_ADDR :8080 Listen address.
VERDANDE_DATA_DIR /data Database, uploaded files and backups.
VERDANDE_SESSION_TTL 720h How long a login lasts.
VERDANDE_INVITE_TTL 168h How long an invite link stays valid.
VERDANDE_RESET_TTL 1h How long a password-reset link stays valid.
VERDANDE_SMTP_HOST — Blank disables outbound mail; invite links are shown in the app instead.
VERDANDE_SMTP_PORT 587
VERDANDE_SMTP_USER —
VERDANDE_SMTP_PASS —
VERDANDE_SMTP_FROM verdande@localhost Sender address.
VERDANDE_SMTP_STARTTLS true unless port 465 Port 465 is TLS from the first byte; everything else negotiates.
VERDANDE_SMTP_INSECURE false Skip certificate verification. For a self-signed internal mail server, and nothing else.
VERDANDE_DEV false Human-readable logs at debug level.

What lives in /data

/data
├── verdande.db      SQLite, WAL mode
├── files/           attachments
└── backups/         nightly snapshots, 14 days

Back up the whole directory. If you copy verdande.db on its own while the server is running you will get a database missing its most recent writes — the -wal file is part of it.

Roadmap

  1. MVP — auth, projects, sections, tasks, sub-tasks, priorities, due dates, quick add, Today and Upcoming, search, keyboard shortcuts.
  2. Sharing — invites, roles, assignees, comments, attachments, activity log, realtime sync, notifications.
  3. Pro parity — recurring tasks, reminders, filter queries, board and calendar views, durations, ICS feeds, templates, automatic backups.
  4. Import/export — Todoist CSV and official export in, CSV/JSON/ICS out.
  5. Integrations — CalDAV server, mail-to-task, Gmail, MCP server for Claude, and a provider-agnostic AI layer that also talks to a local model.
  6. Publication — documentation, landing page, open-source scaffolding.

Development

go test ./...          # everything
go test -race ./...    # what CI runs
gofmt -l .             # must print nothing

Commits follow Conventional Commits; releases are semver tags, which build and publish the image.

Non-goals

Karma and points. Team workspaces and organisations. Native apps. Mail integrations beyond Gmail and the forwarding address. Languages beyond Danish and English. A sync protocol of its own — CalDAV and the REST API are the sync.

License

Not yet chosen. MIT is the intention when this is published.

S
Description
No description provided
Readme MIT
60 MiB
Languages
Go 57.2%
Svelte 20.3%
JavaScript 19.3%
HTML 1.7%
Python 0.7%
Other 0.8%