# Product

> Flare is the context system for teams that build with AI agents. Arlo plans the work, Oren keeps what meetings decide, Nori handles customers, and Signals watches production. All four write into one context graph, and your coding agents read it through Flare MCP.

## The four agents

1. **Arlo · Projects** — Turns the discussion into work you can argue with: specs, epics, stories, acceptance criteria, in shipping order. Marks what must wait. https://flares.in/arlo
2. **Oren · Meetings** — Knows a decision from a maybe. A decision writes onto the project; a maybe stays parked; a bug leaves as a staged ticket with its transcript line. https://flares.in/miro
3. **Nori · Customers** — Answers from what Flare knows. Anything else becomes a ticket with the screen, console, network, and replay attached. https://flares.in/kiro
4. **Signals · Production** — Crashes and dead clicks group into one incident with the evidence; send it to your IDE. https://flares.in/signals

## The graph in the middle

Every agent reads what the others wrote. A decision recorded on Tuesday is already on Thursday's ticket.

## Who reads it

- **The app** — your team works in Flare: projects, meetings, tickets, signals, and an inbox.
- **Flare MCP** — Cursor, Claude Code, Codex, Claude, and ChatGPT read and write the same graph with scoped tokens and audited writes. https://flares.in/mcp
- **REST and OpenAPI** — the same operations over REST with an OpenAPI 3.1 spec. https://flares.in/developers

---
Site map: https://flares.in/sitemap.xml · Machine-readable summary: https://flares.in/llms.txt · Start with the planner: https://flares.in/arlo