Killbottleneck

Create an automation rule on a map: WHEN trigger fires (and optional AND conditions match) DO the actions in order. Rules run for changes made in the UI, via API and by agents alike. Structural limits: 50 rules per map, 10 actions, 20 conditions — there is NO monthly run quota. A rule applies only to future events, never retroactively. node_id scopes the rule to one node (required for schedule rules whose actions target a node).

Approve or decline a TIME-OFF request (an absence waiting for approval) — admin or manager only. event_id from list_events / the request; note = reason or condition (shown to the requester). The user confirms first.

Decline a colleague's pending request for a different deadline on a step (the project owner or whoever assigned the step). To ACCEPT the request, set the wanted date with update_node deadline instead. The user confirms first.

Delete an AI agent from the registry by exact name. Cannot be undone. The user confirms first.

Delete a shared calendar by id or name together with ALL its events (admin or manager only). Cannot be undone — prefer archiving (not offered here) when the history should stay.

Delete one of the user's assistant documents for good (document = the exact title or the id from list_documents). Cannot be undone. The user confirms first.

Delete an event by id (your own, or one in a shared calendar as admin/manager). If you were only invited, you leave the event instead and it stays for the others.

Delete ideas from the user's idea buffer for good — old, duplicate or nonsense entries, or the whole buffer when the user asks to clear it. Pass the exact titles from list_ideas, or all: true for every idea. Only when the user asked for it or chose it — never on your own. The user confirms on a card listing every deleted idea; it cannot be undone.

Delete a node INCLUDING its whole subtree. The apex (root) cannot be deleted and whole maps cannot be deleted via the API. Irreversible — read the map first and double-check the node id.

Delete a project (map) with all its steps for good — cannot be undone; unless the user clearly wants it gone, offer archive_project instead. Project owner only. The user confirms first.

Remove a timed reminder from a map step (the deadline stays). reminder_id from list_reminders; when the step has exactly one reminder of the user it may be omitted. The user confirms first.

Delete an automation rule. Its run log stays (with the rule name snapshot). Irreversible.

Delete a rule template from the library (author or admin only). Rules already created from it are independent copies and stay untouched.

Write a document for the user: an e-mail, meeting points, phone-call points, a note or a summary. It is SAVED to the user's Documents (a panel next to the chat where the user reads, edits and copies it) and shown in a box with a copy button. Write the whole text into `text` (plain text; for an e-mail only the body — pass the subject in `subject` and the recipient in `to` when known); in your reply add only a one-line comment. NOT for ideas or tasks — those go to the idea buffer (add_idea / add_ideas) or a project. When the draft belongs to a project (an order, a customer, a supplier of that pr…

Read one saved document in full (by exact title from list_documents).

Read one map as an indented tree with node ids, statuses ([✓] done, [~] in progress, [ ] todo), deadlines and owners. The header shows the key's access level (owner/edit = full write; work and read = only the status of the key owner's own nodes, like ticking off in the app). Always call this before modifying a map you have not read yet.

Who can see a project (map): the people it is shared with and their permission (read / work / edit), the team access and the public link. Only the project's owner or a co-manager can read it. map_id = the exact title, the project number like "#12", or the id from list_maps.

What you remember about this user (markdown notes you wrote earlier).

The user's own open work today: blocking, overdue, today, this week (across all maps).

Read the organization structure (the org map): positions and functions with node ids, holders and deputies. Use the node ids as dynamic rule targets "position:<nodeId>" / "deputy_of_position:<nodeId>". Read-only — holders and deputies are appointed by an admin in the app.

Open work of ONE person (a colleague) in the projects the USER can see — for preparing a meeting with them. Never anything from projects the user cannot see.

Read the portfolio overview across all team and shared maps the key owner can read (private maps are excluded, exactly like the Organization page): per-project completion, overdue and stuck items, people with overdue work and a 7-day change summary. Optional today=YYYY-MM-DD. Read-only.

What happened in ONE project over the last days (default 14): finished, started, added, deadline changes, owner changes, moved and removed steps — for preparing a meeting or a status report.

The user's current settings (name, language, skin, theme, view, map readability, alignment lock, notification preferences) and — for administrators and managers — the organization settings (name, purpose, members with roles, AI settings without the token, AI credit quota, default skin, billing, AI agents). Call it BEFORE changing any setting and when the user asks where a setting is.

Team workload for the team meeting: per person open / overdue / stuck work, overdue items, stuck items, bottlenecks and projects — team and shared projects only, never private ones.

