Skip to content
KurrentDB

Notifications

Surfaces: web app (the bell, Home) · desktop app (system notifications, rail and tray) · Slack (direct messages) · CLI (kcap config) · your agent (coordination notices at session start)

The web app is at https://<your-workspace>.kcap.ai for a cloud workspace; on the local edition the same pages are served from your machine. The desktop app opens it from Help and support → Open dashboard, and kcap local open opens the local one from a terminal

Notifications tell you when something needs you or when something you care about finished. They collect in the inbox behind the bell, and can also reach you as Slack direct messages. The desktop app tells you about your own agents separately, through your operating system’s notifications

The bell and Slack delivery are behind a switch your workspace may not have on. On the local edition they are off unless turned on in the server’s environment, so the desktop app’s notifications are what you have there

Know when something needs you. The kinds that arrive:

  • An agent is waiting for an answer or a permission
  • A session finished, with its outcome
  • A collision: a teammate’s live session overlaps your files or your work item
  • An evaluation finished, or a knowledge approval is waiting on you
  • A project membership or join request needs a decision
  • Your kcap is older than the server recommends

Open the bell to read them and mark them read. On Home, the Agents tile lists your agents with the ones stopped on you first: a question, a permission request or a failure

The notification center open from the bell on the DashboardThe notification center open from the bell on the Dashboard
The notification center

Get desktop notifications. While the desktop app is in the background, it sends a system notification when one of your agents asks for a permission, asks a question, or finishes a turn and waits for you. A permission notification carries Allow, Always and Decline, so you can answer without opening the app; a question offers Respond in app, and an idle agent Open agent. A usage limit reached also notifies you. Help and support → Settings… → Notifications turns each of Permission requests, Questions and Waiting for you on or off; your operating system must allow kcap’s notifications too, and the tab offers to open that setting when it does not

The desktop app's Settings on the Notifications page
Settings → Notifications in the desktop app

See what is waiting in the desktop app. The dots beside each session in the rail show the ones waiting for you. The tray icon changes when an agent needs attention, its menu lists your running agents, and Review pending launches… appears while a launch request waits for your approval

Understand a collision warning. kcap compares the files and work items of live sessions across people. When two overlap, both sides get a notice, and the agents get it at session start as a coordination notice. It is a heads-up, not a lock: nothing stops either of you editing. Read what the other session is doing before you change the same thing, or ask your agent “who else is working here?”. Detection runs whether or not the bell is on. To stop the notices at session start:

Terminal window
kcap config set disable_coordination_notices true

Get notifications in Slack. If your admin has installed the workspace’s Slack app, open the notification settings from the bell and choose Connect Slack; kcap finds your Slack account by email. Send test confirms delivery. If the account is not found, enter your Slack member ID (it starts with U) instead; Reconnect appears if delivery stops. Each person opts in for themselves; configuring the app does not opt anyone in

Choose what you are told about. The settings dialog lists each kind with a switch for In-app and for Slack. Turn off what you do not want; the detection still runs, so you can turn a kind back on later without losing anything. The desktop app’s system notifications have their own three switches under Settings… → Notifications, and the coordination notices your agent gets have their own key, disable_coordination_notices

Nothing ever arrives. The bell is behind a deployment switch, off by default on the local edition. If your admin says it is on, check your preferences: every kind may be off

The desktop app never notifies me. It notifies only while it is in the background. Check Settings… → Notifications in the app, then your operating system’s notification settings for kcap

Slack says missing scopes. The Slack app was installed before DM delivery was added. An admin updates the manifest and reinstalls it under Administration → Integrations

I got a collision warning for my own session. Two chats in the same repository on the same machine can look like two people before the second has an owner; it clears once the session is attributed

The desktop app shows an agent waiting but the inbox is empty. The mark sits on the session in the rail, or on the tray icon, and means that agent is waiting for you: a permission request, a question, or a launch approval. It is not an inbox item. Open that session’s Chat tab and answer the card there, or answer the launch from Review pending launches… in the tray menu