nxsflow

Issue tracker for coding agents — with the memory and the channel

Set the direction.Assign the ticket.Keep what they learn.

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 | sh

Set the direction.

You plan. Your agents file it.

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.

9v1yP1[epic]CSV export for the reports view
1n3rP1[feature]Write the CSV serializer
6rqpP1[feature]Export button in the reports toolbar

↳ blocked by: 1n3r

ne8wP2[chore]Document the export format

↳ blocked by: 1n3r

Assign the ticket.

You assign. Your agents build.

One message sets them to work through it in order, without you watching.

nxs — one message, then it runs
$ 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.

You correct. Your agents remember.

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.

$ nxm remember … --key csv-quoting

csv-quoting

Never strip CRLF inside a quoted CSV field — RFC 4180 allows it.

new session

$ nxm prime

csv-quoting

Never strip CRLF inside a quoted CSV field — RFC 4180 allows it.

One binary, three tools

What is inside the suite

One binary carries all three. Install it once; each workspace then activates only the products it actually needs.

nxf

flow

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.

nxm

memory

the memory

Durable project facts under stable keys — a fact is evolved in place instead of duplicated, and replayed into every session that needs it.

nxc

chat

the 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

An engine agents can trust

01

Offline-first by default

Everything lives in a local database, so reads and writes are instant and keep working when the network is gone.

02

Convergent CRDT sync

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.

03

Derived, never stored

ready, blocked, and next are computed deterministically from the dependency graph — so the work list is always consistent, never a stale cache.

04

Plugin-declared vocabulary

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.

05

--json everywhere

A deterministic, byte-stable machine surface on every command — the contract agents build on, and the measuring stick for the whole CLI.

06

One binary, one substrate

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.

Documentation

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.

Read the docs