Pulumi
Neo left the Pulumi Cloud console this month, landing in the terminal, GitHub, and Slack alongside a new stateless resource command and a rebuilt CLI.
pulumi do brings direct cloud ops without a project. The new command lets humans and coding agents create, read, update, delete, and list any cloud resource across every Pulumi-supported provider — no project, no state file, no boilerplate.1 A single command covers AWS, Azure, GCP, Kubernetes, and thousands of other provider resources using the same type-token pattern.
Neo reached the terminal, GitHub, and Slack. pulumi neo — now out of experimental and visible by default — runs Neo locally against the CLIs and credentials already configured on the machine.2 Mentioning @pulumi-neo in a pull request or @Neo in a Slack channel starts a task in-thread, with the same RBAC and audit trail as a console session.3 Neo Automations added scheduled runs: pick a cadence, write a prompt, and Neo opens pull requests for each run without waiting to be asked.4
Neo's integration catalog expanded. MCP connections to Atlassian, Datadog, Honeycomb, Linear, PagerDuty, and Supabase are now available alongside CLI integrations for aws, gcloud, az, and kubectl.5 Both are configured once at the org level and available to every task.
The CLI was reorganized for agents and humans alike. Commands now follow a consistent <noun> <verb> pattern with a shared vocabulary — list, get, set, new, edit, remove.6 pulumi up, pulumi preview, pulumi destroy, and pulumi refresh gained --output json. The new pulumi api command exposes the full Pulumi Cloud REST API from the terminal without separate auth setup.7 Coding agents can now create claimable temporary accounts when running unauthenticated.8