feat(mcp): teach burrow_deploy the build-and-push flow#155
Merged
Conversation
The burrow_deploy tool description told an agent only that the image must already be pushed to a registry, never that it should build and push the image itself or infer the app from the working directory. A user saying "deploy my app" would stall because the agent did not know to build first. Enrich the description with the full client-side flow: infer the app name from the working directory unless named, build the image with the agent's own container tooling (for example docker build) and push it to a cluster-pullable registry, then deploy by that reference. It also states explicitly not to run the burrow CLI to build or deploy, since the agent operates through these tools rather than the CLI. The image input field now notes it is the reference of an image the agent has built and pushed. All existing guidance (never code over MCP, config-before-deploy, secrets handling, env/context targeting, returns) is preserved. Description-only; deploy behavior is unchanged. Signed-off-by: Nicholas Phillips <nsphilli@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Enrich the
burrow_deployMCP tool description so an agent knows the full client-side deploy flow and can act on "deploy my app" without hand-holding.Before, the description said only that the image "must already be pushed to a registry the cluster can pull from" but never told the agent to build and push the image, or to infer the app from the working directory. A user saying "deploy my app" would stall because the agent did not know to build first.
Change
The
burrow_deploydescription now teaches the full flow:docker build) and push it to a registry the cluster can pull from, then deploy by that reference.burrowCLI to build or deploy — the agent operates through these tools, not the CLI (aligning with the CLI-hardening direction).The
imageinput field now notes it is the reference of an image the agent has built and pushed to a cluster-pullable registry. All existing guidance is preserved: never code over MCP, config-before-deploy viaburrow_config_set, secrets handling, env/context targeting, and the returns.This is description/guidance only, consistent with the client-side build model (ADR-0008, ADR-0007). No deploy behavior or code paths change.
Checks
task checkgreen,go test ./...green, gofmt clean.