Knowledge

Knowledge is where your agents keep what they learn while working in trackagoat, so the next agent doesn't have to work it out again. Each entry is one finding: a workflow that worked, a pitfall, a decision and why, something that happened, or a fact about your program. The knowledge brief is a short digest of older entries that every agent session starts with.

Say an agent spends twenty minutes working out why a creator's Instagram carousel posts show zero views. It records that as one entry linked to the project. Next week, a different agent (yours or a teammate's) asks about carousel views, and the entry comes back in its first call.

You'll find it in the app under Tools → Knowledge.

Knowledge, notes and documents#

trackagoat already has a Markdown document on every project, campaign, creator, video and person (Notes and documents). The two do different jobs:

Put strategy, instructions and background in documents. Put "we learned this the hard way" in Knowledge.

Entries#

Each entry has:

• Kind: Fact, How-to, Decision, Gotcha or Event.
• Title (up to 90 characters) and summary (up to 280). The summary is what agents load into context, so it's written to stand on its own: one or two sentences someone can act on without opening the entry.
• An optional body in Markdown with the detail.
• Up to 8 tags, saved in lowercase with dashes (Apify Costs becomes apify-costs).
• Links to the projects, campaigns, creators, videos, payout records or people it's about.
• A project, or none for org-wide entries.
• An optional valid until date for things that stop being true. trackagoat archives the entry the day after.

Every entry shows who added it and how: Added by an agent using claude-code for Sam for an agent, or Added by Sam in the app.

Confirming. When an agent relies on an entry and it's still true, it confirms it. You can press Still true on the entry in the app too. Confirmed entries rank higher. An entry nobody has confirmed for 90 days is marked Stale: agents check it before relying on it. Stale entries are never archived on their own.

No duplicates. Before saving, trackagoat compares the new entry with your active ones. If one already says nearly the same thing, the agent is told to confirm or update that one instead.

Archiving. Archive an entry that's wrong or out of date, with a reason, and optionally point to the entry that replaces it. Archived entries stop showing up for agents but stay searchable, and you can make one active again.

Pinning. Pinned entries are loaded into every agent session, next to the brief. Keep pins for the few things every agent should always know.

How agents use it#

When an agent connects over MCP, it gets:

• the organization's knowledge brief;
• the titles and summaries of pinned entries;
• how many entries there are and how many are new since the brief;
• the working rules below.

The rules tell the agent to:

1. Recall before working. Before any real task, it calls recall_knowledge with what it's about to do and the project, campaign or creators involved. Entries linked to those rank higher. It checks Knowledge before redoing an analysis someone may have done already.
2. Record what it learns. After it learns something reusable, it calls record_knowledge, one finding per entry.
3. Confirm what still holds, and update or archive what doesn't.
4. Offer compaction when the server suggests it, and never compact without asking you.

Agents also see related knowledge where they use it: getting a creator, one campaign's stats, or a project's Program Health includes up to 3 entries linked to it.

The knowledge brief and compaction#

As entries pile up, loading them all would cost too much context. Compaction folds older entries into the brief: one Markdown digest, at most 4,000 characters, that keeps the points still worth knowing. Your organization has one brief, and each project can have its own.

When it's suggested. trackagoat suggests compaction when any of these is true:

• more than 40 active entries;
• active summaries add up to more than about 6,000 characters;
• more than 15 entries were added since the current brief;
• more than 10 entries are stale;
• there's no brief yet and more than 10 entries.

When it is, the app shows a banner on the Knowledge page and your agent offers to do it.

How it works. trackagoat doesn't write the brief itself: your agent does, and you approve it.

1. The agent reads the current brief and the candidates: stale, expired, older and rarely used entries, and groups of entries that overlap.
2. It drafts a new brief that keeps what's still true and adds the lasting points of what it folds. Entries that overlap but should stay searchable can be merged into one new entry instead.
3. It shows you the draft. After you agree, it saves everything in one step. If someone changed the brief in the meantime, nothing is saved and the agent starts over from the new version. Pinned entries are only folded if you agree to include them.

Folded entries are marked Compacted and stay searchable. Every version of the brief is kept on the Brief tab, with who wrote it and through which agent. Restore brings back an earlier version and undoes the compactions after it: the entries they folded become active again. Org admins get a notification for every compaction and restore.

To start one yourself, copy the prompt from the banner into your agent, or ask: "Compact our trackagoat knowledge."

Who can do what#

The last three are org settings. An org admin changes them on the Knowledge page under Settings; they can't be changed through the API or MCP. Agents can read the settings, and what the person they're helping may do, so they only offer what that person can approve.

API#

Every Knowledge action is in the REST API under /api/v2/knowledge and in the MCP server. See MCP server: Knowledge and the Knowledge API reference.