Building production AI agents and LLM systems with TypeScript & Python. Sharing architecture decisions, failures, benchmarks, and code from real projects.
I’m building AI developer tools in public.
Not demos—products with real constraints: local inference, native IPC, developer workflows, resumable pipelines, and human approval.
I share the architecture decisions, tradeoffs, and code behind them.
What I’m building ↓
Automatic GitHub/GitLab CI ingestion is not included yet — that’s a future integration target. For now, you can paste or upload evidence manually.
https://t.co/ZaCeyiclqK
Röntgen AI: Relay build pipeline optimizer
I built Röntgen AI, a build pipeline optimizer for Relay. It accepts uploaded or pasted CI evidence and suggests pipeline improvements.
Röntgen AI: Atlas to Blueprint architecture diagrams
I'm working on Röntgen AI: an architecture diagram generator that flows from Atlas to Blueprint. Atlas describes the current system, Blueprint the target. #architecture
The pipeline can take Atlas and help produce Blueprint. You may optionally review intermediate steps. It doesn't replace judgment — it structures the path.
IntelliTab: multi-line comment message prompt support
I added multi-line comment message prompt support to IntelliTab. The commit touches python-server/model.py, python-server/server.py, src/completion-provider.ts, and src/context-extractor.ts.
Radar: incident analysis. Relay: CI pipeline optimization. The seven products can be used together or separately; the workflow is a map, not a mandate.
https://t.co/ZaCeyiclqK
Röntgen AI: a seven-product engineering workflow map
I built Röntgen AI as a seven-product engineering workflow map: Blueprint, Pulse, Atlas, Sentinel, Forge, Radar, Relay. Each one targets a different phase of the dev lifecycle.
Under the hood, the reference architecture uses Appwrite: seventy TablesDB tables, three private storage buckets, and an orchestrator function. This is an optional target, not a constraint. Feedback welcome.
https://t.co/uJrRdNKwDF
OrkestriaAI: durable background execution
I've been building OrkestriaAI, a project for durable background execution. Runs and individual steps are persisted, so failures can be retried instead of lost.
The orchestration model includes idempotency, exponential backoff, timeouts, dead-letter handling, approvals, and audit events. It may look like a lot, but each piece targets a failure mode I've seen in practice.
The target is simple: keep low-risk analysis moving, but make human confirmation non-optional for high-impact changes. Optional automation is fine; blind automation is not.
https://t.co/uJrRdNKwDF
OrkestriaAI: deterministic approval policy
I built OrkestriaAI with a deterministic approval policy. Read-only analysis may run autonomously, but purchases, submissions, deployments, permission changes, destructive actions, and sensitive data transfers pause for human approval.
Approval requirements are computed from action, environment, destination, data classification, cost, and configured policy level. Same inputs, same decision — no guesswork.
Röntgen AI: Sentinel and Blueprint security review
Security review assistant is now included in both Sentinel and Blueprint. It's optional and can be run when you need it.
The assistant may help you catch issues before release. You can target specific files or directories, or run it across the whole project.
No extra services needed. It lives in the repo and works with your existing workflow. See the GitHub repo for details.
OrkestriaAI: five products, one control plane
I built OrkestriaAI: an AI ops control plane with five products — Vela (browser work), Loom (workflows), Tempo (DevOps), Helio (cloud cost), Aegis (security review).
All five share one control plane for identity, permissions, context, approvals, observability, and audit history. You can adopt one or several.
For me the key is: consistent oversight across different AI tasks, with an audit trail. Early project, but open to thoughts.