Documentation
rememd is a menu bar app, a CLI, and a backend you run yourself. These pages cover how the three fit together, what a day of using it looks like, and how to stand up the third one on your own infrastructure.
Getting Started
What is rememd
What it keeps, what it deliberately does not, and why that distinction is the whole product.
How rememd is organised
Workspace, product, focus area, feature - what each level is for, and why context is attached to work rather than to a folder.
Your first session
Set up the hierarchy, connect a terminal, and close the loop - the whole cycle once, end to end.
Connecting your agent
What the setup wizard writes for Claude Code, Cursor, VS Code and Codex, where each config lives, and how to write one by hand.
Daily Use
Workflows
Backlog to feature
How an idea said out loud becomes a feature with a PRD and a spine of tasks.
Several terminals at once
One terminal, one session. What happens when the work spreads across three of them.
Sessions: main and feature
Which session a write lands in, and why an unconnected terminal records nothing.
Features with their own repos
When a feature lives in a repository of its own, and how the connection follows it there.
Data Model
MCP Reference
Reference
CLI reference
Every rememd subcommand, generated from the binary rather than transcribed from it.
Living in the terminal
The guide the command reference is not: what a day at the prompt actually looks like.
Edge cases and gotchas
The things that surprise people once, collected so they surprise you never.
File layout on disk
Where everything is written, in a folder you can open, grep and version.
Team & Remote
Working with a team
What changes when the context stops being only yours.
Where each workspace lives
A home is a level in the tree: this Mac, your box, the team's box, each with its workspaces under it.
Host it yourself
Stand up a backend your team can join - a single binary, Postgres, and a domain. Written from the deployment that runs api.rememd.com.
Hosting options
Pick one level at a time, and know what the next one buys you.
Inviting teammates
Issuing an invite, what the guest gets, and managing members after.
How collaboration actually works
What is shared, what stays yours, and where the boundary is enforced.
Backups and recovery
A dump and a prune on a cron, and what to do when you need them.
Troubleshooting a box
When a box is unreachable or shows you the wrong person, in the order worth checking.