A plan before a deploy

Why reviewing a change belongs between describing infrastructure and applying it.

Describing infrastructure and changing infrastructure are different operations. We want the interface to make that distinction obvious.

Start with the project

An agent should inspect the application before proposing infrastructure. The framework, runtime, and data requirements are already expressed in the codebase.

From there, the infrastructure file becomes a small description of what the app needs—not a place to store credentials or reproduce the whole application.

For example, a small Node.js app could describe its build like this:

nubes.hcl

version = 1

app "api" {
  source "nodejs" {
    path            = "./api"
    package_manager = "pnpm"
    build           = "pnpm build"
  }
}

Make changes reviewable

A useful plan answers a few concrete questions:

What will be created or changed?
Which parts of the application depend on it?
Does it touch persistent data or secrets?

Only then should the conversation move to applying the change. Keeping that boundary explicit makes an agent-driven workflow easier to trust.

nubes plan .ai/nubes.hcl

The path .ai/nubes.hcl stays close to the codebase, and nubes plan makes the review step explicit.