Is the user's work timer (stopwatch) running? Returns since when, the label and the step, or that nothing runs.

The user's OWN week (weekly review): what they finished in the last 7 days, what is overdue, what is due or planned in the next 7 days, what has not moved for a long time (stuck), what blocks others and what they assigned to others that is overdue. Only the user's own work, never other people's private projects.

Look up the app's user guide (how a feature works, where a button or setting is, what a screen shows, what the app can and cannot do). Call it BEFORE answering whenever the user asks HOW to do something in the app or WHERE to find something. query = the feature, screen or action in the user's own words (2–6 words; do not translate it into settings jargon). Returns 1–3 matching guide sections with their web links: answer briefly from them with the exact button and menu names; the app shows the links itself. A question HOW to do something asks for an explanation, not for the action — do not perf…

Invite a new member to this instance by e-mail (creates the account; with e-mail configured the invitation is sent, otherwise a temporary password is shown ONCE to the user on the card). Role admin/manager only an administrator can grant. The user confirms first.

List the shared calendars of the instance — company events (shared), rooms and other bookable things (resource), vacations and time off (absence) — with kind, color, who may add entries (write_access) and whether time off needs approval. Read-only.

The instance's client address book for invoicing (name, address, IČO, DIČ, e-mail, whether the billing details are complete). Call it BEFORE create_invoice to resolve the client the user named (first names are common: 'Karel' may match several clients — then ask_user which one). Also use it to tell the user which details of a client are missing.

The user's saved documents (e-mails, notes, summaries you wrote earlier; the user may have edited them): title, kind, date. Use it when the user refers to an earlier document.

List the calendar events the key owner sees — own, invited, and every event of the shared calendars — in a day range; default today−365 … +730. A multi-day event counts when it overlaps the range. Optional calendar = only that shared calendar. Read-only.

Ideas in the user's idea buffer (quick notes not yet placed into a project), with ids.

Invoices issued in this instance (own ones; an administrator sees all): number, client, total, due date, paid or not. Use it for 'how much did I invoice this year', 'which invoices are unpaid', or to find an invoice number.

List goal maps the key owner can see — own, team and shared maps (id, title, node count, last update, access: owner/edit/work/read). Use archived=true to list archived maps instead.

List the people work can be assigned to: instance members (e-mail, display name, role) and external contacts visible to the key owner (their owner_email is a pseudo e-mail usable as owner). Use these e-mails as `owner` in create_map/add_nodes/update_node and in set_owner rules — an unknown e-mail is rejected. Read-only.

The user's timed reminders on map steps (id, step, when it fires); optional map_id / node_id filter.

Read the run log of a map's automation rules (newest first, max 100): what fired, on which node, ok/failed/skipped and what the actions did. skipped = a safety stop (rule chain depth or per-save cap), detail says which.

List the instance-wide library of rule templates (shape of a rule without a map or node scope). To use one, read it and call create_rule on the target map with its trigger/conditions/actions — the created rule is an independent copy.

List automation rules of a map: id, name, enabled, scope node, trigger, conditions, actions, last_fired and last_error (a non-empty last_error means the rule is misconfigured and its owner was notified).

Where ONE project is stuck — facts, no scoring: steps that are overdue (days late), waiting for their sub-steps (waitForChildren), idle 14+ days (no real change in the change log) and how many open sub-steps each of them blocks. Attaches a card the user can click to highlight those steps in the map temporarily. Use it when the user asks about risks, bottlenecks, what is stuck, late or blocking in a project (the open map or a named one); for the picture across all projects use get_my_day. Summarize the result in short sections (Overdue / Blocking / Waiting / Idle) and say the card highlights th…

Mark ALL of the user's notifications (the bell) as read. The user confirms first.

Move a step (node) with its whole subtree under another step of the SAME map: parent_id = the exact title of the new parent step, or "apex" for the top level. Editors of the map only. The user confirms first.

Unlock a group of tools you need for the user's request but do not see yet (the base set is always present). Groups: pravidla (automation rules), projekt (create / archive / rename / delete a project, also from ideas), udalosti (events, timed reminders), terminy (deadline change requests), prace (comments, work timer), dokumenty (edit or delete earlier documents), pdf (PDF corrections), obrazek (ideas from a photo or voice-note transcript), vzhled (skin, light/dark), tym (team overview, people), pamet (memory), hledani (search the project archive), tyden (weekly review), schuzka (meeting prepa…

Order the yearly Cloud Lite membership by bank transfer (hosted instances; billing details must be complete — set_billing first). Creates a binding order; the invoice arrives by e-mail. Other plans are paid by card in Organization settings → Membership. The user confirms first.

