Changelog

Pick companions and cards in Chat, and review work with Emi

Type @ to pick a companion, # to pick a card or / to run a command. Emi can propose more changes to your cards and help you review finished work. Every change still waits for your approval, and accepting work stays your click.

• Pick a card with # and Emi gets it already opened, so nobody searches for it or copies a link.
• Five commands: /inbox shows what’s waiting on you, /status shows who’s working and who’s free, /review opens a card’s review, /card opens a card, and /assign prepares an assignment for you to approve.
• Cards Emi created show their live status in the chat. Proposals, receipts and reviews now share one clearer layout, and new ones land at the bottom of the chat.
• Emi can propose moving, blocking, unblocking and archiving cards, with up to 10 changes in one proposal. She can also read hand-ins, run status and your Inbox.
• After reading a hand-in, Emi can propose Send back with her notes, or a follow-up card such as a QA check for another companion.
• Companions can check long lists of URLs, pull page facts such as titles and headings, search and read pages in batches, and check sitemaps and llms.txt files.
• Several cards can now run at once.
• Browse Drive: pick the folders a collection can use by browsing them, with no links to paste.

Meet Emi, your AI manager

Emi lives in Chat. Ask her what’s blocked, what finished this week, or to plan a piece of work, and she answers from your boards and documents. When she suggests a change, like a new card or a note, it waits for your approval before anything happens.

Companions: AI teammates that work your cards

Add a ready-made companion, like an SEO Analyst, Content Writer or Lead Researcher, to a collection, assign it a card, and it does the work with the apps you connected. Results come back to your board for review.

• Add a companion from a ready-made role, or create one with your own role. Pick the collections it works in and the apps it can use.
• Ember includes 3 companions and Campfire 10. Both plans include AI usage for companion runs, chat and Takibi web search, which resets with your billing period. Add your own OpenRouter key to use other models.

Wake a card later.

Stuck until a date? Give the card a wake time and Takibi reminds your agent when it comes, instead of the date sitting in a note nobody rereads.

• Set it under Wake on the card, or have an agent run takibi tasks wait <id> --until <time> --reason "..." (CLI 1.23.0). The card is marked blocked, and it doesn’t land in your inbox.
• When the time comes, the card shows Wake due and subscribed webhooks get task.wake_due. The card stays blocked, with the same assignee, until someone checks and unblocks it.
• Times need a time zone, so bare dates and anything more than a year out are refused. Unblocking, reassigning, archiving or finishing the card cancels the wake time.

Watch agents work, live.

Boards, the inbox and activity now update the moment something changes. When an agent moves a card, its pointer carries the card across the board and says what it did.

• No more reloading: moved cards slide straight to their new column.
• Each Profile has its own robot and color, so you can tell agents apart at a glance. Your own changes never show a pointer.
• Prefer a quiet board? Turn off Agent pointers in Settings → Account. Cards still update live, and pointers stay off if your system asks for reduced motion.

Approve doc fixes on the card.

When an agent spots outdated text in your documents, its card now lists each passage next to the suggested fix. Apply or skip each one, with no copying and pasting.

• Go through the suggestions on the card’s Artifacts tab. Apply updates the document; Skip sets it aside, with an optional reason.
• Your choices are saved on the card, so the agent won’t suggest the same fix again.
• If the document changed since the suggestion was made, it’s marked as a conflict instead of overwriting your newer text.

A clearer webhook page.

Each webhook now opens on its delivery history. What it listens for and where it sends are one tab away, and each tab saves on its own.

• Recent deliveries come first, with the same filters, Replay and test buttons.
• A save bar appears only while you have unsaved changes.
• The header shows where deliveries go and what triggers them, and only warns you when something actually fails.

Assistants can update cards.

A connected assistant can now move the card it’s working on, mark it blocked and attach its results.

• It can only change the card it picked up, while it holds it, and only if Connector writes is on for that Profile.
• Assistants can send work to Review, but they can’t accept it: that happens in the app or the CLI. An assistant can still pull its own card back out of Review.
• Profiles that orchestrate can finish a fresh card straight away, but rejected work has to be redone and sent back to Review.
• Assistants can read any attachment their Profile can see, even on read-only connections, including your feedback when you send work back.
• Subscribe a webhook to task.note_added to hear each time an assistant leaves a note. If Connector writes was already on, there’s nothing to re-enable.

Assistants can pick up cards.

A connected assistant can now pick up a task card, leave short notes on it and hand it back. A card stays with it for 30 minutes at a time.

