Getting started

org keeps track of what needs doing, who owns it and when it needs to happen. Use it on your own, with a team or with an agent. Tasks is the main workspace; you can start with a single task and organise it later.

It costs £5 a month for each human. Agents are free.

Your work loop

1. Add a task. Open Tasks and choose New task. Write what needs doing in Capture and save it to Inbox, or choose a project page if it already belongs to one. Nothing is added until you submit the form.
2. Organise and schedule. Give the task an owner, priority or tags when they help. A scheduled date says when you plan to work on it; a deadline says when it is due. Switch Tasks to Agenda to see dates, or keep the list, board, table or gallery layout. These are views of the same work.
3. Do it and mark it done. Open the task for its notes, checklist and subtasks, then change its state to a done state, normally DONE. Its history remains available. Add the next thing you need to do and repeat.

Inbox is for work you have captured but have not organised yet. You do not need an agent or a project before you can add and complete tasks.

Projects and notes

A project groups related tasks and notes on an ordinary page. Open Projects to create one, then use its New task action to keep work on that page. You can add background notes, links and headings alongside the tasks. Assigning a team to the project's tasks sets ownership; collaborators still need access to its space.

For shared work, an administrator can create a team, add accepted members and give it Editor access to the project's space. The creation form shows any access change before you submit it. You can also keep standalone tasks in Inbox without creating a project.

Optional agent help

An agent can read and update the same tasks and notes, through MCP or the API, within access and review limits you choose. You can connect one after you have started using Tasks. Agent work that needs review appears in Review; it does not add a review step to every task you complete yourself.

org sits alongside an agent's memory and chat. It keeps the exact record of work and decisions; there is no chat inside org. When an agent needs your say-so, it asks in its own interface and org records the answer.

A few principles shape everything:

• Building blocks, not a method. States, dates, properties, tags, queries, views and templates. org never tells you how to work: no streaks, no capped lists, no built-in productivity system.
• Text is the source of truth. Every page is a Markdown file you can read, sync to a folder and edit in Neovim.
• Complete without an agent. Everything an agent can do, you can do in the app, and the other way round.
• Access is enforced, behaviour is guided. Who can see what is enforced on every request. What an agent should do on a task is guidance you write, and it's shown to the agent every time.

One account across aegent.dev

You sign in once, at aegent.dev, with a passkey, Google or an email link. The same account works for org and for every other aegent.dev product, and account settings live in one place.

Access you give an agent is for one product only. An agent connected to org can't act anywhere else unless you connect it there too, and the consent screen always says which product you're granting.

Hats

An org is a boundary for ownership, billing and short IDs. You get a personal org when you sign up, and a household or a business is an org too. A hat is how you see each org you belong to: Personal, Household, Acme.

Switch hats from the sidebar. Each hat has its own colour and order, and you can hide one at set times: Acme after 18:00 and at weekends, for example. A hidden hat leaves the switcher and holds its notifications until it's visible again, but it still opens if you go to it. The "All hats" views show your agenda and tasks across every org, labelled by hat; nothing is ever copied between orgs.

Spaces

A space controls access to a group of pages. A project groups related work and notes on a page; it lives inside a space. You can keep several projects in one space when the same people should have access. Changing a task owner does not change who can read or edit it.

Spaces have these visibility settings:

A space can also be marked humans only, so no agent can ever read it, whatever it's been granted. Roles in a space go viewer, commenter, editor, manager.

Pages

A page is a Markdown document in a space, and pages nest. Headings are entries; a heading that starts with a keyword like TODO is a task:

## TODO [#A] Renew car insurance #admin

deadline:: <2026-10-12 Mon -3d>
owner:: @daniel

Compare at least three quotes before the renewal date.

Pages link with [[wikilinks]], embed files and other pages, and can hold live queries, tables with formulas and code blocks. The aegent Markdown reference has the lot.

Tasks

A task has a state from its TODO sequence, and optionally a priority, tags, a scheduled date, a deadline, an owner, an effort estimate and a checklist. org works out where each task stands: ready, blocked, being worked on, waiting for review, on hold, done or cancelled.

Agents can work from the same queue: claim a task, work on it and submit evidence for review. An agent you trust can also complete eligible tasks directly when you enable that permission; explicit required review still applies. Tasks and workflow explains how.

Short IDs

Everything in an org has a short ID, like a78: pages, tasks, comments, files. They're short enough to say out loud, stable when things move, and they grow a character at a time as the org fills up. Any short ID works as a link ([[a78]]), in search, and in a URL: https://aegent.dev/org/daniel/a78.

Short IDs are what you and your agents use to talk about things. "Can you pick up a78?" is enough.

Next steps

• Tasks and workflow
• Connect an agent when you want help
• Bring your things over with your agent
• Learn the keyboard