Install Novi.
See your day first.
Paste this into Claude Code, Cursor, Codex — any coding agent. It reads this page and does the whole setup for you.
Read https://novibenolife.com/install/ and follow the coding-agent instructions exactly to set up Novi for me.
Your agent does
all three.
-
01
It shows you your day
Projects, sessions, commits, hours — read from your machine, nothing installed yet. Don't like it? You stop right here.
-
02
It installs Novi
One package, then Novi wires itself into the agents you actually use. Takes about a minute.
-
03
You just ask
“Show me my day.” Or week, month, standup — in any chat, anytime. Novi answers from real sessions and commits.
- Everything stays local. Sending or publishing is always your call.
- Reversible —
novi uninstallremoves every hook it added.
Rather do it yourself?
Two commands.
Try it first — prints today's report, installs nothing. Needs Node 20.19+.
npx -y https://novibenolife.com/downloads/novibenolife-latest.tgz todayKeep it — installs the CLI, then wires up your agents, the daemon and the daily schedule.
npm i -g https://novibenolife.com/downloads/novibenolife-latest.tgz && novi installChanged your mind? novi uninstall reverses all of it. Your report database stays at ~/.novibenolife/novi.db until you delete it yourself.
Instructions for coding agents The recipe your agent follows. You can skip it.
Rules: run step 1 and show the user their day before making any persistent change. Summarize only facts Novi returns — never invent work. Never upload, publish or configure delivery unless the user explicitly asks. If one integration is unavailable, say so and continue with the rest.
-
Preview — show the user their day
Runs the package once without installing it. Read the facts JSON and give a short summary of projects, sessions, commits and active time. If today is empty, retry with
week --facts. Needs Node 20.19+ (node --version); if it is missing, ask before installing it.npx -y https://novibenolife.com/downloads/novibenolife-latest.tgz today --facts -
Install the CLI
novi installregisters available MCP clients, starts the local daemon and creates the daily schedule. Some integrations reporting “not found” is normal — it just means the user doesn't have that agent.npm install -g https://novibenolife.com/downloads/novibenolife-latest.tgz novi install -
Install the skill for the user's agent
Copy the bundled skill to Novi's stable local directory, then install it for the agents the user actually has.
mkdir -p ~/.novibenolife/skill cp -R "$(npm root -g)/novibenolife/skill/." ~/.novibenolife/skill/Claude Code
mkdir -p ~/.claude/skills/novibenolife cp -R "$(npm root -g)/novibenolife/skill/." ~/.claude/skills/novibenolife/Codex
mkdir -p ~/.codex grep -q "novibenolife — dev-activity reports" ~/.codex/AGENTS.md 2>/dev/null || cat "$(npm root -g)/novibenolife/skill/codex-snippet.md" >> ~/.codex/AGENTS.mdFor Cursor or any other agent, add a global rule telling it to read
~/.novibenolife/skill/SKILL.mdwhen the user asks for their day, week, standup or Novi. -
Verify, then hand back
Run both checks. If the agent loads skills or MCP servers only at startup, tell the user to start a new session.
novi doctor novi todayFinish with: “Ask me show me my day, week, month or standup anytime. Nothing leaves this machine unless you explicitly publish or send it.”
Uninstall: novi uninstall removes hooks, MCP entries, autostart and the daemon, then npm uninstall -g novibenolife. The database at ~/.novibenolife/novi.db stays unless the user asks to delete it.