Ormaos: What happened inside your Python execution?
a day ago
- Ormaos records actual runtime execution paths, not just source code possibilities, showing which branches ran, loop iterations, swallowed exceptions, etc.
- It is designed for coding agents to query from the terminal, but is also human-readable, and provides output with next suggested questions.
- Open source under Apache 2.0, self-hostable, CLI only (no dashboard yet), supports Python 3.12+ via sys.monitoring (PEP 669).
- Three recording levels: Level 1 (basics like duration, HTTP calls, exceptions), Level 2 (call tree for whole process), Level 3 (line-level path inside scoped functions/modules).
- Does not replace existing observability tools like Sentry or Datadog; instead complements them for deep investigation of specific runs.
- Recording is on-demand (via `ormaos run` or inline `with ormaos.record():`), not always-on, and can be scoped to avoid performance overhead.
- It shows swallowed exceptions and lines that never ran, which helps understand failures without adding prints or breakpoints.
- Supports threads, asyncio, child processes, and frameworks like Django ORM, requests, httpx; Linux first, macOS planned.
- First release scheduled for November 2026, with future directions including deeper interpreter integration and lighter always-on recording.