Ntwine

Glossary

The handful of terms Ntwine uses, and where each one is covered.

Ntwine doesn't have much vocabulary, but the words it does use mean something specific. Most of them link to the page that covers them in detail.

TermWhat it means
ProjectA directory you ran Ntwine in, with its own board at /project/<name>. One server holds all of them, and All projects shows them together.
ThreadOne effort, start to finish. The agent's session is the thread.
WorkerThe agent driving a thread: a real Claude Code, Codex or ACP agent process, running as you.
Sub-agentA helper a worker dispatches for one prong of its task, listed under its parent.
HandleA thread's short name, @port-the-parser, used to mention, read and message it. A sub-agent's is @parent.child.
The queueThe list of threads at rest that need you. A thread earns a card only when it wants a human.
BandsPinned, Queue, Running, Snoozed and Done. Every thread is in exactly one.
RestedAn agent that ended its turn and is waiting on you. A rested thread isn't idle; it's your move.
QuestionAn answerable choice an agent hands back, with numbered options and a recommendation.
StepsThings an agent needs you to do that it can't, with a Done button.
SnoozeHide a card until later, optionally with a follow-up prompt.
GoalA standing prompt a thread receives on its own, at every rest, on a clock, or both.
ScheduleA prompt plus a recurrence, in plain words. Each run starts a fresh thread.
Time limitA deadline on a thread that its agent plans around and the card counts down to.
SpinoffA new thread started from another, carrying its context.
Scratch directoryA thread's own folder, .ntwine/threads/<id>/, for its agent's notes and files.
NTWINE.mdAn optional file at your repo root, injected into every thread.