pulumi neo | CLI commands
Start a Pulumi Neo agent task with local tool execution
Synopsis
Creates a Pulumi Neo agent task in CLI tool execution mode and runs the local tool loop. Filesystem and shell tool calls from the agent run on this machine, in the working directory you select, instead of in the cloud agent container. If no prompt is provided, the TUI starts and waits for your first message.
pulumi neo [prompt] [flags]
Options
--cwd string Working directory for local tool execution (defaults to the current directory)
-h, --help help for neo
--org string The organization that owns the Neo task (defaults to the user's default org)
-s, --stack string The name of the stack to attach to the Neo task
Options inherited from parent commands
--color string Colorize output. Choices are: always, never, raw, auto (default "auto")
--disable-integrity-checking Disable integrity checking of checkpoint files
-e, --emoji Enable emojis in the output
-Q, --fully-qualify-stack-names Show fully-qualified stack names
--logflow Flow log settings to child processes (like plugins)
--logtostderr Log to stderr instead of to files
--memprofilerate int Enable more precise (and expensive) memory allocation profiles by setting runtime.MemProfileRate
--non-interactive Disable interactive mode for all commands
--otel-traces string Export OpenTelemetry traces to the specified endpoint. Use file:// for local JSON files, grpc:// for remote collectors
--profiling string Emit CPU and memory profiles and an execution trace to '[filename].[pid].{cpu,mem,trace}', respectively
--tracing file: Emit tracing to the specified endpoint. Use the file: scheme to write tracing data to a local file
-v, --verbose int Enable verbose logging (e.g., v=3); anything >3 is very verbose
SEE ALSO
- pulumi - Pulumi command line
Auto generated by spf13/cobra on 23-Apr-2026
Thank you for your feedback!
If you have a question about how to use Pulumi, reach out in Community Slack.
Open an issue on GitHub to report a problem or suggest an improvement.