Omegon agent

Flynt embeds Omegon through ACP as a project-scoped operating surface, not a generic chatbot.

What the agent can see

The Flynt agent uses project-local tools for documents, tasks, graph, lenses, visual artifacts, UI state, and runtime diagnostics. The active project root defines its working boundary.

Runtime preflight

The agent panel reports deployment and CLI readiness before prompting. A non-blocking warning means Flynt can run but deployment provenance is still being verified; a blocked state requires runtime settings.

Stop Agent and stale tools

0.12.1 hardens the panel boundary. Stale tool-call UI states are bounded, and Stop Agent detaches the panel immediately while process cleanup runs asynchronously with a timeout.

Project → Omegon

The Project navigation includes an Omegon surface for project-local agent state such as the agent journal, ACP deployment manifest, and plugin/runtime cache state.