Back to the archive

Takibi is a shared library for my AI agents

My agents kept creating knowledge in Notion without updating it. I built Takibi to give them shared sources, temporary notes, and permission to do specific jobs.

I gave my agents access to Notion because I wanted them to keep context between sessions.

They created a lot of knowledge. They were much less interested in updating it.

Every agent could write anywhere. Nothing cited where it came from. Each handoff depended on what the previous agent had remembered to write down, in its own words.

I still had to work out what was current, what repeated something we already knew, and what the next agent should trust. I kept ending up with more to maintain.

I built Takibi because I wanted to choose the sources my agents worked from, without stopping them from keeping notes or getting on with a task.

It is a shared knowledge base for AI agents. I organise documents into projects and folders and choose which tools can access them. Connected tools retrieve passages from those sources and cite them in their work. Mine are the agents inside gobofu-os, my own front end: Meta Muse, Codex, and Grok, plus a Grok bot. Deliverables go to Google Drive.

My transcripts are one example

I use Capkiku to capture notes and call transcripts as Markdown into a folder on my Mac. I wanted those files in Takibi without uploading each one by hand.

Takibi’s CLI lets me give a Profile an explicit Uploads permission, off by default. A daily job files new captures into each client’s Uploads folder and remembers what it has already sent. That workflow may add transcripts, but it cannot edit or delete the library, and other agents still cannot add whatever they write to the sources.

Briefs change, and calls cover decisions that never make it into the brief. With both in the same project, an agent with access can search them while doing its work. Takibi returns verbatim passages with citations, and the agent writes its response from those passages. I can follow a citation and read what the source actually said, including the qualifications an agent might have left out.

One of those agents, Meta Muse, recently told me it could not verify whether a client’s knowledge profile was up to date. I pointed it at the Takibi project folder holding that information, and it answered from the retrieved passages instead of guessing.

When sources disagree, Takibi flags the conflict and returns both sides. When nothing matches, it returns no passages, and my agents are instructed to say the evidence is not there instead of filling the gap. My next move is to broaden the question, fall back to search, or read the full document text. Sometimes I simply have not added the source yet.

Notes can be unfinished

An agent can leave a useful observation without adding it to the source documents.

Agents need somewhere to write while they work. A finding from one session can save the next agent from trying the same unsuccessful approach.

Takibi keeps agent notes separate from source documents. An agent can leave the problem it worked on, what it tried, what worked, and what to check next time. The notes are marked as untrusted, and the next agent can search them before retrying something odd.

I review them and collect useful ones into a draft. Before adding that draft to the source library, I check its claims and edit it. Notes expire after 30 days. Anything I want to keep longer has to become a source I have reviewed.

Permission for a job

A writing agent might read approved product material. A transcript uploader might file into specific client folders. I give them one shared Profile when they work together, or separate ones when their jobs need different access.

A Profile holds the document access, capabilities, and daily usage limits for its tools. Each tool gets a key belonging to a Profile, and tools on the same Profile share its access and, when enabled, its notebook.

The access settings let me choose folders or whole projects, decide which capabilities to enable, and pause a Profile when its tools should stop. Task boards attach the same idea to work: an outcome, constraints, and links to the sources to use.

What stays with me

Takibi does not decide what is true. When sources disagree, I see both sides and sort out which is current. A document that needs attention can sit held or quarantined, unavailable to agents until I resolve it.

I still maintain the sources. What I stopped maintaining is agent-written pages nobody reviewed.

Start with one source

If you struggle to keep context between agents or sessions, sign up for Takibi and add one source document you know well. Markdown, plain text, Word, or a PDF with extractable text will work.

Create a Profile with access to its folder, connect an agent that can run the CLI or make API requests, and ask a question the document answers. The getting-started guide walks through it.

Open the citation and check the passage. Then ask something the document does not answer.