We built the data grid we always wished existed
Meet Elyra DataGrid — one grid, three clients, ten million rows, and a first paint that doesn't flinch.
Articles, notes and updates on the agent, the tools, and the craft of building software with AI.
Meet Elyra DataGrid — one grid, three clients, ten million rows, and a first paint that doesn't flinch.
Coding agents are blind to the layer where half your afternoons go: the php-fpm OOM, the .env pointing at nothing, the APP_URL that lies. 0.9.21 ships a Grove integration that reads the environment's own files — plus Freddy the Notetaker, a fourteen-chapter course that builds a real product with Elyra from an empty directory.
Auto-diagnostics and blast radius on every edit, swarm pipelines isolated in git worktrees, and failover that learns which models actually work on your machine. Three instincts, one idea: the agent should check its own work, and the system should learn from the outcome.
Grove 1.2.1 makes sandboxed writes legible: every agent-run migration or SQL statement now comes back with its blast radius — the SQL it ran, the mail it sent, and the metrics — so keeping or rolling back isn't a leap of faith.
Grove 1.1 turns grove mcp from a read-only window into a workshop: sandboxed writes with automatic rollback, a per-request causal chain linking requests to SQL and mail, and one-click 'explain this error' bundles. No app instrumentation required.
Running four coding agents at once is free. Knowing what they're all doing is not. Elyra Conductor v0.8.8 adds a herd strip next to the tab bar — blocked, working, done, sorted by urgency, one click away.
Elyra already shipped LSP integrations — the agent just wasn't reaching for them proactively. 0.9.18 makes symbol lookup automatic after every edit, adds Rust to the LSP lineup with @elyracode/lsp-rust, ships a stack profile for Elyra Framework, and fixes a copy-paste bug quietly breaking /tall:info, /vilt:info and /silt:info.
A field journal through Askr 0.9.4 → 0.9.6: agentless SQL logging, a leader-elected metrics rollup, per-request OpenTelemetry traces, HTTP/3 over QUIC, a -full build, and askr-laravel on Packagist.
A field journal through Askr 0.9.0 → 0.9.3: stale-while-revalidate, RSS-based worker recycling, shadow traffic, native queue autoscaling, a durable L2 tier, and the broadcasting driver that finally deletes Redis from Laravel.
Two features ship in v0.9.16, and neither is possible for a vendor-locked tool: cross-provider failover, so your agent doesn't die when your provider does, and /review --cross, a second opinion from a genuinely different vendor. Provider-agnosticism as a feature, not a footnote.