2026-11-22Gunner Technology

Make a New Service Update the Setup

Prevent coding-agent setup drift by making local and cloud environments consume the same service definitions, then testing setup whenever those definitions change. A service addition should update the setup automatically or fail a required check. Otherwise every new worker inherits another missing step to discover.

What does pattern engineering have to do with setup?

Pattern engineering means improving the conventions and tools that guide repeated work. In Shaping the Loops, Closing the Loops, Revyl distinguishes that work from verification engineering, which checks whether a change satisfies its requirements. The distinction is useful: checking a finished change and improving the conditions that produce the next change are separate engineering jobs.
The article's concrete example is a shared setup workflow for engineers and cloud agents. It argues that setup should follow the service definitions engineers already maintain, so adding a service does not leave a separate setup system waiting for someone to update it. Revyl describes extending an onboarding tool to cloud agents; that example shows how the approach can extend to a new environment.
This post focuses on that maintenance problem. We already cover stable commands for coding agents. Here the question is what keeps the machinery behind those commands current after the application changes. Gunner Technology recommends tying that obligation to the service change itself.

What belongs in the shared service definition?

Keep the information needed to start and check each service in a versioned record: its dependencies, supported runtime, startup command, readiness check and required access. A readiness check establishes that the service can do useful work, rather than merely confirming that a process exists. Give the record an owner who can settle changes to those requirements.
Use that record to assemble each supported environment. A laptop and a cloud worker may need different launchers, networking or installation steps. They should agree about which services a task needs and how to recognize a working installation. Platform differences can stay explicit without becoming separately maintained lists of the application.
For example, suppose a feature adds a background worker that consumes a queue. The service record should carry that dependency into both setup routes. If the local script starts the worker while the cloud image still omits it, the service change is incomplete. A reminder in the onboarding guide leaves that mistake available to every future run.

Does shared setup mean shared credentials?

No. Share the procedure while keeping credentials scoped to the worker and the job. The service record can name the access it requires without storing secret values. The setup system should obtain permitted credentials from your secret store and stop with a clear missing-access report when it cannot obtain them.
An engineer's laptop and a cloud agent do not need identical permissions to start equivalent test environments. Use development accounts, isolated data and approved substitutes where the task allows them. Keep production credentials outside the setup path unless a separately authorized operation requires them. A successful installation should never depend on borrowing an engineer's broader access.
Keep credentials out of setup evidence too. Record whether the required access was available, not the value that supplied it. Your team should own the service definitions, launcher and secret-store configuration in its own environment, so repairing setup does not require access to a provider's private account.

How do you prove a service change updated setup?

Run the declared setup from a fresh environment on each supported platform, then exercise the changed service through a small real workflow. A warm development machine can hide a dependency installed months ago. Preserve the configuration revision, tool versions, readiness results and check outcomes so another worker can tell what actually ran.
For the background-worker example, submit a development job, confirm that the worker consumes it and inspect the expected result. Starting the queue alone proves too little. As our guide to giving agents a real system to test explains, the environment has to represent the behavior the check claims to cover.
Test an unavailable dependency as well. The setup should identify what is missing and withhold readiness, rather than quietly dropping the service from the test run. Keep the required acceptance check outside the builder's ability to waive it. An agent that repairs setup should not be able to redefine an incomplete environment as ready.

Who owns the workaround after setup fails?

The owner of the shared setup path should turn a valid workaround into a reviewed repair, or record why it must remain a local exception. Have the agent preserve the failing command, the missing condition and the smallest proposed fix. Repeating the repair in chat gives the next worker instructions to rediscover instead of working machinery.
Retest from a fresh environment after the repair. If the fix installs a new tool or changes a version, declare that input so it survives the current session. Our discussion of the agent toolbox as a build input covers that dependency. Keep a way to restore the previous setup when the new definition breaks supported work.
Start with a service that repeatedly needs setup help. Make its declared dependencies drive local and cloud preparation, and require a clean run when they change. Let agents do the installation, checking and repair work. People decide the supported behavior and judge whether the evidence meets it. The next worker should benefit without having to ask who remembers the missing step.
In response to Shaping the Loops, Closing the Loops by Revyl.

Quick answers

Do we need to build our own setup CLI?

No. Use the repository tasks or environment tooling you already have if they can consume the shared definitions and report failures clearly.

What if a cloud agent cannot run every service?

Declare the supported subset and which checks it can prove. Route work requiring the missing services to a suitable environment before accepting it.

Should cached environments still be allowed?

Yes, if their configuration is known and current. Keep a fresh-environment check so a cache cannot conceal an undeclared dependency.