Practice Observations
Observations of specific engineering use cases, encountered problems, and reported practices extracted from the evidence corpus.
18Evidence
18Assessed
0Pending
39Observations
100%Coverage
Assessment coverage measures evidence records explicitly assessed for practice observations. Assessed evidence may legitimately contain zero observations.
11 practice observations · execution
| Company | Specific use case being solved | Problem encountered | Reported practice | Selection condition |
|---|---|---|---|---|
| Cursor | Integrate changes produced simultaneously by many agents. | Conventional merge behavior accumulated more than 70,000 conflicts in an earlier run. | Cursor uses neutral third-party agents for merge conflicts and a purpose-built version-control system at higher commit throughput. | coordinationexecution |
| Spotify | Run many background coding-agent sessions with controlled execution and verification. | Autonomous sessions need an execution environment with trusted tools and a reliable quality gate. | Spotify runs Honk sessions in Kubernetes with trusted tools and CI verification. | executionverification |
| Google Cloud | Run agent jobs that continue for hours or days and survive infrastructure or human interruptions. | A long-running agent cannot depend on one process or session remaining alive for the duration of the work. | Google Agent Executor uses durable event logs and snapshots to support execution, resumption, and distributed deployment. | executionobservability |
| OpenAI | Run more concurrent Codex coding tasks than an engineer can comfortably supervise as separate sessions. | Engineers lost track of work and debugged stalled agents beyond roughly three to five simultaneous sessions. | Symphony moves task assignment and workspace lifecycle into an always-on orchestrator where open tasks receive agents in isolated workspaces and humans review outcomes. | coordinationexecutionobservabilityverification |
| Cursor | Execute multiple parts of an engineering task concurrently. | Parallel agent work needs decomposition, isolation, and dependency-aware composition to avoid interfering changes. | Cursor Multitask decomposes work into asynchronous subagents, uses worktrees to isolate concurrent changes, and parallel plans to preserve task dependencies. | coordinationexecution |
| Spotify | Apply a dataset migration across thousands of downstream consumers. | Repository-scale changes need coordinated scheduling and pull-request execution across a large fleet. | Spotify combines Honk, Backstage, Codesearch, and Fleet Management to target and orchestrate the migration. | coordinationexecution |
| Spotify | Run background coding agents with predictable behavior. | Greater execution flexibility increases unpredictable behavior. | Spotify constrains permissions, available binaries, and execution through sandboxing and surrounding infrastructure. | execution |
| Bun | Use a coding agent to fix bugs in the Bun repository. | An agent-authored fix needs evidence that it resolves the bug rather than merely changing code. | Bun's Claude Code bot opens pull requests with tests that fail against the earlier system-installed Bun and pass against the fixed debug build, then responds to review comments. | executionverification |
| Spotify | Make autonomous background coding runs more predictable. | Additional dynamically fetched context and tools increase dimensions of unpredictability. | Spotify limits tools and hooks, constrains Git and Bash operations, and exposes standardized verification. | contextexecutionverification |
| Spotify | Execute software migrations across a large repository fleet with a background coding agent. | Deterministic transformation declarations do not cover every migration, while repository targeting, pull-request lifecycle, review, and production merging still need coordinated infrastructure. | Spotify retained Fleet Management for repository targeting and pull-request lifecycle while replacing transformation declarations with natural-language instructions executed by a coding agent. | coordinationexecution |
| Spotify | Operate background coding agents predictably while agent and model components evolve. | Agent execution needs formatting, linting, diff evaluation, logs, traces, and the ability to change agent or model components without rebuilding the surrounding workflow. | Spotify built a pluggable CLI harness with MCP-based formatting and linting, LLM-as-judge diff evaluation, GCP logs, MLflow traces, and swappable agents and models. | executionobservabilityverification |