• It needs two things: an assistant that supports picking up cards, and Connector writes turned on in the Profile’s Access tab. Without both, it can only read.
• An assistant works one card at a time and can leave up to 3 draft notes each time it picks one up. Handing it back, or turning the switch off, frees the card for others.
• The connect screen tells you about this access before you approve, and Disconnect in Settings → Security cuts it off right away.

Assistant use shows as activity.

Profiles you only use through a connected assistant now show when they were last active, instead of Never used.

• Last active, the online dot and the unused-key alert all count assistant use.
• Move a connection to another Profile and its activity starts fresh there.

Filter what webhooks send.

Each webhook can now be narrowed down: only cards held by one Profile, only moves into certain columns, none of the owner’s own changes, or one delivery per action.

• Only cards held by sends a change only when the card ends up with the Profile you pick. Only moves to limits status changes to the columns you pick.
• Pick a Profile under Owned by, then turn on Skip the owner’s own writes to ignore that Profile’s changes. Handoffs between bots still go through.
• Collapse one action into a single delivery sends one delivery listing every change, instead of one per change.
• Two setups cover most needs: a worker that wakes only when a card lands with it, and a watcher that sees every handoff and finish.

Assistants can read cards.

A connected assistant can now open one task card, with the same access its Profile has in the app.

• Give it the card from a webhook or the board, plus the collection it’s in.
• Its Profile needs access to the whole collection. Anything else looks like it doesn’t exist.
• Handy when a webhook wakes your agent: it reads the latest card before replying.

Bring your own signing secret.

If the app receiving your webhooks gives you its own whsec_ signing secret, paste it into Takibi. That’s what makes webhooks work with Grok.

• Paste it into Signing secret when you create the webhook, or later with Paste a whsec_ secret instead (Replace once one is set). Only whsec_ secrets work.
• The page shows the secret’s last four characters, so you can tell which one is in use.
• A pasted secret takes over at once, with no overlap: switch it while the webhook is off, then test and turn it back on. When the other app rotates its secret, paste the new one.

Connect from Cursor.

Add Takibi to Cursor, sign in, and pick which Profile it works as.

• Add the server address and Takibi’s Cursor client ID to mcp.json. No secret needed, but type the ID exactly as shown.
• Cursor can ask questions with sources, list your collections and open documents. It can’t change anything.
• Grok Bot has a matching client ID, and the connect screen names it.

Mark a Profile as you.

Choose Mark as me from a Profile’s ⋯ menu and that Profile shows your own picture across the app.

• Your picture follows it across Profiles, tasks, activity, logs, Home, Notes and the inbox. Mark another Profile to move it. Only you ever see your picture.
• Work you do yourself shows your picture too, labeled you or Founder, including in document history. Other Profiles keep their robots.
• The webhook failure badge now uses the webhook icon.

Zapier (private beta).

Connect Takibi to thousands of apps through Zapier. Accept the invite, paste a Profile key, and build Zaps that file documents, manage tasks and ask your collections.

• New Document and New Task start a Zap when something lands in a collection.
• Create Task, Append Note and Upload Document write to Takibi. Ask Takibi answers with quotes from your documents and how strongly they back the answer.
• Each Zap step only needs the permission it uses, and the connection test shows what the key can see.

Read a follow-up’s parent.

With CLI 1.19.0, takibi tasks get <id> --with-parent shows the card a follow-up came from: its description, plus its attachments with the command to read each note.

• Without the flag, the CLI reminds agents that the parent card exists.
• --ancestors <1-3> goes further back, and TAKIBI_WITH_PARENT=1 always includes one level.
• Archived parents come with a note. If a parent is gone or off limits, the CLI notes it and carries on; connection or server errors still stop the command.

Accept or reject work.

Reviewing a card now ends in a clear decision. Accept approves it, and it waits in Review until you move it on. Reject sends it back with your note as feedback.

• Accept and Reject sit at the bottom of the card. Accepted cards show an Accepted badge until you move them on. Rejected cards go back to To do, with your note as Founder feedback.
• Agents can do the same with takibi tasks accept and tasks reject (CLI 1.18.1). Add --to in_progress to send a rejected card to In progress instead.
• The History tab is now Activity: edits, handoff notes, assignments, moves and decisions in one timeline, newest first.
• Edit, Archive, Instructions and Delete moved into the card’s top menu. Accepted cards leave your inbox.

Read all notes at once.

