Quickstart: Consultant
If you bill by the hour and your value depends on remembering what every client said three weeks ago, this is for you.
What you get
- Morning briefing in Telegram — every day at 07:00, a synthesis of what’s new across clients, what’s overdue, and what’s contradictory
- Auto-captured Fireflies meeting notes — every Fireflies call lands in your vault, tagged by client, with action items extracted
- Notion sync for deliverables — your client-facing Notion stays in sync with your private vault; you write once, it appears in both
- Contradiction alerts — when a client says X on Monday and Y on Friday, Exocortex tells you
Prerequisites
- Docker (Desktop or engine) on Linux/macOS/Windows
- A Fireflies account with API access (Pro plan or higher)
- Optional: a Telegram bot token for morning briefings (free, ~2 min to set up via @BotFather)
Screenshot
Step 1: Start the stack
git clone https://github.com/hretheum/exocortexcd exocortexcp docker-compose.override.yml.example docker-compose.override.ymldocker compose up -d --buildWait ~2 minutes for the database and workers to come up. Check health:
curl http://localhost:8000/healthStep 2: Connect Fireflies
Edit .env:
FIREFLIES_API_KEY=fk_your_key_hereRestart the Fireflies worker:
docker compose restart fireflies-syncThe next time you finish a meeting, the transcript and summary will appear in your vault within ~30 minutes.
Step 3: Set up Telegram notifications
- Message @BotFather on Telegram, run
/newbot, follow the prompts. Save the token it gives you. - Message your new bot once (just say “hi”) so it can DM you.
- Get your chat ID:
curl https://api.telegram.org/bot<TOKEN>/getUpdatesand look for"chat":{"id": ...} - Add to
.env:
TG_BOT_TOKEN=123456:ABC...TG_CHAT_ID=987654321- Enable the Telegram profile:
docker compose --profile telegram up -dStep 4: First night shift
The Night Shift runs at 03:00 UTC by default. To trigger it manually right now:
docker compose exec api python -m exocortex.workers.synthesizer --oncedocker compose exec api python -m exocortex.workers.telegram_daily_digestWithin seconds, you’ll get a Telegram message with the morning briefing.
A day in the life
| Time | What happens |
|---|---|
| 07:00 | Telegram briefing lands. Skim it on your phone. You see one new contradiction flagged (client said “approved” Friday, “let’s revisit” today). |
| 10:00 | Standup with Client A. Fireflies records it. |
| 10:30 | Meeting ends. ~5 min later, the transcript is in your vault under wiki/work/meetings/2026-05-25-client-a-standup.md, tagged client-a. Action items extracted automatically. |
| 14:00 | Client B call. Same thing. |
| 17:00 | You glance at wiki/work/clients/client-a.md — auto-compiled dashboard shows the last 5 meetings, open action items, decisions made this month. |
| Friday | Gap Radar weekly report drops. You see one client cluster with 4 meetings but no synthesized decisions. Prompt to review. |
Next steps
- Configure your sources — connect Gmail, RSS, Notion mirror
- Read about Two-Way Cockpit — how to make Notion your client-facing surface while keeping your private graph
- MCP tools reference — ask questions in Claude Desktop with your knowledge as context