Docs

Neram is a project and task workspace where Clerk Organizations are the canonical tenant. Projects hold the work; one optional Sprint shows what the team is focusing on now. Browser, CLI, and MCP share the same model.

CLI reference

Every command, every --json payload.

MCP reference

Local stdio and hosted Streamable HTTP.

Quickstart

npx neram login          # Clerk OAuth (PKCE); choose an Organization
npx neram doctor --json  # config, auth, and MCP readiness
npx neram whoami --json  # identity + active Organization + workspace totals
npx neram daily --json   # compact execution digest

neram login opens the browser, returns to a loopback 127.0.0.1 callback, and stores the Organization-bound token in the OS keychain with a chmod 600 fallback at ~/.config/neram/credentials.json. Switching workspaces reruns OAuth and requires MCP reconnection.

What is a Sprint?

A Sprint is an optional organization-wide focus window, not another home for tasks. Choose 1, 2, or 4 weeks—or no fixed end—then add a few Backlog tasks. Ending saves committed/completed history and returns unfinished work to Backlog.

Three surfaces, one model

Web

Kanban board, Focus view, task detail.

CLI

neram on npm. Human text by default, --json for agents.

MCP

Local stdio or hosted HTTP. Same tools, same auth.

Config

CLI loads public config from /.well-known/neram-agent.json. Override only for local dev with NERAM_CONVEX_URL, NERAM_CLERK_FRONTEND_API_URL, NERAM_CLERK_OAUTH_CLIENT_ID.