Feature explorer

Everything flows through Kernel.

Requests arrive from email, Slack, meetings, and trackers. Kernel turns them into planned, tracked work, hands tasks to your agents, and sends the results to Asana, Toggl, your calendar, and your invoices.

In Kernel and agents Out

Walk through every stop

The walkthrough

Follow the work from the first message to the last invoice.

Nineteen stops, in the order work actually moves. Each one plays a short recreation of the product with sample data.

Act 01 · In

Work arrives from everywhere.

Kernel reads the places requests already land: email, Slack, meetings, trackers, and your calendar. Nothing becomes a task until you accept it.

In · Gmail

Email requests become reviewable suggestions.

With read-only access, Kernel reads recent Inbox messages and your replies. When a thread asks something of you, it drafts a task or an event for you to review.

  • Imports the last 48 hours of Inbox messages, plus eligible sent replies
  • Suggests tasks and events, with due dates and guests
  • Shows its reasoning under “Why Kernel suggested this”

In · Slack

Mentions and DMs don't slip through.

Direct messages, mentions, replies in threads Kernel already kept, and the channels you choose all feed the same Inbox.

  • Read-only access to the conversations you include
  • Your own promises count: “I'll get back to you” becomes a follow-up
  • Channels are added one by one, never all at once

In · Fireflies

Meeting action items find their owner.

When a recorded meeting ends, Kernel reads the transcript, Fireflies' summary, and the action items, then keeps the ones that are actually yours.

  • Uses the transcript, summary, and action items together
  • Leaves out items that belong to someone else
  • Lands in the same Inbox as email and Slack

In · Asana & GitHub

Tickets you already have, in one queue.

Choose Asana projects or assignees and GitHub repositories. Their work arrives as Inbox suggestions next to everything else, so one review covers every client.

  • Asana: tasks from the projects or assignee you choose
  • GitHub: open issues from selected repositories
  • GitHub stays read-only; Kernel never writes to it

In · Calendar & booking

Your real calendar, and a link clients can book.

Google Calendar events appear in the planner, with RSVP built in. Scheduling links let clients choose a time from your real availability, and each booking becomes a meeting with a Google Meet link.

  • Events from the Google calendars you authorize
  • Reply Yes, Maybe, or No without leaving Kernel
  • Booking pages offer only the times you're free

In · Capture

Type it once. Kernel splits it up.

Write a messy note and use Draft with AI to turn it into separate suggestions, or paste a Gmail, Slack, or Fireflies link into Add to Inbox.

  • Draft with AI turns free text into up to ten suggestions
  • Add to Inbox accepts Gmail, Slack, and Fireflies links
  • Search Gmail by subject to bring in a thread

Act 02 · Kernel

Kernel turns it into a plan.

Suggestions become tasks, tasks become timeboxes around your meetings, and your agents pick up the work from there.

Kernel · Inbox review

Nothing becomes a task without you.

Each suggestion waits in the Inbox with its evidence and a confidence score. Accept it into Backlog or Ready, link it to a task you already have, or clear it.

  • Discard sets a good suggestion aside, with Undo
  • Reject asks why: Not mine, Duplicate, Noise, and more
  • Already done closes it without creating work

Kernel · Rules & AI checks

Rules route it. Checks keep it honest.

Destination rules send matching messages to the right organization, project, or calendar, with optional parser instructions. Exclusion rules skip noise, and everything skipped stays visible in Reviewed messages.

  • Checks whether a request is really yours before suggesting it
  • Matches existing tasks to avoid duplicates
  • Closes a suggestion when a later reply shows the work is done

Kernel · Tasks

One board for every client.

Accepted work joins one board that runs from Blocked to Done. Every task carries its client key, priority, and due date; habits and standing tasks handle work that repeats.

  • Client keys like NWR-142 on every task
  • Habits create ordinary Ready tasks on a schedule
  • Standing tasks hold ongoing work that never finishes

Kernel · Planner

Timeboxes that respect your meetings.

Kernel places ready work around your meetings, inside your Scheduling hours. Locked blocks stay put; a block that passes unworked is marked missed and rescheduled.

  • Today's priorities are placed first
  • Locked blocks track time automatically
  • End work day closes out what's left

Kernel · Time

Every start is a timebox.

Starting work opens a planner block and records time against the task. Each entry carries its billability and a work note, and drafts from agents wait for your review.

  • Summary, Entries, and Drafts in one place
  • Billable or non-billable, entry by entry
  • API drafts are accepted or discarded by you

Kernel · T3 Code

Hand a task to T3 Code.

Link T3 Code sends a snapshot of the task to T3 Code on your Mac. Project mappings choose the provider instance, model, permissions, and Build or Plan, so Claude or Codex starts with the right context.

  • Draft fills in the composer; Work starts the first turn
  • Running, Done, or waiting for your approval, shown on the task
  • Paired once with krnl connect t3code

Kernel · Codex

Or give Codex the first pass.

Link Codex sends the same snapshot to Codex. Draft opens a prefilled composer and sends nothing; Work starts the first turn in a new Git worktree.

  • Status: Running, Done, or Disconnected
  • Stop and Open in Codex, right from the task
  • The Kernel task's status is never changed for you

Kernel · Agent API & krnl

Any agent can do the work you do.

Agents with an API key read and manage the same tasks, time, and projects through /api/v1. The krnl CLI pairs your Mac, and the Kernel skill teaches agents to post work summaries back to the task.

  • Keys are Read only or Full work
  • Work summaries land on the task as work notes
  • Choose off, ask, or yolo for summaries and completion

Act 03 · Out

Then it goes where it's needed.

Completed work, recorded time, and invoices flow back out to your calendar and the tools your clients already use.

Out · Asana

Asana stays in step.

Linked tasks send completion and column moves back to Asana. You map each Kernel status to an Asana column, and you can create a new Asana task straight from Kernel.

  • Completing or reopening in Kernel updates Asana
  • From Kernel status, to Asana column
  • Titles, notes, and dates aren't synced

Out · Toggl

Recorded time, sent to Toggl.

Sync to Toggl previews each day's recorded time before anything is sent, using your organization and project mappings. If a copy is edited or deleted in Toggl, Kernel offers to repair it.

  • Create, Restore, Recreate, or Remove, row by row
  • Repairs are never preselected
  • One way: Kernel's record stays the source

Out · Google Calendar

Your plan shows up where people look.

Planner blocks are written to Google Calendar, and moving a block moves the event. Sync copies events between calendars with privacy rules, so a client's calendar can show Busy instead of details.

  • Create, edit, move, and delete events from Kernel
  • Privacy: Busy, a default label, custom, or full details
  • Copied guests are text only, so nobody is invited

Out · Invoices

Invoices built from the record.

Unbilled time and fixed fees become invoice lines. Issuing freezes a PDF, payments move it to Paid, and a mistake is voided rather than quietly rewritten.

  • Hourly work, fixed fees, and adjustments
  • Draft, Issued, Sent, Paid
  • Work billed outside Kernel can be recorded too

Out · Client dashboards

A live report your client can open.

Share a public, revocable link for an organization or project. Clients see tasks, time, money, and invoices, as totals only or with entries.

  • Revoke a link at any time
  • Totals only, or Summary and entries
  • Time entries also export as CSV through the API

End to end

One request, all the way through.

Private beta

Your work, in motion.

Demos use fictional clients and sample data. Kernel is still being built one week at a time.

Back to the mapKernel home