Your first session

Walkthrough of a typical flow end-to-end.

1. Set up the hierarchy

• Create a workspace (e.g., "My Company")
• Create a product inside it (e.g., "Main App")
• Create a focus area (e.g., "Growth")

That is the whole of the setup by hand. A focus area can carry repo paths, and they are worth knowing about, but they are not a step here: they only give a bare tool call something to resolve against when nothing is connected. Step 3 connects the terminal explicitly, which is the normal path and the one that decides.

Features live inside the focus area, and this is where to stop clicking. You can add one in the panel if you already know exactly what it is, but the usual route is step 4: connect at focus area level, say what you are building, and let the agent create the feature with its PRD and its tasks in one go.

2. Capture some ideas

Optional, and one way in rather than the way in - something you are ready to build can go straight to a feature in step 4. The backlog is for the ones you are not ready to start, so they stop living in your head.

Open the product in the menu bar panel and go to its Backlog. Type into the field at the top:

# Add referral rewards

Users who refer 3+ friends get a free month of Pro.

It auto-saves. First line becomes the title, rest is description.

3. Connect a terminal

Run rememd connect in the terminal you want to work in, then pick the product, focus area or feature from the menu bar panel. All three are real targets, and you can name one outright instead of picking: rememd connect famnly -a Growth. Before any feature exists, the focus area is the target you want - it is what scopes the backlog and what a new feature gets created inside.

Nothing is written into your repo. The agent already running in that terminal picks the binding up on its next rememd call, and one started afterwards is handed the routing table at startup, before your first prompt. From then on every rememd call defaults to that target - you do not name the product or feature again.

4. Talk to your agent naturally

Try any of these:

• "What's in the backlog?" → the agent calls get_backlog, shows grouped list
• "We're adding referral rewards. Set up a feature for it." → the agent calls create_feature, writes the PRD from what you just described, and creates the tasks
• "Let's work on the referral rewards item - break it down" → same, starting from the backlog item instead of from the conversation
• "What should I work on first?" → the agent calls get_tasks, highlights the NEXT task
• "I just hit a bug - the session persists wrong" → the agent calls report_issue
• "Mark the first task done" → the agent calls update_task

Each of those defaults to whatever this terminal is connected to. You never pass a product or feature name unless you mean a different one.

5. Close the loop

End with "log this session", or just close the terminal - a session with real work in it is logged on disconnect either way. Tomorrow, "where were we" reads it back.