@ArizePhoenix: Something we’ve been playing with and liking a lot: Give every coding agent its own observability stack. Because Arize …

Something we’ve been playing with and liking a lot: Give every coding agent its own observability stack. Because Arize Phoenix can run fully local-first and air-gapped on your computer, each coding agent can get its own Phoenix instance: its own port, its own SQLite DB, its own traces, its own evals. That means every agent working in its own worktree can observe what it did, inspect its traces, run evals against its changes, and use that feedback loop to self-verify before handing work back. A private loop for every agent: code → trace → evaluate → improve → verify This makes it possible to scale many coding agents locally without cross-talk, shared state, or interference between neighboring work. The bigger idea is that agents should not just generate work. They should be able to measure and validate their work continuously. Local-first observability makes that practical.