This guide walks a new R&D engineer named Priya (joining the Kbot-Link team this week) through her first working task, end to end. You do the same steps in your workspace as you read. Nothing here is a demo — every screen shown is what actually happens.
The AI Helper is not a boss and not a stopwatch. It's a scheduling teammate whose job is to make sure the number you're measured on is fair to you.
Reads the ticket you're about to work on, looks at similar past tasks and the code paths involved, and proposes a required-hours number — the honest amount of time this task should take. You either accept or counter. Once you and your manager sign, the number is locked and the clock is fair.
It doesn't watch your screen. It doesn't count keystrokes. It doesn't read your DMs. It doesn't compare you to other engineers behind your back. Your score is your actual hours ÷ the number you signed for — that's it.
Nothing else starts until you finish T0. The AI Helper can't propose fair hours if it can't see your work signals — so we spend 30 minutes granting scoped, revocable access to the things it needs to read.
From your Workforce workspace, click Start T0 access in the pinned banner. You'll see six sub-tasks. Each is one grant.
Paste a read-only token from your own Claude / OpenAI / Gemini account. This lets the AI Helper see your past AI sessions on the code you're about to work on — so it can propose hours from your actual patterns, not a generic estimate.
Sign in with your own GitHub through the Claude Code web session. You'll authorize read on src/public/kbot-link and the OTA routes — nothing else in the Kbot repo. You never hand over anyone else's GitHub credentials.
src/public/kbot-link and src/api/routes/ota.routes.tsThree more one-click grants: GitHub Issues + Projects filtered by kbot-link label, GH Actions runs touching your paths, and read on the R&D Zoom channel only (DMs and other channels stay out of scope).
One page. Says exactly what the AI Helper reads, stores, and never touches. You sign; your manager (in your case, the Kbot-Link lead) counter-signs. You can revoke any grant any time — the manager gets notified but can't block the revoke.
The Kbot-Link lead assigns you KL-152 — "Add tenant filter to OTA release picker". Before you write any code, you'll agree the hours with the AI and your lead.
Open KL-152 in Workforce. The three-way agreement panel is already populated with the AI's first proposal.
You look at the code and notice the tenant filter has to talk to a permissions check the AI didn't reference. You counter with 7h and one sentence of reason. This is a normal round — most tasks take 1 or 2 rounds to converge.
The AI reads your reason, agrees the permissions check is real, and updates its proposal to 7h. That's convergence.
Your lead sees the agreed 7h and one line of reasoning. They approve in 15 seconds. The task auto-flips to In progress and the "actual hours" timer starts tracking.
You don't press "start" and "stop". Actual hours are inferred from two signals you already produce.
Every time you commit code that references KL-152 (in the branch name, PR link, or commit message), the AI Helper looks at the timestamps and infers active work windows. Two commits 20 minutes apart on the same branch = 20 minutes of work.
If you prefer to be explicit — some engineers do — hit T to start a timer on the open task and T again to pause. It's additive: the timer sums with the commit windows, deduped.
The task detail shows required and actual side by side, live. You can see whether you're on plan without opening a dashboard.
Task shipped. PR merged. Time to read the score.
Either flip the state to Done yourself, or let the auto-close fire when the linked PR merges to main. Both do the same thing.
Actual came in at 6.5h against a required of 7h. Delta = 0.93. That's "on plan" — the score band is 0.9–1.2.
Three bands, no punishment for being close:
Friday afternoon, your first weekly diary lands. It's yours — you see it before your lead does.
Workforce sidebar → Diary → this week. The layout is identical to the daily view, aggregated across your 5 working days.
Score = weighted sum across six categories (task-time, code quality, delivery, collaboration, context assets, reliability). Week 1 is mostly task-time and delivery — your context-assets and collaboration scores fill in as you work more with others.
Your lead sees the same diary you see, at the same time. Nothing is hidden. If they want to talk about anything on it, they'll ask — and you'll both be reading the same page.
Open the task, click Re-estimate. AI proposes a new required-hours. New three-way sign starts. Original agreement stays in history — nothing hidden.
Flag Blocked with the name of the blocker. Clock keeps running on the actual, but the delta calc ignores blocked time. Your lead sees the block within minutes.
Hit Escalate. Your lead joins the thread and the three of you land the number together. This is a normal path, not a failure.
Doesn't matter — commit-authoring windows will pick most of it up. If you want to correct, use Adjust actual with a note. Adjustments are visible to your lead.
Split creates a sibling task and asks the AI to propose hours for each half. The original required is retired; the two new signatures replace it.
Settings → Grants → click Revoke on any T0 grant. The AI Helper stops reading that signal immediately. Your lead is notified.
#rd-onboarding in Zoom.