docs: update AGENTS.md and README for platform reorg (#381)

* docs: update AGENTS.md and README for platform reorg and Slack outbox C&C

* docs: cover Google Workspace, Linear, and Jira integrations in README

Author: anish749

AGENTS.md

@@ -44,10 +44,10 @@ cmd/pigeon/main.go → cli.Execute()
        ↓
   internal/hub          Routes incoming messages to connected Claude Code sessions via SSE
        ↓
-  internal/listener/*   Platform-specific listeners (slack, whatsapp) — write to store, observe identity
-  internal/gws/*        Google Workspace pollers (drive, gmail, calendar)
-  internal/linear/*     Linear issue poller
-  internal/jira/*       Jira issue poller
+  internal/platform/*   Per-platform adapters, each with its own manager/poller/auth subpackages:
+                           slack, whatsapp   — listeners that write to store, observe identity
+                           gws               — Google Workspace pollers (drive, gmail, calendar)
+                           linear, jira      — issue pollers, split into issue.jsonl/comments.jsonl
        ↓
   internal/store        Store interface + JSONL protocol v1 implementation (modelv1/)
   internal/identity     Cross-platform contact identity (Observer/Resolver pattern)
@@ -66,7 +66,7 @@ cmd/pigeon/main.go → cli.Execute()
 
 - **MCP Server** (`internal/mcp/server`): Runs inside Claude Code as a channel server. Connects to the daemon's SSE endpoint and delivers messages as channel notifications.
 
-- **Outbox** (`internal/outbox`): Queues outgoing messages from Claude for human review. `pigeon review` opens a Bubble Tea TUI for approve/reject.
+- **Outbox** (`internal/outbox`): Queues outgoing messages from Claude for human review. By default, review happens as command-and-control in Slack — the daemon posts a message to the owner's DM with approve/dismiss/send-mode/feedback actions (`internal/platform/slack/interactive.go`). `pigeon review` (hidden from help, still functional) opens a Bubble Tea TUI for the same approve/reject flow.
 
 - **Paths** (`internal/paths`): XDG-compliant directory resolution. Env overrides: `PIGEON_CONFIG_DIR`, `PIGEON_DATA_DIR`, `PIGEON_STATE_DIR`. Defaults: `~/.config/pigeon/`, `~/.local/share/pigeon/`, `~/.local/state/pigeon/`.
 
@@ -111,7 +111,7 @@ Both are scoped by `read.SearchDirs(workspace, platform, account)` which resolve
 2. Pollers receive GWS/Linear/Jira updates → write JSONL/content files through the store and typed paths
 3. Hub picks up new messages → pushes to connected MCP sessions via SSE
 4. Claude Code receives channel notifications → can read/search/reply via CLI
-5. Outgoing replies go to the outbox → human approves via `pigeon review` → sent via `api.Send()`
+5. Outgoing replies go to the outbox → human approves via Slack command-and-control (or `pigeon review`) → sent via `api.Send()`
 
 ## Error Handling
 

README.md

@@ -1,30 +1,38 @@
 # Pigeon
 
-Pigeon is a local-first messaging bridge for AI agents. It mirrors your messaging history as plain text files and lets AI agents read, search, and reply to messages through a CLI, or receive them in real time through Claude Code.
+Pigeon is a local-first bridge between AI agents and your messaging and workspace tools. It mirrors Slack and WhatsApp conversations, Gmail, Calendar, and Drive activity, and Linear and Jira issues as plain text files, and lets AI agents read, search, and reply through a CLI — with Slack and WhatsApp messages also delivered in real time through Claude Code.
 
 ## The Idea
 
-Messaging platforms generate a constant stream of context that AI agents could act on, but these platforms are designed for humans, not programmatic access. Pigeon solves this by maintaining a local mirror of your messaging history and providing a CLI that agents can use to navigate and search that history.
+Messaging and workspace platforms generate a constant stream of context that AI agents could act on, but these platforms are designed for humans, not programmatic access. Pigeon solves this by maintaining a local mirror of that history — Slack and WhatsApp conversations, Gmail/Calendar/Drive activity, Linear and Jira issues — and providing a CLI that agents can use to navigate and search across all of it.
 
-When connected to Claude Code, pigeon delivers messages in real time via channel notifications. Claude can then react to incoming messages, gather context from other tools, and draft replies, all while keeping a human in the loop for anything outgoing.
+When connected to Claude Code, pigeon delivers Slack and WhatsApp messages in real time via channel notifications. Claude can then react to an incoming message, pull context from a related Linear ticket, Jira issue, or Google Doc, draft a reply, and queue it for your approval, all while keeping a human in the loop for anything outgoing.
 
-This becomes powerful when combined with other agent-facing CLIs like [linear-cli](https://github.com/schpet/linear-cli) for issue tracking or [Google Workspace CLI](https://github.com/googleworkspace/cli) for docs and email. The agent can correlate a Slack question with a Linear ticket, pull context from a Google Doc, draft a reply, and queue it for your approval. Pigeon provides the messaging layer; the agent orchestrates across all of them.
+Pigeon builds on top of [linear-cli](https://github.com/schpet/linear-cli), [jira-cli](https://github.com/ankitpokhrel/jira-cli), and the [Google Workspace CLI](https://github.com/googleworkspace/cli): you authenticate through those tools, and pigeon uses that same auth to poll and mirror your issues and workspace activity locally.
 
 ## How It Works
 
 **Listeners** connect to messaging platforms (Slack, WhatsApp) and append incoming messages to local text files, organized by date. They run as a background daemon.
 
+**Pollers** sync Google Workspace (Gmail, Calendar, Drive), Linear, and Jira on a schedule, mirroring issues and workspace activity to local files the same way listeners mirror messages.
+
 **The CLI** lets agents (or humans) list conversations, read history, search across platforms, and send replies. `pigeon help` describes everything.
 
-**Channels** deliver messages to Claude Code in real time via MCP channel notifications. When a new message arrives, Claude gets pinged and can react immediately.
+**Channels** deliver Slack and WhatsApp messages to Claude Code in real time via MCP channel notifications. When a new message arrives, Claude gets pinged and can react immediately. Workspace and issue data from pollers is searched on demand rather than pushed live.
 
-**The Outbox** holds outgoing messages from Claude for human review. `pigeon review` opens a terminal UI to approve, reject, or provide feedback before anything is sent.
+**The Outbox** holds outgoing messages from Claude for human review. By default, review happens right in Slack: the daemon DMs you the pending message with buttons to approve, dismiss, or leave feedback. `pigeon review` opens a terminal UI for the same flow.
 
 ## Prerequisites
 
 - **[ripgrep](https://github.com/BurntSushi/ripgrep#installation)** (`rg`) — required for search, read, and file discovery. Install via `brew install ripgrep`, `apt install ripgrep`, or see the [ripgrep installation guide](https://github.com/BurntSushi/ripgrep#installation).
 - **[uv](https://docs.astral.sh/uv/getting-started/installation/)** — required for the embedding sidecar used by workstream routing. Install via `curl -LsSf https://astral.sh/uv/install.sh | sh`.
 
+Optional, only needed for the integrations you use:
+
+- **[Google Workspace CLI](https://github.com/googleworkspace/cli)** (`gws`) — for `pigeon setup-gws` (Gmail, Calendar, Drive). Run `gws auth login` first.
+- **[linear-cli](https://github.com/schpet/linear-cli)** — for `pigeon setup-linear`. Run `linear auth login` first.
+- **[jira-cli](https://github.com/ankitpokhrel/jira-cli)** — for `pigeon setup-jira`. Run `jira init` and export `JIRA_API_TOKEN` first.
+
 ## Installation
 
 Download the latest release for your platform:
@@ -67,11 +75,20 @@ pigeon daemon start
 pigeon claude
 ```
 
+Set up Google Workspace, Linear, or Jira to mirror them for search (no live Claude Code delivery):
+
+```bash
+pigeon setup-gws                    # after `gws auth login`
+pigeon setup-linear                 # after `linear auth login`
+pigeon setup-jira                   # after `jira init` + JIRA_API_TOKEN
+pigeon daemon start
+```
+
 Run `pigeon help` for the full list of commands.
 
 ## Multi-Account
 
-Pigeon supports multiple Slack workspaces and WhatsApp numbers simultaneously. Each account gets its own listener, message store, and session binding. The daemon manages all of them, and `pigeon claude` lets you pick which account to connect.
+Pigeon supports multiple accounts per platform — several Slack workspaces, WhatsApp numbers, Google Workspace accounts, Linear workspaces, and Jira configurations simultaneously. Each gets its own store under the data root, and the `--workspace` flag scopes CLI operations to a subset of accounts. Slack and WhatsApp accounts additionally get a session binding: the daemon manages all of them, and `pigeon claude` lets you pick which one to connect.
 
 ## Architecture
 
@@ -91,8 +108,10 @@ Pigeon supports multiple Slack workspaces and WhatsApp numbers simultaneously. E
    (storage)    (via MCP channel)
 ```
 
-The **daemon** runs all platform listeners, serves a Unix socket API, routes messages to connected Claude Code sessions, and manages the outbox.
+The **daemon** runs all platform listeners and pollers, serves a Unix socket API, routes Slack/WhatsApp messages to connected Claude Code sessions, and manages the outbox.
 
-The **hub** routes incoming messages to the right Claude Code session. One session per account. Handles session lifecycle: connect, disconnect, and handoff when a new session replaces an old one.
+The **hub** routes incoming Slack and WhatsApp messages to the right Claude Code session. One session per account. Handles session lifecycle: connect, disconnect, and handoff when a new session replaces an old one.
 
 The **MCP server** runs inside Claude Code as a channel server. It receives messages from the daemon via SSE and delivers them as channel notifications that Claude can act on.
+
+Google Workspace, Linear, and Jira pollers run inside the same daemon and write to the same text-file storage on a schedule, but they don't go through the hub — that real-time push to Claude Code is Slack/WhatsApp only. Their history is searched on demand via the CLI instead.