Diagnostics and developer experience

What it is

When Omniscio misbehaves — it is slow to start, the window freezes, a reply goes missing, or a session simply disappears — the answer is rarely on the screen. This area is the collection of tools that record what happened and let you hand the evidence to someone (or to an AI) who can read it.

It runs from the deep end to the shallow end. Deepest, files on disk hold the authoritative log, a continuous heartbeat tape, and per-incident traces. One level up, in-app panels let you watch those records live, inspect memory and the processes Omniscio has spawned, and export a support bundle. And at the surface, the app gives you a one-click way to report a problem with the diagnostics already attached, and to see which build is actually running. "Developer experience" here simply means the tools a developer would reach for are reachable from inside the app, without a terminal.

The detachable windows belong to this area only as a workflow aid — popping a session or a project into its own window so you can watch several at once beside other work.

Where to find it

• Settings → Diagnostics — the log level, the log-files card, the crash-dumps folder and the export-for-support action, plus the Running build card (branch, short commit, build time).
• The toolbar — the Debug Logs button (a terminal icon) opens the live log viewer; the bug icon opens Send Feedback.
• Settings → Maintenance → Resources — the in-app process monitor.
• A session's ⋯ menu — Pop Out to Window detaches a single session.
• The projects sidebar — right-click → Open in new window detaches a project or an integration panel.

How it behaves

Each part of the area is owned by its own page:

• The logs and the support bundle — the rotating log files and their archive, the separate bootstrap log, the live Debug Log Viewer, exporting a bundle, and automatic crash reporting: Logs & Debugging (where to find logs, export for support).
• The silent-crash trail — the heartbeat tape that explains a window that simply vanished, with no crash dialog and no error report: Main-process heartbeat (silent-crash forensic trail).
• Filing a report — the in-app Send Feedback dialog and the local route that mirrors it, with device diagnostics attached automatically: CLI Feedback Submission (file bugs / feature requests from external AI).
• Startup evidence — a single self-contained file capturing the timeline of the most recent launch: Startup trace (single-file launch performance log for bug reports).
• Latency evidence — a continuous tape of slow clicks, keypresses and rendering stalls: Interaction trace (slow-click, jank, and navigation latency log).
• Watching processes — a read-only, Task-Manager-style view of every process Omniscio has spawned: Resources Diagnostic Panel (in-app process monitor).
• Memory investigations — an endpoint that captures a heap snapshot and returns a small summary of where the memory is going: Heap snapshot diagnostics (memory bloat investigation via CLI).
• Detaching a session — popping one session into its own window: Detached session window (Pop Out).
• Detaching a project or panel — opening a whole project or an integration panel in its own window: Pop out a project or integration window.

Related

• Logs & Debugging (where to find logs, export for support) — where the logs live, the live viewer, the support bundle and crash reporting.
• Main-process heartbeat (silent-crash forensic trail) — the tape that records the app's health so a silent crash can be explained.
• CLI Feedback Submission (file bugs / feature requests from external AI) — the in-app Send Feedback button and the route that mirrors it.
• Startup trace (single-file launch performance log for bug reports) — one file for "the app feels slow to start".
• Interaction trace (slow-click, jank, and navigation latency log) — a tape of slow clicks and stalls.
• Resources Diagnostic Panel (in-app process monitor) — live CPU and memory for every process Omniscio spawned.
• Heap snapshot diagnostics (memory bloat investigation via CLI) — capturing and summarizing renderer memory.
• Detached session window (Pop Out) — popping one session into its own window.
• Pop out a project or integration window — opening a project or integration panel in its own window.