Several terminals at once
One terminal, one session. What happens when the work spreads across three of them.
This is the normal state, not an advanced one. rememd does not own your terminals, so there is nothing to configure - you open as many as you like and connect each to whatever it should be writing to.
The two-line model
Sessions receive logs. Features receive intent.
A session is the record of one stretch of work: its events, and the log written at the end. A feature is where the thinking lives: the PRD, the notes, the plans, the tasks. The first is history, the second is instruction.
Everything else follows from that.
Handing work to another terminal
Write it to the feature, and let the other terminal read it with
get_feature_context. Never write into another terminal's session.
A session is one agent's record of what it did. Something dropped into it from outside is not part of that record, and the agent whose session it is has no reason to look there - it is writing to that session, not reading from it. The feature is the shared surface, and reading it is the first thing an agent does.
Terminal A: "Note that the retry header has to be parsed before the body,
or the backoff is wrong." → add_note on the feature
Terminal B: "What are we building?" → get_feature_context
→ the note is in the answer
Working a second feature without moving
attach_to_feature points your writes at another feature while this terminal stays
connected to what it was. detach_from_feature parks it, keeping the session.
Use it when a question about a neighbouring feature comes up mid-flow and opening a terminal for it would cost more than the answer is worth.
What is not enforced
None of this is a lock. rememd cannot stop an agent writing to the wrong place - the routing rules are instructions an agent honours, delivered at startup, and an agent that ignores them will write wherever it likes and rememd will store it faithfully.
Worth being plain about, because a rule described as a guarantee is trusted like one.
If two terminals end up disagreeing about where something went, the tool that shows you
the truth is where_was_i - it reads events rather than intentions.