Status reports,writtenby the AIReported the moment a session ends. You just open the dashboard.See the demo dashboardNo sign-up. Demo data is ready.Claudethat didthe work.

Claude helped L Lin Xiao fix an idempotency bug in the refund callback.

Everyone on the team has an AI partner.

Nobody knows better what got done today.

When a session ends, the partner writes it up in one line
and sends it to your dashboard with the time and changes.

Gemini helped W Wang Ke backfill 30 days of daily-active data.

Codex helped C Chen Mo refactor the order state machine to be table-driven.

Five questions every boss asks.
One dashboard answers.

What your best people know,
written down.

Skills, inferred

Rules over the work summaries infer what each person is good at: debugging, refactoring, performance. Nobody fills in a form.

Bus factor, visible

When only one person solidly holds a skill, the dashboard tells you.

Export as SKILL.md

Export one person's way of working as a file, drop it into .claude/skills/, and everyone's Claude Code can follow it.

First, what is collected
and what is not.

Surveillance tools do not last. HeyBoss takes the minimum a roll-up needs, and the team can see all of it.

Reported

  • Tool, project folder name, session time and length
  • Number of turns, token usage
  • Files changed, lines added and removed, commits
  • A one-line summary (the session title, or the first 200 characters of the first prompt)

Never reported

  • Code or file contents
  • The full conversation
  • Keystrokes, screens, browsing history
  • Anything outside an AI session

Visible to the team

The collectors are a few dozen readable lines. Set HEYBOSS_DRY_RUN=1 to see the exact payload before anything is sent.

Your data stays yours

Self-hosted. The data is a JSON file on your own server and never touches a third party.

Never in the way

If reporting fails it is skipped silently. It never blocks or interrupts an AI session.

Three steps in,
automatic after.

1

Deploy HeyBoss

One Next.js app. Set HEYBOSS_TOKEN, start it, done.

HEYBOSS_TOKEN=secret npm run start
2

Install the collectors

A SessionEnd hook for Claude Code, notify for Codex. One line of config each.

# ~/.codex/config.toml
notify = ["node", "codex-notify.mjs"]
3

Open the dashboard

Sessions report when they end and the dashboard refreshes every 30 seconds. Anything else can POST to /api/ingest.

Full setup guide →

Questions people ask

Will the team feel watched?

That is why the boundary comes first: summaries and counts only, open scripts, and a preview of every payload. Tell the team what is collected before you roll it out. That matters more than any technical measure.

Do more sessions or more lines mean better work?

No. The numbers show where AI collaboration happens. They are not a performance score. HeyBoss replaces “what are you working on?”, not a ranking.

Which AI tools are supported?

Claude Code and Codex CLI have ready-made collectors. Cursor, Gemini CLI or anything else can POST to /api/ingest.

How are skills worked out?

Keyword rules over the work summaries, with the sessions behind each skill listed so you can check. Treat it as a lead, not a verdict.

What do I see before real data arrives?

Demo data. The dashboard switches over when the first real report comes in.

No sign-up. Look around with demo data first.Open the demo dashboard