Everything that reaches you becomes one todo list.
Mail, chats, tickets, comments, appointments, letters and bank statements flow in —
Zeff derives what is yours to do, tells you why, and puts the button that finishes it right beside it.
Locally, on your machine. Nothing leaves it unless you say so.
Website · Download (alpha) · Extensions · Write a plugin · Licence · info@getzeff.com
Your day is spread over a dozen channels. Tickets in Jira. Mail in Outlook, Gmail and that old T-Online account. Chats in Teams, WhatsApp and Signal. Review comments in GitLab. Two calendars. A letter with a file number. A bank statement you keep meaning to look at. Somewhere in all of that is the one message you should answer today — and the promise you made last Tuesday.
You shouldn't have to turn that into a todo list by hand. Zeff does. It reads every channel, locally, and derives your todos from what actually comes in: who asked you for what, by when, in which message — and what already happened since. A reply you sent, a ticket that moved, a payment that arrived: the todo settles itself. What's left is one calm list, each item with its sources, its reason and a ready-made action.
Outlook · Gmail · IMAP/POP3 ───┐
Teams · WhatsApp · Signal ─────┤ ┌────────────────────────────────────┐
Jira · GitLab reviews ─────────┼──► read · understood ───►│ Your todos │
Calendars · documents · bank ──┤ matched · deduped │ why · from where · by when · next │
Workspace · journal · agents ──┘ └────────────────────────────────────┘
Around that list sits everything you need to work it off: a mail client and chat view, a Notion-like workspace, AI agents that take todos over in your own repos, and a Studio to build whatever else you need.
- 📥 Every channel in, one list out. Todos are a derivation of everything that arrives — not another inbox to feed by hand.
- 🏠 Local first, for real. A server on
127.0.0.1, a desktop launcher, one SQLite file per account. No cloud account, no OAuth app to approve: connectors read the web apps you are already signed in to. - ✋ It never acts behind your back. Automatic steps only read and propose; every write — a message, a comment, a booking — happens on your click. A test enforces it.
- 🤖 Agents that actually work. Claude Code, Codex and Copilot run on your todos with live sessions, worktrees, diffs and delivery — and they can ask you when they need a decision.
- 🔒 Privacy you can see. Every source and database carries a sensitivity (open, personal, secret) that the AI, the knowledge server, agents and MCP all respect.
Sample data — people, mails and chats made up for the demo.
![]() Today — where to start, who's waiting for you, the actions ready to go. |
![]() Every inbox, one place — mail and chats in one list, a tab per channel. |
![]() |
![]() |
On your phone All of Zeff at app.getzeff.com, straight from your PC over an encrypted peer-to-peer connection — no cloud in between. Pair it with a QR code from the launcher, tick todos offline, and talk to Zeff in the chat: it makes todos, writes notes and looks things up for you. |
Everything in Zeff is an extension (a plugin) you turn on or off on Menu → Plugins. Each has a page in the docs with what it does, how to set it up, its settings and screenshots — follow the link. All of them: docs/extensions.
| Extension | Highlights |
|---|---|
| Todos | Derived from every channel, not typed · each says why, from where, by when · settles itself when the source shows it is done · one-click actions · hand it to an agent |
| Mail & Chat | One inbox for mail and chats · a real mail client and chat view · replies over the account's own SMTP · AI review turns what needs you into todos |
| Calendar | Your calendars plus Outlook and Google in one week view · free slots for meeting suggestions · meetings become time entries |
| Agenda | Notes on a timeline, in projects · pin, tick off, tag · reminders and today's events |
| Timeline | One log across all sources, tied to people, tickets and projects · a marker for what is new |
| Open loops | Promises both ways, unanswered questions, requests · loops close by themselves |
| News | Your feeds scored for your interests · muted words, trusted sources · a daily overview |
| Extension | Highlights |
|---|---|
| People | A profile for everyone who matters · what Zeff knows across sources · dates with reminders · duplicates merged everywhere |
| Organisations, projects & places | Known under every name your sources use · each gathers its people, tickets, mails, money and hours |
| Cases | One place per matter, held together by a file number · the other party, what is owed, the next deadline · a GiroCode to pay |
| Finances | Whom you owe and who owes you · payment plans and the months ahead · the day you are debt-free |
| Documents | Drop PDFs, Office files, pictures, audio · text extracted (scans and audio too) · searchable, a source of todos |
| Time tracking | Jobs and projects against your hours and absences · weekly and monthly reports · agents propose bookings |
| Correlations | What goes with what in your days (mood, energy, meetings, spending) · real statistics, told only when it holds |
| Knowledge | A searchable wiki and graph of your data and Confluence · what you should know right now · questions answered with the rows behind them |
| Extension | Highlights |
|---|---|
| Workspace | Pages and databases in a block editor · table, board, list, gallery, calendar, timeline, chart · formulas with units · tables that transform (table → transform → result, with data-flow marks, protection and a "calculated" look) · panels and Wrap · widgets the AI builds · pipelines, automations, agents · views of your own |
| Notebook | Code cells in any page: Python, Node.js, Rust — each language a plugin, Docker containers by default · inputs and a returned output other blocks and widgets use · read and write Zeff behind permissions you grant (asked while the cell runs) · sharedStorage across languages · .znb: a Jupyter notebook with Zeff's blocks on top · a sticky Run all |
| Studio (beta) | Flows on a canvas · sandboxed Node.js lambdas with a web IDE · lifecycles · apps in one click · permissions you grant |
| Lookups | Type a title, pick a suggestion: films, books, Wikipedia, web results become rows |
| Code | AI workers on your todos in your repos · live sessions you can steer · branches, diffs, pushes and merge requests on a click |
| Admin sessions (beta) | Live Claude sessions that run as Windows administrator |
| Jira briefing | Your Jira boards as Workspace boards, each card with the AI's view of where it stands |
| Extension | Highlights |
|---|---|
| LLM | The layer every AI task goes through · backend and model per task · your instructions and context |
| AI backends | Claude Code, ChatGPT (Codex CLI), GitHub Copilot CLI, local models (Ollama, LM Studio) |
| Auto actions | A ready-made action for every open todo · you review, adjust, click |
| Actions | The one-click buttons on todos and rows — writes only on your click |
| Extension | Highlights |
|---|---|
| Outlook · Gmail · IMAP / POP3 | Mail from your accounts, replies on your click |
| Microsoft Teams · WhatsApp · Signal | Chats read without opening them — no read marks, no blue ticks |
| Google Calendar · Google Drive · Google Keep | Calendars, a copy of documents and backups in your own Drive, your Keep notes |
| Jira · GitLab | Tickets, boards, merge requests and review comments as context for todos and workers |
| Revolut | Bank statements settle payments by themselves |
| Web search · Browser (beta) | The AI searches the web and reads or clicks through public pages |
| Time-sheet systems | Your booked week exported to Chrono and Punch |
| Extension | Highlights |
|---|---|
| Accounts | Work and private side by side, each with its own database, browser profile, AI backends and plugins |
| Backups | Encrypted daily ZIPs, rotation, restore in one click, optionally a copy in your Drive |
| Languages | English, German and Spanish, with dates and numbers in your format |
Safe by construction. Every source and database carries a sensitivity (open, personal, secret) that the AI, agents and MCP respect; automatic steps only read and propose — every write happens on your click (a test enforces it); code that reads or writes Zeff's data waits for a permission you give.
Download the archive for your system from the releases — it brings the launcher, its own Node and Zeff, built. No Node, npm or checkout needed.
| System | Archive | Start |
|---|---|---|
| Windows 10/11 x64 | Zeff-<version>-windows-x64.zip |
Zeff\Zeff.exe |
| Ubuntu 22.04+ x64 | Zeff-<version>-linux-x64.tar.gz |
Zeff/zeff |
| macOS | Zeff-<version>-macos-*.zip (when built) |
Zeff.app (unsigned: "Open Anyway" once) |
- Unpack it anywhere (on Windows not into
Program Files— Zeff keeps its data next toZeff.exe). - Start it and say yes to the one-time setup of
https://zeff(a hosts entry and Zeff's own certificate; without it Zeff runs onhttps://127.0.0.1:1337). - Follow Setup in the app: plugins, sign-ins, first data.
An update replaces the program and keeps the data (Windows app\data, macOS ~/Library/Application Support/Zeff,
Linux ~/.local/share/zeff). Every archive has a .sha256 next to it and a README.txt inside.
What your PC still needs depends on the plugins you turn on — the Plugins and Setup pages show ✓ / ✗ with a hint for each:
| For | Needs |
|---|---|
| Connectors that read web apps (Outlook, Teams, GitLab, Gmail, WhatsApp, Keep, Google Calendar) | a Chromium browser — Chrome, Edge, Brave or Chromium (CHROME_PATH overrides) |
| Work tab, Repos | git |
| Jira sync | uvx (uv) for mcp-atlassian, or any Jira MCP server via JIRA_MCP_COMMAND |
| AI | the Claude CLI, Codex CLI or Copilot CLI, signed in once |
| Scanned PDFs, audio | Poppler's pdftoppm; a transcriber such as Whisper |
External plugins are plain folders in Zeff's data folder. They appear under Menu → Plugins at once, and you turn them on there after seeing what they ask for — no rebuild, no restart.
plugins/my-plugin/
zeff-plugin.json ← what it adds, and what it may do
ui/index.html ← a view of your own, inside Zeff
rules.md ← rules every Work worker gets
A plugin can add rules for every worker, / commands, views in the sidebar or as a session tab, MCP
servers, event hooks on runs and todos, and drive Zeff through the API. Views run in a sandboxed frame behind
a permission-checked bridge; hooks have time limits and no shell. The one permission that can't be contained is
exec, and Zeff says so before you enable it — the trust model.
Start with the overview and the examples in examples/plugins/. Reference:
manifest · API · panels ·
hooks. npm run plugin:check -- <folder> validates a plugin. Integrations that must not live
in a public repo can be mounted as a git submodule under integrations/ — docs/integrations.md.
Every account has its own MCP endpoint; the /mcp page lists them with ready-to-paste config.
claude mcp add --transport http --scope user zeff http://127.0.0.1:9333/api/mcpAgents can book time (report_time, list_time_entries …), work on todos (list_todos, start_todo,
todo_context, finish_todo …) and search knowledge (search_knowledge). Each endpoint takes the token of its
account (Authorization: Bearer …, Menu → MCP).
Web apps you're signed in to Zeff (Next.js 16, 127.0.0.1) You
───────────────────────────── ─────────────────────────────── ─────
Outlook · Teams · Gmail · Keep ──► drivers (MCP over stdio, CDP) ──► SQLite ──► Today · Todos · Mail
WhatsApp · GitLab · Calendar syncs ─► Lage (AI) ─► todos per Workspace · People
Signal Desktop · Jira (MCP) knowledge server · agents account Work (agents) · MCP
- Drivers. Each connector is a small MCP stdio server (
src/plugins/<id>/driver.mjs) that attaches over CDP to the account's automation browser and reads the web app like you would. Sign-ins are yours — Zeff asks, never signs in itself. Signal is read from Signal Desktop's own objects, without opening chats or marking them read. - The Lage. Syncs feed an AI pass that turns new activity into todos, loops and reviews. Prompt changes are
checked with before/after evals on your own past decisions (
npm run eval, docs/evals.md). - Knowledge. A Next app of its own per account (
knowledge/) compiles each page once per version — summary, concepts, entities, relations — and answers searches and questions. - The launcher. Electron supervises Zeff and the knowledge servers, serves them as
https://zeffandhttps://knowledge.zeff, restarts them after a crash, and starts with the OS.
Stack: Next.js 16 (App Router, Turbopack), React 19, Tailwind CSS 4, Drizzle ORM + better-sqlite3, MCP SDK v2, Playwright over CDP, Electron.
npm install
npm run dev # on a free port
npm test # each test file on its own temporary database
npm run test:server # a disposable server: fresh database, free port, TTL
npm run e2e # the browser smoke suite
npm run deploy # typecheck, lint, tests, build, restart through the launcher, page probes- Migrations are written by hand:
drizzle/00NN_name.sql(statements separated by--> statement-breakpoint) plus an entry indrizzle/meta/_journal.jsonwith awhengreater than every earlier one. Don't rundb:generate— its snapshots are long out of date. - Risky writes are tested on a snapshot (
better-sqlite3backup(),DATABASE_PATH), never on the live database. - Writes only on a click is a test:
tests/safety.test.tsfails when an automatic step reaches a write. - A release is
npm run releaseon the system it is for (native modules): it builds a commit fromgit archive, packs the archive with its.sha256, then unpacks and starts it with a barePATHand checks pages, drivers, work hosts and migrations.npm run release:check -- <archive>runs that check alone.
src/app/ pages, API routes (api/mcp, api/ext/v1), server actions
src/plugins/<id>/ a built-in plugin: manifest, driver.mjs, server actions, UI
src/lib/ the core: entries, schedule, boards (the Lage), work, sync, mail, ext (external plugins)
src/db/ Drizzle schema, connections, accounts
knowledge/ the knowledge server
launcher/ the Electron launcher
docs/ documentation; docs/plugins is shipped with Zeff (/ext/docs)
examples/plugins/ plugins to copy
tests/ e2e/ node:test + tsx; Playwright smoke suite
Zeff is alpha. It is used every day, on Windows first; Linux builds are checked, macOS builds are not published yet. Expect rough edges, migrations and the occasional breaking change.
Zeff is provided "as is", without any warranty and without any liability. You use it entirely at your own risk. It can contain errors, lose or corrupt data, send or fail to send messages, miss or misread a todo, a deadline or a payment, and stop working when a service it reads changes. Zeff is no substitute for your own checks: what it derives, summarises or suggests — including anything the AI writes — may be wrong. Connectors that read third-party services (WhatsApp, Signal, Teams, Outlook and others) may break those services' terms of use and can lead to your account being restricted; using them, and getting the permission of your employer or IT department where needed, is your responsibility. Keep backups.
To the extent permitted by applicable law, the author accepts no liability whatsoever for any damage arising from the use of or the inability to use Zeff. Mandatory liability that cannot be excluded by law (under German law: for intent, gross negligence and injury to life, body or health) remains unaffected. See sections 15 and 16 of the AGPL.
Zeff is free software under the GNU AGPL-3.0: use it, at home or at work, change it and share it, as long as what you pass on (or offer over a network) stays under the AGPL with its source. If that doesn't fit, for a closed product, a hosted service without publishing your changes or a company that can't use AGPL software, there is a commercial licence. How the two fit together is in LICENSING.md; contributions need the short agreement in CONTRIBUTING.md. Commercial licences and questions: info@getzeff.com. The landing page lives in site/ and is published to getzeff.com.




