kristianwindandClaude Opus 5
91671a4f97
Until now a note was shared exactly one way: file it in a shared project, and
everyone who could read the project could read the note. That is right when the
note belongs with a body of work and wrong when it is just "let Sofie see this" —
it made you stand up a project to hand over a single page.
A note can now be shared with named people directly, at viewer or editor — the
same two roles a project membership uses, so there is one idea of a role in the
program and not two. The paths stack: a note can be loose, filed, shared with
people, or any mix, and access is the most any of them allow.
The store:
- note_shares (migration 0030): note ↔ user ↔ role, one row per person, owner
recorded. Visibility (AllNotes, and search via mayTouchNote) widens to include
notes shared directly with the reader.
- the effective role folds a direct share on top of the owner and project paths.
The rules, drawn where they protect the owner:
- read = viewer, edit text = editor, on any path.
- MOVE a note (change its project) is owner-only: an editor filing it into a
project the owner is not in would take the owner's own note away from them.
- DELETE is owner or project-editor — a direct share, however high its role,
does not reach to throwing the note away.
- SHARE and UNSHARE are the owner's alone, like a project's invitations.
- the picker is everyone on the instance (a closed, invited set) minus who is
already on the note; a made-up id and the owner themselves are refused.
The list:
- a "Delt med mig" group at the top, collapsible, that appears only when it has
something in it — the same rule Favoritter follows — so it costs nothing when
you share nothing. A shared note lives there, not also in a time bucket.
- every shared note carries a small chip in its owner's avatar colour, the
project mark's shape said for a person.
- no star or archive button on a note somebody else owns: those change the note
itself, and it is not yours to put away.
- the editor grows a "Del med personer" panel for the owner: who can see it, at
what role, and an add row drawn from the instance's other people.
The old comment in the notes footer argued against a note having an access list
of its own. That was the right call until the case it did not cover — sharing
without a project — turned out to be the one actually asked for. Updated to match.
Person now carries json tags, so a note's owner serialises as id/name/avatar_color
like every other person in the API rather than as Go field names.
Tests: a shared note reaches the other person marked and owned; a viewer reads but
cannot write; an editor writes but cannot re-share or delete; unshare removes
access and is owner-only; the candidate list excludes who is already on and the
owner; and a made-up id and self are refused. OpenAPI covers the three new routes.
Co-Authored-By: Claude Opus 5 <[email protected]>
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
All six phases are built. See What works today for what is tested and what is not.
Documentation: docs/, built with Material for MkDocs.
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 @regnskabbecomes 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, and foldable groups over the projects in the sidebar.
- Notes, beside the work. Rich text that is Markdown underneath — headings,
lists, quotes, fenced code. A note is shared by filing it in a project;
#projectand[[another note]]are links, and a task shows the notes that mention it. A zip of Markdown goes in — Obsidian, Bear, or Apple Notes through the exporter intools/— and comes back out the same shape. - Drag where it means something. Reorder a list or a board, file a project under a group, drop a task on another project, or drop it on another day.
- Sharing. Owner, editor and viewer roles. There is no open registration: everybody arrives through an invite link, either to a project or — from Settings → Brugere — to the instance itself. Nobody's password is ever chosen by somebody else.
- 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
Every phase in the plan is built. You can install it, add tasks by typing a sentence, share projects, watch somebody else's changes appear live, set repeating chores and reminders, save filters, import your Todoist account, sync two-way with Apple Reminders, forward mail into it, and add it to Claude as a connector.
| Area | State |
|---|---|
| SQLite schema, migrations, WAL | Done, tested |
| Full-text search, Danish-aware | Done, tested |
| Quick-add parser (Danish + English) | Done, tested |
| Argon2id passwords, sessions, TOTP, recovery codes | Done, tested |
| Project roles and permission checks | Done, tested |
| REST API: projects, sections, tasks, sub-tasks, ordering | Done, tested |
| Today, Upcoming, search, activity log | Done, tested |
| Waiting on others: what you have delegated, by person | Done, tested |
| Assignee shown on every task that is somebody else's | Done, smoke-tested |
| Activity log, visible per project | Done, smoke-tested |
| Change a member's role without removing them | Done, tested |
| Sharing: invites, roles, members | Done, tested |
| Live sync over WebSocket | Done |
| Web interface: sign-in, views, quick add, ⌘K, shortcuts | Done |
| Task detail: description, sub-tasks, comments, files, reminders | Done |
| Settings: account, notifications, integrations, AI, tokens, data | Done |
| Device list: where you are signed in, and signing one out | Done, tested |
| User administration: invite to the instance, promote, remove | Done, tested |
| Server errors kept in the database, readable after a restart | Done, tested |
| PWA icons: PNG for launchers, apple-touch-icon for iOS | Done, smoke-tested |
| Invite and password-reset links that open the right page | Done, smoke-tested |
| Drag to reorder, in both the list and the board | Done |
| Drag a task to another project or another day | Done, smoke-tested |
| Foldable project groups in the sidebar | Done, tested |
| Month view on Upcoming, not only per project | Done, smoke-tested |
| Recurring tasks (RRULE, Danish + English) | Done, tested |
| Reminders, absolute and relative | Done, tested |
| Saved filters with a query language | Done, tested |
| Board and calendar views | Done |
| ICS calendar feed, task durations | Done, tested |
| Project templates | Done, tested |
| Nightly backups with rotation | Done, tested |
| Comments, attachments, notifications, Web Push | Built |
| Notes: rich text, Markdown on disk, links to projects, notes and tasks | Done, tested |
| Notes in and out: a zip of Markdown, both directions | Done, tested |
| Todoist CSV import and export, account export | Done, tested |
| MCP server for Claude | Done, tested |
| CalDAV server (two-way VTODO) | Done, tested |
| Mail-to-task | Done, tested |
| AI layer (Anthropic/OpenAI/Google/local) | Built, degrades when unconfigured |
| Gmail: OAuth2 with PKCE, polling, one-way to tasks | Done, tested |
| Google Calendar: read-only, laid over the task calendar | Built, never run against Google |
| Calendar subscriptions: ICS and webcal, several per person | Done, tested |
| Times on tasks, set by dragging in the week grid | Done, tested |
| Notes: archive, grouped list, images, source view | Done, tested |
| Update notice for administrators | Done, tested |
| Personal API tokens | Done, tested |
| OpenAPI 3.1 spec, checked against the router | Done, tested |
| End-to-end smoke tests (Playwright) | Done |
| Documentation, landing page, licence | Done |
Not finished: Web Push, the AI providers and the Google Calendar API calls are implemented against their specifications and have only ever been exercised there, not against live services. Gmail is no longer in that list — it runs in production, including the flagging and de-duplication that took a day to get right. Calendar subscriptions over ICS and webcal are proven; the Google half of the calendar is not. Everything else has an interface: opening a task shows its description, sub-tasks, comments, files and reminders, and the settings pages cover the account, notifications, integrations, AI, API tokens, import, export and templates.
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.
What it looks like
 |
 |
