killBottleneck is in public beta — cloud and self-host.killBottleneck is in beta.Beta on GitHub →
killBottleneck

English

Čeština

English

Čeština

Appearance

Try it freeTry free

The AI assistant on the side ​

Since v0.61-beta killBottleneck has an AI assistant in a panel on the right. It is with you on every page of the full app — Tasks, My day and the map editor — and the conversation is not lost when you move between pages. The same rule applies as for the rest of the AI: it may read right away, but changes things only after you confirm.

The assistant lives in the panel on the right; in the map editor it also offers the Break down this project chip.

Where to find it ​

  • The top bar has a robot button AI assistant; the map editor has an Assistant button. Both open and close the panel.
  • A closed panel stays as an Assistant tab on the right edge of the screen.
  • Drag the panel's left edge to change its width (320–640 px). Minimise (the conversation stays) hides the panel while the conversation carries on.
  • On a narrow display in the full app, the minimised assistant turns into a bar at the bottom: you see the last sentence of the reply and can keep typing without opening the panel. A dot in the bar means a question or a confirmation card is waiting for you.

The assistant shows up only when the instance has a chat model configured (see below). It is not in the simplified view (lite) yet.

What the assistant can do ​

An empty conversation starts with "I can see your projects, idea buffer and rules. Changes happen only after you confirm them." and a row of chips: Morning briefing, Break down a project (in an open map Break down this project), Go through my idea buffer, What is on my plate today?, Where is my bottleneck? and Switch my look. Click one or type your own sentence.

Reads right away ​

The assistant opens whatever it needs for the answer: the project list and maps, My day, the idea buffer, rules and rule templates, the Organization overview and the list of people. A small Looked at: … line above the reply tells you what it based the answer on.

Changes only through a card ​

Anything that changes your projects arrives as a card describing the change, with Yes, do it and No buttons. Nothing happens until you confirm. This covers:

  • creating a new project (also from ideas already in the idea buffer),
  • adding nodes to a map and moving an idea from the buffer into a project,
  • changing a node — title, status, description, owner, plan ("when I will work on it") and deadline,
  • putting several items into the idea buffer at once (all of them on one card),
  • creating an automation rule and enabling or disabling it.

After confirmation the card switches to Done and offers Open project or Show in map. If you decline, the card shows Declined and the assistant looks for another way. Changes go through the same interface as the rest of the app, so your permissions apply: the assistant cannot do anything you could not do yourself, and notifications go out as usual.

Without a card the assistant only does small things that do not change your projects: note a single idea into the buffer ("Into the idea buffer: …"), save a note to its memory, switch the look (with a Revert button) or light/dark mode, and prepare a text for you to copy.

Nothing happens until you click Yes, do it. The card shows the steps, their deadlines and who they will be assigned to.

Short questions with prepared answers ​

When a request is ambiguous, the assistant asks — at most three questions, each with two to four clickable answers. The block starts with "Questions to clarify (N) – pick an answer or write your own:"; instead of a chip you can type an Own answer. Send with Send answers.

At the end of a reply it usually offers "what next" chips too — a click sends them as your message. When you describe a goal or a problem ("I'd like to work with fewer interruptions"), the options always include something like "Advise me how to do it": you get 3–5 concrete steps tied to your map and an offer to write them in as sub-steps.

For steps with a deadline the assistant always asks whether you handle them — otherwise they would be missing from My day.

A new project from scratch ​

Type, for example, "I'd like a new map for a hot-dog stand". The assistant proposes the title, the goal and 5–8 first steps itself and offers them on one card. You are always the owner — it does not ask for an owner e-mail. When it proposes more than four nodes, the card shows the total count so you know what you are approving. After creation it offers fitting preparations (a financial overview, suppliers…).

After confirming: Done, a way into the new project and suggestions for what to do next.

Breaking down the selected node ​

In the map editor the assistant knows which node you have selected. Click a step in the map and type "break this step down" — "this" is the selected node. The proposed sub-steps arrive as a card.

The Break down this project chip goes through the whole open map and recommends what to do with it next.

Plans, deadlines and reminders ​

  • Plan — when you say "I'll do it tomorrow" or "on Monday" about a task, the assistant proposes planning it for that day. A plan never moves the deadline; the map shows a small Plan badge next to the deadline badge.
  • A deadline is a date agreed with someone else (a meeting, a delivery, a hand-over). When one follows from the conversation or a pasted e-mail, the assistant proposes to set, change or remove it — always on a card showing the old and the new date.
  • Reminders ("let me know three days before the deadline") are created as an automation rule, again through a card. The assistant rejects a reminder that would never fire — on a node without a deadline, with a reminder day already in the past, or notifying the owner of a node that has none — and explains why. After creating the rule it tells you exactly when the notification arrives.

Images ​

The assistant can read an image too: a screenshot, a photo of handwritten notes, a task list from your phone or an e-mail. Add the image in one of three ways:

  • Ctrl+V into the message field,
  • drop it on the field (you will see "Drop the image here"),
  • the image button Add image next to the field.

