Background jobs for AI workloads: when a run should not hold a request open
When an AI run belongs in a request and when it belongs in a job, and how 10xGraph runs jobs as a thin TaskIQ layer with a worker, a scheduler and the same auth.
When an AI run belongs in a request and when it belongs in a job, and how 10xGraph runs jobs as a thin TaskIQ layer with a worker, a scheduler and the same auth.
The limits a 10xGraph run has by default: parallel tool cap, run, node and tool timeouts, per-user run cap, one run per thread, request size limits and paging caps.
Gate pull requests on what an AI agent did: which tools it called and with what arguments. Uses 10xGraph eval sets, trajectory scoring with no judge model, and pytest.
Cheaper models, a stateless MCP spec, MCP CVEs, approvals everywhere and EU transparency rules: what changed in AI in 2026 and the 10xGraph code to handle each one.
Why a crash mid-node re-runs tools that already fired, why the usual fixes fall short, and how 10xGraph's tool ledger and versioned writes close the gap.