| Board view — one column per section. | The light theme. |
 |
 |
| A week at a time, so a task can be dragged across a month boundary. | A task, opened: description, priority, labels, sub-tasks and its files. |
 |
 |
| Notes, filed in a project to share them. | The same note as its source — which is what the export writes to disk. |
 |
 |
| Five themes and four looks: how bright, and how it reads. | What has been done on the server. |
Regenerate these with node scripts/generate-screenshots.js from web/. It starts
the real binary, creates its own account and a second one to share with, fills them
with demo data and photographs fourteen surfaces — nothing to set up and nothing to
remember. (go run ./tools/shots still works, and is the way to photograph an
instance that is already running.)
Running it
As a Rune in Yggdrasil Panel
verdande is built to be deployed as a Rune in Yggdrasil Panel — that is its home, and the manifest ships in this repository. It runs anywhere Docker does as well.
- Runes → Carve a rune (upload) and pick
rune/verdande.yaml. - Create a server from it.
- 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. - 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.
- 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_GMAIL_CLIENT_ID |
— | OAuth client from Google Cloud, if anyone will connect a mailbox. |
VERDANDE_GMAIL_CLIENT_SECRET |
— | |
VERDANDE_UPDATE_CHECK |
false |
Ask GitHub whether a newer release exists. Sends nothing about your instance. |
VERDANDE_PANEL_URL |
— | The Yggdrasil panel this instance runs under, so it can ask to be restarted from its own settings. |
VERDANDE_PANEL_TOKEN |
— | An API token from that panel, belonging to somebody with control of this server. |
VERDANDE_PANEL_SERVER_ID |
— | Which server to restart — the id in the panel's URL. |
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
- MVP — auth, projects, sections, tasks, sub-tasks, priorities, due dates, quick add, Today and Upcoming, search, keyboard shortcuts. (done)
- Sharing — invites, roles, assignees, comments, attachments, activity log, realtime sync, notifications. (done)
- Pro parity — recurring tasks, reminders, filter queries, board and calendar views, durations, ICS feeds, templates, automatic backups. (done)
- Import/export — Todoist CSV and official export in, CSV/JSON/ICS out. (done)
- Integrations — CalDAV server, mail-to-task, Gmail, MCP server for Claude, and a provider-agnostic AI layer that also talks to a local model. (done)
- Publication — documentation, landing page, open-source scaffolding. (done)
Development
go test ./... # everything
go test -race ./... # what CI runs
gofmt -l . # must print nothing
Working on the interface means two processes: the API on 8080, and Vite on 5173
proxying /api to it, so the session cookie stays first-party exactly as it is in
production.
VERDANDE_DATA_DIR=./data VERDANDE_DEV=true go run ./cmd/verdande
cd web && npm install && npm run dev
To run the whole thing as one binary the way it ships:
cd web && npm run build && cd .. && cp -r web/build cmd/verdande/webbuild && go build -tags embedweb -o verdande ./cmd/verdande
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
MIT. See CONTRIBUTING.md and SECURITY.md.