Reference
Limitations
An honest list of what is not available yet, so you know the limits before relying on it.
Agent
- DeepSeek is the only model provider so far.
- There is no automatic contradiction check yet; contradictions can be asked about through the chat.
- The Markwork agent only touches Markdown files in the work folder. Running commands is only done by an external harness from a kanban card.
- A batch has at most 20 actions. Moving a file does not update links in other files; the agent must propose that separately.
- The search is keyword-based (BM25), not meaning-based;
search_textdoes not recognize synonyms. - The Git tools only read what has been committed.
- Undo restores a deleted file from the journal snapshot, not from the Trash.
- The conversation history cannot be searched from the panel yet; search the files in
.markwork/chats/. - The token estimate is rough (3 characters per token).
External harness
- Only pi so far. The run status (queued, working, log) only exists while the app is open.
- A card is recognized by its text, so editing the title of a card that is being worked on breaks its status.
- A question is recognized by a
?at the end of the answer. - The
[[ ]]notes on a card are copied only at Work on it with pi; Reply to pi does not copy them again. At most 10 notes, 8,000 characters per note and 24,000 in total. On the board, a link to a note that does not exist is shown the same as a normal link. - Without a permission extension such as
permission-gate, all the pi tools run right away. - There is no worktree per card, interactive terminal, or diff view of the harness result in Markwork yet.
The kanban board
- Only top-level list items become cards.
- There is no archive or label editing through the interface yet; write
#tagin the card title. - Moving a card with the keyboard is only possible through the right-click menu.
Home
- Due dates and the inbox are only read from the open work folder (at most 300 Markdown files).
- Clicking a task opens its board without highlighting its card.
- Recent files are recorded by Markwork itself, not through the GNOME recent files list, so they do not appear in other apps.
The daily journal
- One fixed journal folder (
journal/in the work folder) with a fixed template; it cannot be set in Preferences yet. - Activity is only recorded while Markwork is open and only for the open work folder. Cards moved by editing the board text, or boards changed outside Markwork, are not recorded (their commits still appear).
- Activity is merged when the journal is opened with Ctrl+Alt+J or from Home, not while the journal is open. Opening the journal file from the file tree does not merge it.
- Commits are recognized by their short hash: an amended or rebased commit can appear twice. Commits on other branches are not included.
- Undoing an agent change is also recorded as an agent change.
The editor and export
- An animated GIF only shows its first frame; an image changed on disk is reloaded after the app is opened again.
- Long table cell text is cut with “…”, and the contents of a cell are only one line.
- There is no side-by-side view or tab reordering by dragging yet.
[[ ]]links: there is no backlinks panel or graph yet; renaming or moving a file does not update the links that point to it; the![[ ]]embeds and the^idblock references are not supported yet; the[[suggestions are only file names, not headings yet.- HTML export does not embed local images and does not include the code block colors yet.
GNOME integration
- The interface is in English; the translation infrastructure (gettext) is in place, but no other language is available yet.
- It has not been tested in a Wayland session; the tests run on X11.
- Installing through Meson and the Flatpak build have not been tested. In Flatpak,
gitandpimust be available inside the sandbox. - The system accent color and the
Adw.ShortcutsDialogshortcuts dialog are only used on libadwaita 1.6/1.8 and newer; on older versions the default Adwaita color and a plain shortcut list are used. - A floating panel in a narrow window does not close when the editor is clicked; close it with its button.
The complete list is in the Limitations section of the README.