Filo joins your conversations. Wherever they happen.
An AI participant for engineering teams. Designed to join your Slack threads, meetings, and coding sessions, and capture the why behind every decision while it's still fresh.
Filo: 3 questions · 1 decision saved
#eng-architecture
Should we use Postgres or DynamoDB for the new orders service?
09:30
Architecture sync
6 attendees · scheduled 30 min · "decide today"
11:15
Claude Code
Refactor orders module — Postgres adapter, schema migration plan
14:40
Active
Use Postgres for orders service
15:05
Designed for the surfaces your team already thinks in.
Slack first. Meetings, code review, and coding sessions next.
Phase 1
Slack
Phase 2
Google Meet
Phase 2
Linear
Phase 3
Cursor
Phase 3
Claude
Phase 3
Notion
Observes the conversation. Asks when there's a gap.
Filo isn't a checklist. It watches a decision form, and when context is thin — a missing alternative, an unstated assumption, an owner without a name — it steps in. Examples of what it might ask:
01What alternatives did you consider?
02What would have to be true for you to reverse this?
03Who's on the hook if it goes wrong?