Skip to content
ArchFoundry Docs Open the canvas

Approve what a coding agent asks for

Updated October 19, 2026Plans: Free, Pro, Enterprise

Overview

When Claude Code, Cursor or another connected agent asks ArchFoundry for infrastructure, nothing is created. ArchFoundry drafts and prices a design for the agent's account, and the request waits for a person on your team. You open it, read the plan and the cost, and either deploy it or decline it. The agent sees the result either way.

Prerequisites

  • A coding agent connected by signing in or with an agent token. See Connect Claude.
  • To deploy or decline: an owner or admin role, or any member when the account's environment is named dev, development, sandbox or test. Anyone in the organization may open and review a request.

Steps

  1. In the workspace sidebar, click Deployments. Requests from agents are listed at the top under Waiting for approval, with the agent, the account, the change in monthly cost and what the agent asked for. You can also open the link the agent gives you.
  2. Click Open and review. The canvas opens with the agent's design, and a strip at the top quotes what it asked for and what it costs at list prices.
  3. Read the design on the canvas. Change it if you need to.
  4. Click Review and deploy. The deploy flow opens, with its plan, its cost and its typed confirmation. See Deploy a diagram to your AWS account.
  5. To turn it down instead, click Decline… in Deployments, optionally write why under Why not? The agent reads this (optional), and click Decline. On the canvas strip, Decline does the same without a reason.

Example

An agent asked for a database and an API container. The strip on the canvas reads:

text
claude-code asked: "A Postgres database and a container for my API, kept small."
+$54.51/mo at list prices

Expected result: after you deploy, the strip says Deployed. The agent can read the result. The agent's next call to get_outputs returns the endpoints, ports and the ARN of the secret that holds the database password.

Verify it worked

  • The request leaves Waiting for approval.
  • A deployed request appears in Deployments like any other stack.
  • A declined one says Declined. The agent is told nothing was created, and why if you said.

Troubleshooting

An owner or admin decides this one. You may review the request, but not decide it. The account is not a development environment, so an owner or admin approves it.

An owner or admin approves requests for this account. On the canvas you can still click Review the plan to read what would be created.

The deploy stopped partway. Deploy again to finish it. The agent sees the request as failed until then.

Only an owner or admin can reopen it. A declined request shows Declined agent request and why. Ask an owner or admin if it should go ahead after all.

Keeping a record. Owners and admins can download every request, who decided it and what it became, with Export the audit (CSV) under Coding agents.

Next steps