Fireflies (meeting transcripts for agents)

What it is

Fireflies records and transcribes meetings. Once your Fireflies key is saved, any agent on this computer can look up your Fireflies meetings when you ask about them ("what did we decide in Tuesday's ops sync?", "find the call where we talked about pricing"). The agent reads; it never changes anything in Fireflies and nothing is stored on your computer.

This is the same key "What should I do next?" uses to look through your meetings, so you enter it once.

Where to find it

How to turn it on

1. In Fireflies, create an API key under Integrations → Fireflies API.
2. In Omniscio, open Settings → Mission Control and paste it into Fireflies API key. It is stored encrypted on this computer.

That is all. Agents never ask you for the key; if it is missing they tell you to add it here.

How it behaves

• Status — an agent can check whether a key is saved. It learns yes or no, never the key.
• List — your meetings, newest first, with title, date, length, organizer, participants and a link to open the meeting in Fireflies. Up to 50 at a time, with paging and an optional date range.
• Search — the same list narrowed to meetings matching a keyword.
• One meeting — its details, the Fireflies summary (overview, short summary, action items, keywords) and the speaker-labeled transcript. Very long transcripts are cut at 1,500 lines and the answer says so.
• When something goes wrong — the agent gets a short plain reason: the key was refused, Fireflies is busy, the meeting does not exist, or Fireflies could not be reached.

For agents

Use the fireflies skill; the route reference is fireflies.md.

• Routes, in cli-server-fireflies-routes.ts: GET /fireflies/status, GET /fireflies/meetings, GET /fireflies/search, GET /fireflies/meetings/:id. Answers use the { ok, data } envelope.
• The three meeting-data routes take only the install-wide full-trust token (~/.amc/cli-token); a scoped session token gets a 403 tier refusal. /fireflies/status takes any valid bearer because it returns only { configured }.
• No saved key → 403 "Fireflies is not connected…". Bad input → 400. A Fireflies failure → 502 with a humanized error and code: SERVICE_UNAVAILABLE.
• The Fireflies client is fireflies-meetings.ts, which shares one GraphQL request helper with What Next's fireflies-transcripts.ts. Search words and ids travel as GraphQL variables, never inside the query text.
• This is control-server routes plus a skill, not an MCP server — by standing order.
• Invariants: fireflies-cli-contract.md.

Related

"What should I do next?" reads the same key to look through your meetings — see pm-what-next-investigator.md. Granola does the same job for Granola meeting notes.