Work together
Docs, tickets, and the board
Write the plan as a doc, break it into tickets, and move them across the project's board to done.
Work in Nexul usually starts with a doc: what you want and why. Tickets are the pieces of work cut from it, and the board shows where each one is. All three belong to a project, under its name in the sidebar: Board, Interview, Docs, Memories, and Settings.
Docs
Open Docs under the project. The list groups docs by folder, newest first, one line each with the time it was made; the Created menu in its header sorts by last edited instead, and each row then shows its last edit. Pin a doc from its row menu to keep it at the top. Pins and collapsed folders are kept in your browser, so they’re yours alone.
Before you open a doc, the space beside the list shows what is moving: Needs attention lists the docs a play is writing or waiting on an answer for, and the newest edits follow under Today, Last 7 days and Earlier, each with its folder, who started it and its first line. New doc sits at its top. The list’s search narrows it to one Matching list. On a narrow window the list fills the page, and the docs that need attention lead it.
Write in the editor with formatting, tables, task lists, and code blocks; type / for the block menu. A task list is - [ ] lines or Task list in that menu; click a box to tick it. A body you can’t edit shows its boxes ticked or empty but won’t toggle them. To size a table like a spreadsheet, drag a column’s right edge or a row’s bottom edge. On a tablet, tap a cell and drag the small bars on its right and bottom edges. From the keyboard, put the cursor in a cell and press Alt+Shift+Right or Left to widen or narrow its column, or Alt+Shift+Down or Up to make its row taller or shorter. A row still grows to fit taller text, and the sizes stay when an agent edits the doc. Several people can edit at once: you see who’s there and where their cursors are, and edits merge as you type. If an edit can’t merge, a banner offers Keep my version or Use server version.
- Mention with
@: a person, a ticket, or another doc becomes a live chip. Pasting a link to a ticket or doc in the workspace does the same. Mentioning someone tells them in their inbox. A chip you can’t open still shows what it points at, with a lock; it doesn’t open, and pointing at it says You don’t have access. - Times pasted as Discord codes, such as
<t:1792867165:F>, show in each reader’s own zone, as they do in chat. The body keeps the code: put the caret inside one to edit it. - Attach files by pasting, dropping, or
/then Image. The doc’s files are listed under the body. - Preview a file by clicking its name in the list, on a doc, a ticket or a memory. Images and SVGs show in place, PDFs open in the browser’s viewer, audio plays, and a CSV or TSV shows its header and first 100 rows. A SQLite database or any other type shows Download instead; so does a file over 10 MiB. Download is always in the preview’s header.
- Diagrams: a code block in Mermaid (a
```mermaidfence in markdown) draws its diagram under the code, in docs, tickets, memories and ticket notes alike. It redraws when you stop typing, and a diagram that doesn’t parse says why instead. Labels show as text only, so nothing written in a diagram can run in the page. - HTML pages:
/then HTML page starts a code block whose HTML runs as a page in the body (a```html-pagefence in markdown), for a chart, a mockup or a styled summary. While you edit, the page shows under its code and redraws when you stop typing; readers see only the page. It takes the app’s colours and fonts through CSS variables such asvar(--foreground),var(--card),var(--border)andvar(--brand), follows light and dark, and grows to fit what it shows. It runs sandboxed, so it can’t see your session or the rest of the doc, and its links open in a new tab. The phone app shows the page too, in the phone’s own fonts. - Watch with the eye button in the doc’s header; it shows the watcher count and is dimmed while you aren’t watching. Watchers hear about edits. You start watching a doc when you create it or save an edit, and Stop watching sticks until you choose to watch again.
- On this page lists a doc’s headings once it has two. On a wide window it sits to the right of the body and marks the section you’re reading; on a narrower one, the list icon in the header opens it.
Folders
Every doc lives in one folder of its project. New docs land in Main unless you start them from another folder’s +. New folder in the list header adds one, and a right-click on a folder starts a doc in it, renames it, deletes it, or opens its Permissions…, whose rules reach every doc in it (see People and access). Deleting a folder moves its docs to Main; it never deletes a doc. Main can be renamed, not deleted. Move a doc with Move to folder in its row menu.
Lock, clone, archive, and delete
The row menu, on a right-click, also has Lock, Archive, Clone, Permissions… for whoever can change the doc’s rules, and Delete.
- Lock makes the doc read-only for everyone, people and agents alike, until someone presses Unlock. Locking needs
docs:lock, granted apart from editing. Starting a doc play locks the doc too. - Clone copies the doc and its files into any project where you can write docs.
- Archive takes the doc out of the list without deleting it. Show archived in the list header’s menu swaps the list to the archived docs, each with Restore in its row menu, and the menu’s button reads Archived until you untick it. Archive and Restore need
docs:write, and the doc page’s menu has them too. - Delete is permanent. It’s refused while a ticket names the doc as its source; clear that ticket’s source first.
History
A doc keeps its versions, and History in the doc page’s menu shows them. Anyone who can read the doc can open it.
- What is kept. A save that changes nothing writes no version. A doc keeps its last 10 versions, plus any named version, which is never dropped. People editing together at the same time write one version per sitting, once the text has had no edits for 5 minutes or the last editor leaves, credited to everyone who edited.
- The dialog. The doc as it read is on the left and the Versions list is on the right, newest first on a timeline. Each version shows its time, how many words it added and removed, who made it, and the play or agent it came through; a named version leads with its name, and the newest says Current. Pick a version to read it next to the one before it: added words are tinted green, removed words are struck through in red, and a bar in the margin marks each changed run of paragraphs (grey for edited, green for added, red for removed). A paragraph added or removed as a whole sits on a tinted band.
- Stepping through the changes. The strip above the text names the picked version and the one it is compared with, and counts the changes (“1 of 2 changes”). The arrows beside the count, or the
[and]keys, move to the previous and next change. A version with no changed text says No text changes. As it was next to Changes (in the dialog’s header on a narrow window) turns the marks off to read the version as it was. The oldest version kept has nothing before it, so it shows without marks. The list is read when you open the dialog and does not update while it is open. - One version. A doc with only one version shows a small panel saying when it was saved and by whom; older versions appear after the next edit.
- Restore. Restore names the picked version’s time (“Restore 24 Oct 14:00”) and saves its title and text again as a new version on top, so nothing in the list is rewritten. It needs
docs:write, is disabled on the newest version, and a locked doc refuses it.
A ticket has the same dialog under History in its menu, for anyone who can read the ticket. The versions are the ticket’s description, and Restore puts an older description back (it needs tickets:write). Between the versions, in time order, each field that changed gets its own line: “Status In progress → Testing”, “Labels + security”, “Developer None → sam”. Hover a line to see who made the change, the play, automation or agent it came through, and when. The last line is Created. A ticket keeps its last 100 field changes. Field changes are only shown: they have no Restore, and nothing in the list sets a field back, so change a field on the ticket itself.
Docs and tickets share one rule for agents: a save an agent makes on a doc or ticket while a play you started is running on it shows the play’s name, such as Implement with AI. Any other save an agent makes for you shows as an agent.
Clarify a doc
When a doc is a rough idea, run Clarify via AI on it. The agent reads the doc and asks a round of questions about what it leaves open.
- Switch the doc to Questions. The number beside it counts questions waiting on an answer.
- Answer, skip, or add your own under Anything else?. Anyone who can edit the doc can answer, whenever they like.
- Press Continue via AI for the next round. The agent reads the earlier rounds too.
- When a round finds no gaps, the agent writes the answers into the doc. Press Close, then To tickets via AI to cut it into work; once it has, the doc’s tickets show there in its place. A closed doc shows a green tick in place of its icon in the doc list, until another round starts.
While To tickets via AI runs, a line above the doc counts the tickets it has written so far. When it finishes, the line says how many it wrote, with Open board beside it to go and see them. Whoever started the run also gets a notice in their inbox when it ends.
Once no question is waiting, Update doc via AI shows beside Continue via AI. It asks nothing more: it writes the answers so far into the doc, keeping the authors’ words, and puts what’s still open under Open points. It shows again if someone changes an answer after the doc was written.
The doc keeps its author’s words until one of those runs writes it. It’s locked only while a round runs.
On the phone app the same Doc | Questions switch sits under the doc’s title. Answer there the same way; someone who can only read the doc sees the questions and answers but can’t change them. Tapping a notice about questions opens the doc on Questions; any other way in opens it on Doc.
Tickets
Create a ticket with New ticket in a board column, or from a doc so the ticket keeps that doc as its source. Pick a type; its body template fills in the sections to write. A new project’s task has What needs doing, Acceptance criteria, How to verify and Out of scope; a feature opens with Why in place of the first; a bug has Steps to reproduce, Expected result, Actual result and Screenshots. Set a Developer to build it and a Tester to check it, both optional.
The ticket page has everything else. The line under the title shows where the ticket stands, on every tab: its key, its status, whoever acts next (the tester while it sits in a Testing column, otherwise the developer), its first open blocker and two of its pull requests, with a count for the rest. The properties and the sections below sit beside the ticket and its thread; on a narrow window they fold behind Details above the tabs.
-
Due date. Pick a day in the Due row of the properties; the × in it clears the date. Anyone who can edit the ticket sets or clears it, and anyone who can see the ticket sees it. The date is a plain day with no time or timezone. Agents set it with
due_ononticket_update(a date as2026-10-30, or an empty string to clear it) and find tickets by day withdue_fromanddue_toonticket_list. -
Links. The + adds Blocked by…, Blocks…, Found in…, or Source doc…. A blocked card shows an icon until every blocker has a merged pull request or is done, but still moves freely; a play on it asks you to confirm. A blocker that merged shows a merge icon, so a ticket can start on its code while the blocker waits in QA.
-
Development. Create a branch, or link an existing branch or pull request. A pull request links itself when its title or branch name carries the ticket’s key, such as
REF-42 Fix loginorfeature/REF-42-login, or its description closes it, such asFixes REF-42(closes, fixes or resolves), in any case; a description that only mentions a key, such as “live sync is REF-43”, links nothing; the key resolves in the workspace of the project that holds the repository, and a#42or a key matching no ticket links nothing. A branch or PR can link to more than one ticket. Point at a linked branch or pull request and press its × to unlink it, if you linked the wrong one; that needs permission to change the ticket, and the branch or PR itself is untouched. A pull request that still names the ticket in its title or branch name, or closes it in its description, links itself again the next time GitHub reports it. Agents unlink withunlink_prandunlink_branchonticket_update. -
Testing. In a Testing column it shows where to test and the acceptance criteria, with Pass and Fail. Fail asks for steps to reproduce, the expected and actual results, and a screenshot. It never points at production.
-
Thread. The ticket’s conversation, where plays post their runs and agents leave notes. Its three latest lines show under the description, with Open thread. It has its own tab beside Ticket, under the title; a link that ends in
/threadopens straight to it. Files posted in the thread are counted under Attachments, with a link to them, and a new message moves the ticket’s updated time. -
Notes. Shows once an agent has left a note on the ticket: the newest note opens there, and the list beside it opens any other. A link that ends in
/notesopens straight to it.
A ticket opened inside the Inbox has the same tabs.
Delete a ticket
The ⋯ in the ticket page’s header has Delete, for whoever holds tickets:delete. The confirm names the ticket. Deleting is permanent: the ticket goes with its labels, links, attachments and thread, and any ticket it blocked is no longer blocked. A ticket page returns to the project’s board afterwards; one opened inside the Inbox stays there.
Bugs
A bug is a ticket of the type named bug, and it always says which ticket it was found in. Use Report a bug on the ticket page to file one linked to it, or Report a bug in the board’s add menu, where you can mark the origin unknown. A done ticket is never reopened: a bug found later is a new ticket, listed on the done one under Found after done.
Finished
A ticket is finished once it has at least one merged pull request and none still open, even when the pull request is linked after it merged. Pull requests closed without merging don’t count. The default Ticket finished automation then moves it to its project’s Done status; see Automations.
Inbox
Inbox lists what happened to the tickets, docs, memories and stacks you follow, newest first, across the whole page until you open a row. Opening a row marks it read. Unread at the top right shows only what you haven’t read yet, plus the row you have open; All shows everything again, and the browser remembers your pick. To put a read row back as unread, so it stays bold and counts in your badge until you come back to it, right-click it and pick Mark unread. A doc’s notifications share one row, and so do a ticket’s, its play runs included; Mark unread puts the row’s newest one back. Agents use notification_update with unread: true.
A stack you watch adds a row when one of its services crashes and another when it comes back; opening the row takes you to the stack. Every reader of a stack watches it unless they turn off Watching on its page, see Watching a stack. A second crash while the first row is still unread lifts that row with the newer service’s name instead of adding another.
The board
Board shows one project’s tickets as columns. You design the columns, but each belongs to one of five stages, in order: backlog, progress, review, testing, done. Plays and automations read the stage, never the column’s name, so rename freely. Only done is final.
- Drag a card between columns to change its status.
- Group cards into swimlanes by category, such as a sprint. Dragging a card to another swimlane changes its category.
- The face at the end of a card’s key is whoever acts next: the tester while the card sits in a Testing column, otherwise the developer. A grey face means no one is set. Click it to pick someone, or No one, without opening the ticket (it needs
tickets:write). - A card shows a spinner and how long it’s been going beside its key while a play runs on the ticket, or while
@Agentanswers in its thread. Once that turn ends, a pulsing amber dot stays there while something the agent started keeps running in T3 Code, such as a test run it watches or a helper agent. Nexul hears this while the computer’s owner has Nexul open. - Filter by category, label, type, and status, or Search. Not blocked under Blockers hides the cards still waiting on another ticket. Needs answer under Plays keeps the tickets whose play stopped on a question for you.
- Playing narrows the board to tickets with a play running or waiting on an answer. It shows while at least one is.
Columns, categories, ticket types with their icons and body templates, and label colors are set per project, in the project’s Settings → Statuses, Categories, Ticket types and Labels. Each row says how many tickets it holds; a column or type that still holds tickets can’t be deleted, and its menu says so. New label on the Labels page makes a label before any ticket carries it, so it’s offered when tagging a ticket; a label no ticket carries can be deleted from its ⋯. Drag a column to reorder it within its stage, or a category within the list. A color can be any you like: drag on the color square and hue strip, type a hex, or take one of the quick colors (the arrow keys move through them, Enter takes one). It shows as picked in every theme, so check it reads on the palettes your team uses.