With CLI 1.17.0, the new Read all notes permission lets one Profile read every Profile’s notes. Run takibi notes list --all-authors --since <date> to gather the week’s lessons in one list.

• Narrow it with --project or --author. Each note shows who wrote it and when.
• Reading notes this way changes nothing. Keys without the permission get a clear error.
• notes append now warns when you leave out --project, since notes without one are easy to miss later.

Connect your assistant.

Sign in to Takibi from your AI assistant and pick which Profile it works as.

• It reads only what that Profile can read, and it can’t change anything.
• It answers from your collections, lists them and opens the documents it cites.
• Every connection shows in Settings → Security, where Disconnect cuts it off right away.

Mark cards blocked from the CLI.

With CLI 1.16.0, agents can mark a card blocked and say why with takibi tasks update.

• tasks update <id> --blocked --reason "..." marks it blocked with the reason.
• Pass --reason alone to change the reason and nothing else.
• --unblocked clears it.

Copy instructions for your agent.

The Instructions button at the bottom of a card copies a short prompt with the card’s ID and title.

• Paste it into your agent, like Desk. It tells the agent to read the card before replying.

Agents can create and edit cards.

With CLI 1.15.0, takibi tasks create adds a card and tasks update changes its title, description or due date. Both need the Create tasks permission.

• New cards start in To do, unassigned unless you pass --assignee.
• tasks get now opens one card directly instead of scanning the board.
• skill --install --dir works once per custom folder, and the CLI needs Node.js 20 or newer.

Follow-up tasks.

Choose Follow-up at the bottom of a card to start a new To do card linked back to the original.

• The original keeps its status, assignee and history. Nothing moves backwards.
• Related work in Details links both ways, and the board shows how many follow-ups each card has.
• Deleting a card leaves its follow-ups in place as tasks of their own.

Card history.

Each card has a History tab that keeps earlier titles and descriptions, plus handoff notes and who wrote them.

• Open History to read earlier versions: the original, recent edits and recent handoff notes.
• Use this text puts an old version back on the card.
• Restoring keeps the replaced text in History, so you can undo it.

Notes on cards.

Cards can hold markdown notes. Agents attach theirs, and you can attach your own.

• Notes open right on the card, with a copy button. Drive and web links still work for sheets, slides and other files.
• A note can’t be edited once attached. To fix one, remove it and attach a corrected copy.
• Agents attach notes with takibi tasks artifact add --markdown and read them with tasks artifact show.

Card tabs.

Each card has Details, Artifacts and History tabs.

• Details holds review notes, the description and card settings. Artifacts holds notes and links.
• History holds earlier versions and handoff notes.
• Blocked cards say why in a banner, and links show the site name instead of the full address.

One inbox for every board.

The inbox lists what needs you on any board: questions from agents and finished work to review. Open it from the top right, the command menu, or G I.

• Choose a row to open the card on its board. It leaves the inbox once you answer, unblock or accept it.
• Cards an agent is stuck on come first, then questions, then reviews, oldest first.
• Cards waiting on someone else stay on their board. The inbox replaces the sidebar review count and the task counts on Home.

A redesigned task board.

The task board was redesigned: cleaner cards, drag and drop that follows your pointer, and filters that find any card on a busy board.

• Filter by text, assignee, status, blocked or overdue with Filters. Active filters stay in the toolbar and never shift the board.
• Review works like a to-do list: overdue cards come first, questions show a Waiting on you badge, and each card shows its handoff note next to Accept.
• Blocked cards can’t move to Done until unblocked, finished cards can be archived from the Done column in one go, and deleting a card removes it for good.

@mention Profiles.

Type @ in a card’s Context to bring a Profile in, then pick a name from the suggestions.

• The suggestions show Profiles that can work on that board.
• Saved mentions show as name tags on the card.
• Agents read the same @mentions you write.

Webhooks catch new assignments.

Creating a card with an assignee now sends an assignment event, so agents that only listen for assignments hear about it.

• No more unassigning and reassigning a new card to wake your agent.
• The webhook board picker shows how many boards there are, with a shorter list you can scroll or search.
• Refreshing deliveries shows progress and tells you when the list is up to date. Webhook actions confirm their results.

Webhooks for tasks.

Give Takibi your agent’s address and pick which boards and task changes should wake it up.

• Get notified when cards are created, assigned, moved or blocked.
• Test the connection before turning it on, and check the signature on each request.
• Change signing secrets with a 24-hour overlap. Temporary failures get up to six attempts, and you can replay any failed delivery.

Upload files from the CLI.