Correct text in the PDF the user attached (block "[PDF text: …]"): replace exact strings — a price, a name, a sentence. `find` must be copied EXACTLY as it appears in the PDF text (same spaces, punctuation, currency) and be the SHORTEST distinct piece — just the amount with its currency, just the name, just the sentence — not the whole line; one entry per place; give the page number from the "--- page N ---" markers. The user confirms on a card, then the browser edits the PDF (the server never sees the file). When a price changes, also offer the dependent totals/VAT visible in the text as furt…

Replace your memory with the given markdown text (whole text, brief bullets). Without `map`: memory about the user (preferences, style, context). With `map` (exact map title): your notes about that project (who decides, what is awaited, agreements, what blocks).

Remove a position from the org structure (by exact title). The user confirms first.

Rename a project (map). Owner or editor. The user confirms first.

Send a bug report or an improvement idea about the app to its developers (kind: chyba = bug, napad = idea) with the user's text — the same as the report form in the app; needs e-mail on the instance. The user confirms first.

Ask the assigner for a different deadline on the user's OWN step in SOMEONE ELSE'S project — the deadline stays until the assigner agrees (the owner of a project changes deadlines directly with update_node). cancel=true withdraws the user's pending request. The user confirms first.

Bring back the previous version of an assistant document (undo the last rewrite; calling it again redoes it). The user confirms first.

Create or update an AI agent in the registry (by exact name): description, webhook_url (required for a new agent), enabled, allowed_emails (members who may run it; empty = anyone). The agent's secret can NOT be set here ("AI agent registry" dialog). The user confirms first.

Create a client in the address book, or update an existing one (pass `client` = its exact name or id to update). Fields: name, address (lines separated by newline), ico, dic, email, note. Use it when the user gives client details in text, or after a business-card photo transcript: fill in ONLY what the transcript really contains (IČO = 8 digits, DIČ = CZ + digits, ZIP = 5 digits), never invent an IČO, address or e-mail. The user confirms on a card.

Save a rule shape into the instance-wide template library (create, or update with template_id — only the author or an admin may update). Templates carry no map and no node scope; create_subnodes may only use parent=trigger_node. Template names are unique.

Search ALL the user's projects — active AND archived — by project number (#12), project title, step (node) titles, descriptions and owners. Also searches the user's own Documents (drafts, meeting notes, meeting prep). Case- and diacritics-insensitive, matches word forms by stem ("fakturami" finds "Faktura"); rare words weigh more; a multi-word query need not match completely — results are ranked. Returns matches grouped by project with its number, state (active/archived), open steps and deadlines, then matching documents. Use it when the user asks where something is or was, refers to an older,…

Set the weekly AI credit quota of the organization (kvota_tyden, 0 = no own cap; the plan may cap it) and/or the administrators' share in percent (podil_admin; the rest goes to the other members). Administrator only. The user confirms first.

Change the AI provider settings of this instance (own server only): provider (none|ollama|openai|api|custom), url, model, transcribe_url, transcribe_model, vision_enabled, vision_model. Pass only the fields to change; the API token can NOT be set here (Organization settings → AI). The user confirms first.

Save the billing details of the organization (hosted instances): company, ico, dic, street, city, zip, email. Pass only the fields to change. Administrator only. The user confirms first.

Set the DEFAULT skin of the whole instance (for users who have not chosen their own): builtin_id = indigo, contrast, terminal, sepia, ocean, les, pulnoc, svestka, broskev, grafit, rubin, ruze; empty string removes the default. Administrator only. The user confirms first. For the user's own skin use set_skin.