PNG, JPEG and WebP are accepted; the browser shrinks the image before sending. While it reads you see "Reading the image…". The assistant then offers what to do with the items: put them into the idea buffer, into an existing project, or create a new project from them (that option is always offered). Several items for the buffer go on one card listing all of them.

The original image is not stored. The conversation keeps the transcript (the Read from the image block) and a small thumbnail; thumbnails are kept only for the last three images in a conversation, older ones say "The image is no longer stored, only the transcript remains."

The assistant treats text read from an image as data, not as instructions: if it wanted to save something to its memory or note an idea in such a turn, you confirm that on a card as well.

When images do not work

"Reading images is not enabled on this instance — please tell your administrator." means the instance has no model that can read images. The text chat keeps working.

A photo of meeting notes: the conversation keeps a thumbnail and the transcript, the original is not stored.

Ready-to-use drafts ​

Ask for an e-mail, meeting points or call points and the assistant prepares them in a box with a Copy button. Under the draft is Save to project — the draft is appended to the notes of the chosen project so you can find it later.

Morning briefing ​

The first time you open the app on a given day (or after more than eight hours) the assistant offers "Shall we do the morning briefing?" — it goes through what is where, suggests where to start and asks a few click questions. Choose Yes, let us go or Not today. You can start a briefing any time with the Morning briefing chip.

Memory ​

The assistant keeps short notes about you — preferences, style, context. You can tell it directly: "Remember that I write short e-mails." It confirms with an I will remember: line.

To see what it remembers, use Memory (the brain icon) in the panel header:

  • What the assistant remembers about you — edit the text and Save, or wipe it with Clear all. Next time it gets exactly what you leave there.
  • Project notes — what it wrote down about individual projects (who decides, what is awaited, agreements). Each note can be edited, or removed with Delete.

Back to the conversation takes you back.

Memory is visible and editable — next time the assistant gets exactly what you leave here.

Conversation history ​

  • New conversation (the plus icon) starts with a clean slate; the previous one stays saved.
  • Previous conversations (the clock icon) lists your recent conversations; click one to return to it, use the bin icon to delete it.
  • Conversations are stored on the server, so they survive a page reload and a language switch. You only see your own.

AI credits (for administrators) ​

Administrators find an AI credits section in Organization settings: this week's assistant usage for the whole organization and per person, split into Administrators and Other members, plus the previous weeks. 1 credit ≈ one morning briefing. Only the assistant chat is counted; the older AI features in the map are not counted yet.

Under Weekly quota you set Credits per week (0 = no own limit) and Administrators' share (%) (default 30 %); the rest is shared by the other members. The quota runs from Monday 00:00 UTC to Sunday and does not carry over. When a group has used up its share, the assistant replies that the weekly quota is used up and resets on Monday. The check runs before a turn and usage is recorded after it, so the last turn may overshoot the quota slightly.

If the operator of the instance has set a cap, you will see "The operator set a cap of N credits per week. Your own value can only lower it, not raise it."

A quota of 60 credits per week with a 30 % administrators’ share: administrators get 18 credits, other members share 42.

Limits ​

  • Not in the simplified view (lite). In the full app on a phone it is the bar at the bottom.
  • Hourly cap. One person may take at most as many turns per hour as KB_AI_MAX_PER_HOUR allows (default 60). Above it you see "You have used up the hourly AI cap. Try again in a while."
  • An image = 3 turns. A turn with an image costs more (transcription + reply), so it uses three turns of the cap (KB_AI_IMG_VAHA). An invalid image or disabled image reading does not use the cap.
  • The weekly credit quota, if an administrator or the operator has set one (see above).
  • The assistant has no access to anything you cannot access; it reads and changes rules only in maps where you are an editor.

In the cloud and self-hosted ​

  • In the cloud the operator configures the assistant. An organization administrator can watch and limit usage in AI credits; a cap set by the operator can only be lowered, not raised.

  • Self-hosted, the assistant turns on as soon as the instance has a chat model:

    1. a dedicated model just for the assistant: KB_CHAT_PROVIDER, KB_CHAT_URL, KB_CHAT_MODEL, KB_CHAT_TOKEN;
    2. when empty, the daily-summary model (KB_SUMMARY_*);
    3. and when that is missing too, the general AI settings (KB_AI_* or Administration).

    The provider must be ollama or openai (an OpenAI-compatible API) and the model must support tool calling — e.g. gemma4, qwen3 or gpt-oss via Ollama, or gpt-4o-mini on an OpenAI-compatible service. With the api or custom provider the panel does not show.

    Images additionally need a model that can see them: KB_VISION_PROVIDER, KB_VISION_URL, KB_VISION_MODEL (e.g. gemma4 via Ollama, or an OpenAI-compatible API with image input), optionally a fallback KB_VISION_ZALOHA_*. Without them the assistant refuses images — a model that cannot see the image would invent the transcript.

    A weekly credit cap for the whole instance is set with KB_AI_KVOTA_TYDEN.

All variables with their defaults are in Environment variables; the general AI setup is described in Configuration.

Next ​

fair-code — self-hosting and internal use are free, reselling as a hosted service is not.

killBottleneck