nxfflow
the board
Issues, epics and the dependencies between them. ready, blocked and next are derived from the graph on every query — never stored, so the work list cannot go stale.
Issue tracker for coding agents — with the memory and the channel
Your agents keep forgetting where the project is going — and which rules it runs by. With nexus-flow, every new session starts knowing what's queued, what the rules are, and what's already been figured out.
Offline-first — fast locally, convergent when connected.
$ curl -fsSL https://nxsflow.com/nxs/install.sh | shSet the direction.
You plan the direction with your agents: it lands on the board as epics and tickets, and it stays there — across sessions and branch switches.
nxf — planning session
▸ Add a CSV export.
◂ One epic, three tickets. Two of them wait on the serializer — I put the dependency in.
↳ blocked by: 1n3r
↳ blocked by: 1n3r
Assign the ticket.
One message sets them to work through it in order, without you watching.
$ nxc send --to coder --ref nxf_ids=9v1y "work the queue"opened thread m-01M1X1HA7XZV7B2K7EWF5T4QPC in dm:fead28fb47b8$ nxf next9v1y P1 in progress [epic] CSV export for the reports view1n3r P1 open [feature] Write the CSV serializer$ nxf blocked6rqp P1 open [feature] Export button in the reports toolbar↳ blocked by: 1n3r (open)ne8w P2 open [chore] Document the export format↳ blocked by: 1n3r (open)$ nxf list --status closed1n3r P1 closed [feature] Write the CSV serializer$ nxf next9v1y P1 in progress [epic] CSV export for the reports view6rqp P1 open [feature] Export button in the reports toolbarne8w P2 open [chore] Document the export format
Keep what they learn.
Something goes wrong, you say why once, and the rule outlives the session that earned it.
nxm — what outlives the session
check failed · 1n3r — Write the CSV serializer
csv: line breaks inside a quoted field were stripped
▸ RFC 4180 allows CRLF inside quotes. Never strip it.
csv-quoting
Never strip CRLF inside a quoted CSV field — RFC 4180 allows it.
new session
csv-quoting
Never strip CRLF inside a quoted CSV field — RFC 4180 allows it.
One binary, three tools
One binary carries all three. Install it once; each workspace then activates only the products it actually needs.
nxfthe board
Issues, epics and the dependencies between them. ready, blocked and next are derived from the graph on every query — never stored, so the work list cannot go stale.
nxmthe memory
Durable project facts under stable keys — a fact is evolved in place instead of duplicated, and replayed into every session that needs it.
nxcthe channel
Messages between you and your agents, on the record in the same change-log: a message hands the work on, and the answer comes back to whoever asked — no scraping each other's output.
Why it's built this way
Everything lives in a local database, so reads and writes are instant and keep working when the network is gone.
Each change is appended to a change-log, never overwritten. When devices reconnect, every one folds to the same result: edits to different fields both survive, and two edits to the same field go to the same winner everywhere.
ready, blocked, and next are computed deterministically from the dependency graph — so the work list is always consistent, never a stale cache.
Item types, ranking, and presentation live in plugins — an issue tracker and a personal to-do ship in the box; you can declare your own.
A deterministic, byte-stable machine surface on every command — the contract agents build on, and the measuring stick for the whole CLI.
flow, memory, and chat share one local database, one sync, and one change-log — so an agent's plan, its memory, and its messages converge as one truth.
What we build on it
nexus-flow is what NexusFlow UG builds its own products on. Both stand on the same engine: the same board, the same memory, the same channel. Even the engine is built on its own boards.
The workshop where you design and your agents forge — from roadmap through build and review to release. You lead, they ship.
From intent to shipped.running knowledge-work projectsnexflow.itA companion for knowledge work — like a personal Chief of Staff. It prepares your day, captures every conversation, and keeps the thread so nothing slips.
From 'someday' to done.Guides for the whole suite — getting started, core concepts, the command reference, plugins. The same documentation the CLI serves, so the two never drift apart.