T3 Code
Hand the task to T3 Code.
Link T3 Code sends a snapshot of the task to T3 Code on your Mac. Your mapping picks the project, provider, model, and permissions, and the thread's status and summaries come back to the task.
Flow left to rightTasks
2ReadySchedule
All tasks · Last updatedRKS-31Homepage hero motion specLow Priority
BSH-52Patient intake form accessibility auditCriticalOct 10
2DoingIn motion
All tasks · Last updatedNWR-142Webhook retry backoff for fulfillment eventsHigh PriorityOct 9
CAS-88Backfill July telemetry into warehouseHigh PriorityOct 8
NWR-142MoreWebhook retry backoff for fulfillment events
DescriptionRetry failed fulfillment deliveries with exponential backoff and record each attempt, so support can see why an order is late.Client Northwind RoboticsProjectFulfillment APILifecycleDoingPriority
HighStart afterNoneDuration2hTime blocksPlanner defaultDueThu, Oct 9
T3 CodeLink T3 Code
Link Codex
Link Asana
Link issue
Start HighStart afterNoneDuration2hTime blocksPlanner defaultDueThu, Oct 9T3 CodeLink T3 CodeNWR-142: Webhook retry backoff for fulfillment eventsMacBook Pro · Work · fulfillment-apiDoneHanded off · 4mOpen in T3 Code
Link CodexLink AsanaLink issue Code Alpha New thread SearchProjects fulfillment-apiNWR-142: Webhook retry backoff for fulfillment eventsCompletednowDead-letter queue for failed deliveries2dSignature check on inbound webhooks4d warehouse-jobs brand-siteNWR-142: Webhook retry backoff for fulfillment events fulfillment-apit3code/webhook-retry-backoff
NWR-142: Webhook retry backoff for fulfillment eventsWork on the Kernel task below. Gather as much context as you can from the task before starting.key: NWR-142
t3codeHandoffId: 7c1e9a04-…
href: https://app.krnl.work/t/NWR-142Worked for 3m 48sAdded exponential backoff with jitter to fulfillment webhook retries, capped at six attempts, and recorded each attempt’s delay. All 14 webhook tests pass.
Saved a work summary to NWR-1422 files changed+79 −8
Saved a work summary to NWR-1422 files changed+79 −8Ask anything, @tag files/folders, $use skills, or / for commands
Claude Opus 5 · HighBuild Auto-accept edits
Claude Opus 5 · HighBuild Auto-accept editsHighlights
Draft or Work
Draft opens a new T3 Code composer with the task filled in and sends nothing. Work starts the thread and its first turn, in Build or Plan.
Mapped per project
Map an organization or project to a T3 Code project on each Mac, with its provider instance, model, options, permissions, and checkout.
Status on the task
Running, Done, or Disconnected, with approvals and questions called out. The planner's queue card shows Working or Waiting for you.
Mappings
Map each project once.
In Settings → Integrations → T3 Code, point an organization or project at a T3 Code project. Choices come from what that Mac's T3 Code reports, and Kernel checks them again at launch.
- Provider instance and model, named exactly as T3 Code names them
- Supervised, Auto-accept edits, Auto, or Full access permissions
- A new worktree for Git projects by default, or the project folder
MacBook ProT3 Code is runningConnected2 mappings · 6 projects
Organization and project mappingsOrganization default Northwind Roboticsfulfillment-api · New worktreeclaude-work · Claude Opus 5 · Effort: High · Supervised · No thread name prefixEdit
claude-work · Claude Opus 5 · Effort: High · Supervised · No thread name prefixEditProject override Pipeline Rescuewarehouse-jobs · New worktreecodex · GPT-6 Astra · Reasoning: High · Auto-accept edits · No thread name prefixEdit
＋ Add mapping T3 Code mapping saved.codex · GPT-6 Astra · Reasoning: High · Auto-accept edits · No thread name prefixEditWork summaries
Summaries land on the right task.
When the agent finishes or pauses after real work, the Kernel skill saves a Markdown summary to the task, tied to its thread. The card's Work summaries link opens it.
- Each summary links back to its thread with Open in T3 Code
- AGENTS.md presets choose off, ask, or yolo for summaries
- A summary never changes the task's status or records time
NWR-142MoreWebhook retry backoff for fulfillment eventsClient Northwind RoboticsLifecycleDoingT3 CodeLink T3 CodeLink CodexLink AsanaLink issue
T3 CodeLink T3 CodeNWR-142: Webhook retry backoff for fulfillment eventsMacBook Pro · Work · fulfillment-apiDoneHanded off · 6mOpen in T3 CodeLast work summary · 2m
3
3Link CodexLink AsanaLink issueWork notesWebhook retry backoff for fulfillment events＋ Add newAll work notesT3 Code summaryOct 8, 4:12 PMMac agentsT3 Code summaryOct 8, 2:05 PMMac agentsT3 Code summaryOct 7, 5:40 PMMac agentsT3 Code summaryOct 8, 4:12 PM · Mac agentsOpen in T3 CodeDone. Added exponential backoff with jitter to fulfillment webhook retries, capped at six attempts.
- Each attempt records its delay and status
- 14 webhook tests pass
retry.ts, retry.test.tsTests. pnpm vitest run src/webhooksRemaining. Tune the cap after a week of retries.Good to know
- Pair a Mac once with krnl connect t3code and a pairing link from T3 Code's Settings → Connections.
- Kernel receives a thread's state, title, and a short explanation, never its conversation.
- Launches aren't queued: while T3 Code is closed, its Mac shows Disconnected.
- Workflow presets such as Research or Implement start a saved Work launch from beside Link T3 Code.
- Stop a running turn in T3 Code itself; Kernel has no Stop control for T3 Code threads.
- Starting, waiting on, or finishing a thread never changes the Kernel task's status.
