Work that stays
where agents can find it.
Neram keeps projects calm and durable, with one optional Sprint for what matters now and the same context for people and agents.
npx neram login && npx neram mcpnpx neram daily --json
npx neram task add --project "Website" --title "Ship pricing" --json
npx neram sprint plan --task-id TASK_IDCopy, run, and your agent has the same Sprint context you do.
One focus across projects
Projects hold all work. An optional Sprint shows only what the team is focusing on now.
Same tools, two transports
Local stdio for dev, hosted HTTP with Clerk id_token for CI. Stable error codes either way.
Scriptable by design
Every command has --json. Pipe to jq, run in CI, or let your agent call it directly.
Kanban without theater
todo → inProgress → done with optional position, assignee, due date, and Sprint.
Clerk workspaces
Organizations are the tenant. Roles, members, and switching are Clerk-native.
Simple Sprint memory
History keeps the committed and completed counts; unfinished work returns to Backlog.
How it works
neram login opens Clerk OAuth (PKCE). Pick an Organization — that’s your tenant. Tokens go to OS keychain, fallback to 0600 file.
Start an optional 1, 2, or 4 week Sprint—or leave it open-ended—then choose a few Backlog tasks.
Agents call daily_brief, capture_task, move_task, complete_task via MCP — same identity you use in the browser.