We scan this tool’s changelog a few times a day and keep the changes that would alter your agent’s next action: 15 since January 2026, each linked to its source.
doctlWhen authenticating doctl for repository work, run `doctl auth login` to approve browser OAuth, or `doctl auth init` to enter an API token; credentials are stored in an authentication context. Use `--no-browser`, `--timeout`, `--scopes`, `--save-scope`, or `--context <name>` to adjust browser sign-in as needed.
doctl auth loginWhen creating an agent with doctl v1.176.0, use `--template` to select the sandbox image; use `--template sandbox` to create a sandbox without an agent. The official documentation found does not provide the command’s full invocation.
When adding cloud firewall rules with doctl v1.169.0, include `action:allow` or `action:deny` in each rule string to set its action; omitted action defaults to allow.
doctl compute firewall add-rules <firewall-id> --inbound-rules "protocol:tcp,ports:22,address:<source-CIDR>,action:deny"To inspect the configured DigitalOcean account’s prepayment details, run the config command; to inspect its gate status and balances, run the status command.
doctl prepayment configWhen you need a secret’s values as key-value pairs, run `doctl secrets get --region <region> --kvs <name>`. The `--kvs` flag reveals values as `KEY=VALUE` pairs; the release note says they print in alphabetical order.
doctl secrets get --region tor1 --kvs my-secretWhen working with GradientAI scenarios or simulations in doctl v1.168.0, choose the command for the operation: use `scenario-set` to manage scenario sets and `simulation-run` to run or inspect simulations.
doctl gradient scenario-set list --statuses readyWhen inspecting or changing an Advanced MySQL cluster, use `doctl databases configuration get` to retrieve its configuration or `doctl databases configuration update` to patch specified fields.
doctl databases configuration get <CLUSTER_UUID> --engine advanced_mysql -o json --access-token <ACCESS_TOKEN>When managing an NFS share access point, use `doctl nfs access-point` commands. Create one with its share ID, name, export path, and VPC ID; use `list`, `get`, or `delete` to inspect or remove access points.
doctl nfs access-point create --share-id <share-id> --name <name> --path <absolute-export-path> --vpc-id <vpc-id>When creating or updating a DOKS cluster, set the CoreDNS Autoscaler explicitly with `--enable-coredns-autoscaler=true` or `false`; if omitted, the API applies a Kubernetes-version-specific default. [doctl v1.161.0 source](https://github.com/digitalocean/doctl/blob/v1.161.0/commands/kubernetes.go)
doctl kubernetes cluster create <cluster-name> --region <region> --version <kubernetes-version> --enable-coredns-autoscaler=trueTo inspect a database cluster’s storage autoscaling settings, run `doctl databases storage-autoscale get <cluster_uuid>`. To update them, run `doctl databases storage-autoscale update <cluster_uuid> --enabled <true|false>`; when enabling, you may also set the threshold percentage and GiB increment.
doctl databases storage-autoscale get <cluster_uuid>