Know what every developer worked on, and who needs a hand
See what everyone worked on, in plain words
Every card carries an AI-written summary of the work itself, not a count of prompts and commits, and a status that shows who is moving and who needs help. Filter by status, then open a card to see the full profile.
Stuck, active, exploring or idle, with the reason why
Every developer gets one of four statuses, worked out from their prompts, session summaries and commits. Each one comes with what triggered it, so a lead knows exactly where to help.
- Stuck
The same problem keeps coming back across prompts and sessions, and nothing committed has solved it yet.
How it is detected
- One problem repeated over several prompts or days
- An open question or blocker in the session summaries
- Lots of AI work on a ticket with no commit that closes it
What to do: Answer the open question, pair them with someone who knows the area, or bring in whoever has to decide.
- Active
Steady sessions and commits that move the ticket forward, day after day.
How it is detected
- Regular sessions that end in a summary
- Commits linked to the work in progress
- Problems that come up are solved the same day
What to do: Leave them to it, and recognize the progress so the rest of the team sees what works.
- Exploring
Reading, asking and prototyping in new code or a new tool, with few commits so far. Normal at the start of new work.
How it is detected
- Many questions about code they have not touched before
- Prototypes in scratch branches
- Few or no commits yet
What to do: Point them to the Knowledge Base and the teammate who knows the area, so exploring turns into shipping sooner.
- Idle
No AI sessions or commits in the selected period.
How it is detected
- No sessions recorded on any machine
- No commits in the selected period
- Shown with the date of their last activity
What to do: Check in without assumptions. Idle can mean leave, meetings, work that needs no AI, or an agent that stopped syncing.
How serious is stuck?
- Stuck · Low
- The same problem came up again within a day.
- Stuck · Mid
- Two days on one problem, or a blocker waiting on someone else.
- Stuck · High
- Three days or more, or work blocked until a decision is made.
One profile with the whole story
The week in numbers, an AI summary of the work, a day-by-day breakdown with every blocker the developer hit, and the badges they have earned. Pick a developer to switch profiles.
Alex
Backend engineer · payments-api
- Prompts
- 13
- Commits
- 6
- Active hours
- 9.2h
- Sessions
- 4
AI summary, last 7 days
Working on PAY-482, proration for plan changes. Upgrades and same-cycle downgrades are built and tested. Annual-to-monthly downgrades are blocked: the prorated credit can be larger than several monthly invoices, and product has not decided how to handle it. Both options are ready behind a flag.
Daily breakdown
Thu, Oct 83 prompts · 1 commits · 1.8h
- Narrowed the options with product to a capped carry-over or a partial refund.
- Built both behind a feature flag, so the decision can ship without another dev cycle.
Stuck · Mid: Waiting on product to choose between a capped carry-over and a partial refund. Both are ready behind a flag.
Wed, Oct 70 prompts · 2 commits · 1.1h
- Pushed 2 commits without an AI session: test fixtures for annual plans.
Stuck · High: Capping the credit costs the customer money, not capping it leaves negative balances. No decision yet.
Tue, Oct 66 prompts · 3 commits · 3.4h
- Shipped proration for upgrades and same-cycle downgrades, with tests for monthly and annual plans.
- Found that an annual-to-monthly downgrade can create a credit bigger than three monthly invoices.
Recognition that follows real work
Badges are earned automatically from activity, and teammates can give each other kudos for work they noticed. Developers level up as they go, so good habits get seen by the whole team.
Milestones
- First sessionRan a first AI coding session.
- First commitShipped a first commit from an AI session.
- 30 days inA month of working with CloudByte AI.
- 1-year anniversaryA full year of AI-assisted work.
Streaks
- 3-day sparkAI work on 3 working days in a row.
- 7-day blazeAI work on 7 working days in a row.
- 30-day runAI work on 30 working days in a row.
Craft
- Deep focusA long session that ended in finished, committed work.
- Prompt proPrompts that rarely need a follow-up to get it right.
- Commit machine50 commits that came out of AI sessions.
Team
- Monthly top coderMost finished work on the team this month.
- Team favouriteMost kudos from teammates this month.
Recent recognition
Your team, this week
Priya earned Monthly top coder for the most finished work on the team in September.
Maya earned Deep focus for the session that cut the reconciliation report from 12 minutes to 40 seconds.
Alex got kudos from Priya: "Thanks for building both refund options behind a flag."
Nina earned 3-day spark in her first week on agent-sync.
From insights to better conversations
Developer Insights exists to help people do their best work, not to watch them.
Unblock faster
See who has been stuck, on what and for how long, so a blocker gets an answer in a day instead of at the next standup.
Better 1:1s
Open each 1:1 with what the developer actually worked on, in plain words, instead of a guess about how things are going.
Celebrate real wins
Badges and kudos come from work that shipped, so recognition is fair and visible to the whole team.
Coaching, not surveillance
- Built for coaching, not ranking: no leaderboards by default.
- Developers see their own insights, admins decide who else can.
- Summaries describe the work, never keystrokes, file contents or environment variables.
- Insights stay inside your organization and its project boundaries.
Developer Insights questions, answered
How summaries, statuses and recognition work.
A card for every developer with an AI-written summary of what they worked on and their current status: stuck, active, exploring or idle. Open a card to see the full profile, with a day-by-day breakdown, the problems they are stuck on, their badges and the kudos they received.
From the developer's own prompts, session summaries, observations and commits for the selected period. It describes the work and its outcome in plain words, such as which ticket moved forward and what is still open, rather than counting prompts and commits.
It looks for the same problem coming back across prompts and sessions, open questions or blockers in the session summaries, and a lot of AI work on a ticket with no commit that closes it. The profile says what the problem is and how long it has been open.
They show how serious a stuck status is. Low means the same problem came back within a day. Mid means two days on one problem, or a blocker waiting on someone else. High means three days or more, or work blocked until a decision is made.
No. Idle only means no AI sessions or commits were recorded in the period. The developer may be on leave, in meetings, doing work that does not need AI, or using a machine whose agent stopped syncing. Treat it as a reason to check in, never as a verdict.
Automatically, from real activity: milestones such as a first commit or a year on the platform, streaks of working days with AI, craft badges such as Deep focus, and team badges such as Monthly top coder. Teammates can also give each other kudos, which count toward Team favourite.
Every developer sees their own profile. Admins decide who else can see it, for example a team lead for their own team.
It is built for coaching, not ranking. There are no leaderboards by default, and statuses come with the reason behind them, so a lead can help with the actual problem instead of judging a number.
Know what your team worked on, and who needs a hand.
Install the agent once per laptop and every developer card fills in from the sessions your team already runs.
- Free for up to 5 developers
- 10-minute setup
- Your Anthropic key, your spend (Enterprise)