With CLI 1.8.0 and the Uploads permission, takibi doc upload <file> adds a document to a collection the agent can reach.

• PDF, Word .docx, Markdown and text, up to 10 MB each.
• Pick where it goes with --project <name-or-uuid> and --folder <uuid>.
• If a file is held back or refused, the CLI says why.

Let a Profile upload files.

Turn on Uploads for a Profile so its tools can add documents to collections it can reach.

• Agent uploads get the same checks and limits as uploads in the app.
• A Profile with folder access can only upload into those folders. Documents outside folders need access to the whole collection.
• Uploads stay off until you turn them on for that Profile.

Conflicting notes link up.

When two bot notes disagree, each one now links to the other instead of being hidden. Read both before trusting either.

• A Conflicts with N badge marks notes that disagree.
• Open a note to see what it disagrees with.
• Drafts made from notes show their conflicts too, so nothing slips through unchecked.

Edit Profile budgets.

Open a Profile to change its daily token budget or ask limit at any time.

• Set it below what’s already used today and new calls stop until you raise it or usage resets at midnight UTC.
• The activity log records each change and the new limits.
• Usage meters in Settings update as soon as you save.

Task and note permissions.

Choose what each Profile can do with tasks and whether it can keep notes. Every key on that Profile shares those permissions.

• Choose whether it can pick up cards, create them or assign them.
• Profiles can update cards assigned to them, and still see other cards on boards they can access.
• Turn notes on separately, and use another Profile when a tool needs different permissions.

Guided Profile setup.

Name the Profile, choose its permissions and document access, then copy its first key.

• Each step explains what the Profile will be able to do.
• The key card spells out its access in plain words.
• Save the key when it appears. It’s shown only once.

Teach your agent Takibi.

takibi skill --install adds instructions that teach your agent how to use Takibi.

• Works with Codex, Claude and .agents skills folders.
• Run takibi skill to print them instead.
• The CLI mentions it once on first run, then stays quiet.

Review what bots remember.

Notes now have a review queue and a searchable list for each Profile, and you can turn the best ones into a draft document.

• Open a note without losing your place in the list.
• Keep useful notes, or remove ones your bots should stop seeing.
• Copy or download the draft after checking each point against your documents.

Update reminders in the CLI.

Once a day, the CLI checks for a newer version and prints a one-line notice.

• The notice never mixes into command output, so scripts and --json stay clean.
• It stays silent when offline, and you can turn it off.
• Single-file installs get a download link instead of npm instructions.

Collection names in the CLI.

takibi projects shows what a key can reach, and --project takes names instead of IDs.

• Keys with one collection can skip --project entirely.
• If two collections share a name, the CLI stops and asks for the ID instead of guessing.
• Offline, names still work from the list saved by takibi projects --add.

See tags before adding more.

The tag dialog shows the tags already applied at the top and keeps the full list behind a toggle. The Profile access editor takes less space.

• Applied tags show above your new ones, so you never add the same tag twice.
• Long tag lists start collapsed. Type to find a tag.
• Saved access takes up less room, with folders grouped under their collection.

Tag many files at once.

Select files anywhere in Documents and tag them together from the floating action bar.

• Pick an existing tag or type a new one.
• Tag files from different collections in one go.
• The action bar moves with the page and stays clear of Tibi.

Tibi on every screen.

Tibi, the helper in the bottom right, now works on every screen, with guide links, billing tips and timely reminders.

• Most screens link to their guide, which opens in a new tab.
• After a key is shown, Tibi reminds you to save it before you leave.
• Press ? to open it anywhere. It never pops up on its own.

Edit cards in place.

Change a card from its details when the requirements change.

• Change the title and description without making a new card.
• Update the due date and note why a card is blocked.
• Edit or remove links attached to the card.

Merge related documents.

Choose Consolidate on two related documents to review a merged version before it replaces them.

• Copy a prompt with both texts to give your agent.
• Paste the merged Markdown back into Takibi and name the file.
• Takibi uploads the merged file before removing the two originals.

The Takibi CLI.

The CLI and its skill let agents use your knowledge base and work on tasks from the tools they already use.

• Ask questions and search documents with a key limited to what you allow.
• List and pick up cards, update their status and attach links.
• Use JSON output when another tool needs to read the result.

Activity links to its work.

Task and document entries in Logs and the Home activity feed now link to what they describe.

• Open the card or document preview straight from the entry.
• Takibi switches to the right collection when needed.
• Deleted or expired documents stay as plain text, without a broken link.