Feature request: Expose Epoch companion output programmatically (hooks / file / event)

Summary

The Epoch companion (the turtle that comments in the speech bubble) often raises useful observations — security concerns, edge cases, second opinions on code changes. Currently, these are visual-only: the user sees them but they don't enter the conversation context unless manually copy-pasted.

Request: Expose Epoch's comments programmatically so they can be captured and injected into the agentic loop.

Use case

In our workflow, Epoch frequently catches things that would benefit from Claude acting on them directly — e.g., "could this cause email spam?" during a code change. Today the user has to read Epoch's bubble, copy the text, and paste it as a new message. This breaks flow, especially in fast-paced sessions.

If Epoch's output were accessible, it could serve as an automatic "second reviewer" whose observations feed back into the conversation without manual intervention.

Proposed approaches (any of these would work)

1. Hook event OnEpochComment — fires when Epoch generates a comment, with the comment text available to the hook. The hook could inject it into context via user-prompt-submit or similar.

1. File output — Epoch writes its latest comment to a known path (e.g., ~/.claude/projects/.../epoch-latest.json with { timestamp, comment, context }). A user-prompt-submit hook could read and inject it.

1. System prompt injection — Epoch's comment is automatically appended to the next user message as a <epoch-observation> tag, similar to how <system-reminder> works today.

1. Session JSONL integration — Epoch's comments are logged in the session file alongside tool calls and messages, making them retrievable for post-session analysis.

Why this matters

Epoch is positioned as a "watcher" — but a watcher whose observations are only visual is an incomplete feedback loop. Making its output programmatic would:

• Enable automated review workflows (Epoch flags concern → Claude addresses it)
• Create audit trails of what Epoch observed during a session
• Allow hooks to route Epoch observations to external systems (Slack, logs)
• Make the companion genuinely agentic instead of decorative

Environment

• Claude Code CLI + Desktop (Windows 11)
• Opus 4.6 with hooks and custom skills