Save the SUPPLIER details printed on invoices: name, address, IČO, DIČ, VAT payer + rate, bank account (the app derives the IBAN for the QR payment), e-mail, number prefix, default due days. scope = 'org' (the shared details of the whole organization, administrator only; default for an administrator) or 'me' (the user's OWN details — they take precedence over the shared ones for their invoices and get their own number series; default for a member). Pass only the fields to change; empty string clears a field. The user confirms on a card. Never invent an IČO, address or account.

Turn the public link of a project (map) on or off — on, anyone who reaches the instance's address can view it (read only). Project owner only. The user confirms first.

Give icons (one emoji each) to several steps of a map at once — when the user asks for icons everywhere / for the whole project / for a list of steps. Read the map with get_map first (it shows which steps already have an icon); items = exact node titles with the emoji; the project goal (apex) counts as a step too. Steps not listed keep their icon. The user confirms once for the whole list.

Turn a notification type on or off for the user: in-app and/or e-mail (e-mail only when the instance has e-mail configured). type = one notification type (as listed by get_settings) or "all". Pass only the channels to change. Applied right away with an undo link on the card; turning e-mail off or turning everything off goes through a confirmation card first.

Change ONE personal preference of the user: language (cs|en), theme (light|dark), mode = view (auto|lite|full; lite = simplified phone view; the assistant is available there too via the robot button at the top — the user confirms on a card because the screen changes), readability of the map (normal|large|titleOnly), align_lock (none|classic|compact|bands), notify_email_mode (instant|digest|none; only when e-mail is configured), full_name, display_name. Theme, readability, align_lock and names are applied right away with an undo link on the card; language, notify_email_mode and mode = lite go t…

Enable or disable a rule of a map. The user confirms first.

Switch the user's visual skin. Ids: indigo (blue), contrast, terminal (green on black), sepia, ocean, les (forest green), pulnoc (midnight), svestka (plum), broskev (peach), grafit (graphite), rubin (ruby red), ruze (rose pink).

Give every member of this instance access to a project (map) — read or edit — or remove it (none). Named sharing stays untouched. Only the project's owner. The user confirms first.

Switch light or dark mode.

Share a project (map) with a person, or change their permission — "add him to the project" means this tool. permission: read = views and comments, work = collaborator (opens step details, asks for due-date changes; the default when the user does not say), edit = co-manager (edits the map and shares it further). member = an e-mail address (even without an account) or the exact name of a member of this instance (list_people). Only the project's owner or a co-manager can share it. The user confirms first.

Start a relax break for the user: a calm aquarium, beehive or ant colony scene, optionally with a countdown (the user can lock the screen and step away). Only after the user agreed or asked for it.

Start the user's work timer (stopwatch), optionally on a step of a map (map_id + node_id) or just with a label — a timer already running is stopped first (one at a time, like in the app header). The user confirms first.

Stop the user's running work timer; optional note (as in the app, a note on a timer that has no step becomes an idea in the buffer). The user confirms first.

Offer the user 2–4 concrete next steps as one-click chips at the end of your reply (phrased as instructions to you, e.g. "Put the blade under Workshop operations"). Call it at the end of every reply that does not use ask_user.

Remove a person's named access to a project (map). Only the project's owner or a co-manager. The user confirms first.

Rewrite or extend a saved document when the user asks ("make the e-mail more formal", "add the price to the note"). Send the WHOLE new text (not a diff). The previous version is kept — the user can restore it. Read the document with get_document first.

Change an existing event by id: your own, one in a shared calendar as admin/manager, or your own time off. Only the given fields change; an empty string clears time, end_day, end_time or calendar (calendar "" = make it personal). Moving `day` of a multi-day event keeps its length. participants replaces the whole list; remind false cancels the reminder.

Change the title and/or description of an idea in the user's idea buffer (idea = the exact title or the id from list_ideas). The user confirms first.

Change a member's role (admin|manager|user), the flags "AI agents manager" / "org structure manager" (administrator only) or their deputy (e-mail of another member, empty string = none). Never the user's own role. Deleting an account or resetting a password is NOT possible here — Organization settings. The user confirms first.

Update fields of one node: title, status (todo/in_progress/done), description, deadline (YYYY-MM-DD, empty string clears), planned_on (YYYY-MM-DD, today to +7 days, empty string clears — WHEN the key owner plans to work on it; this is how killBottleneck expresses priority, never by moving the deadline), owner (e-mail, empty string clears), wait_for_children, colour, icon (one emoji), who performs it (executor_kind / executor_name) and the automation wish (automation_wanted / automation_note). Unknown fields are rejected with the list of allowed ones. Marking status done may unblock waiting nod…

Change a position of the org structure (by exact title): holder (member e-mail, empty = vacant), deputy (member e-mail, empty = none), position_kind (position|function), title. The user confirms first.

Rename the organization and/or set the purpose of the instance (team = company/team, family = family & friends, solo = just for me). Administrator only. The user confirms first.

Update an automation rule. Pass only `enabled` to toggle it on/off; otherwise pass the FULL new shape (name, trigger, actions, optional conditions/node_id) — partial field edits are not merged. Edits apply to future events only and clear the rule's error state.

Who is away — time off from absence calendars that is approved or not subject to approval (pending and rejected requests are excluded) — in a day range; default today … +14. One line per person and absence. Read-only.