AWS AgentCore CLI 1.0 brings agent workflows to the terminal

AWS has made Amazon Bedrock AgentCore CLI version 1.0 generally available, giving developers a terminal-based way to create, deploy and operate AI agents and their supporting resources. The practical shift is that users can work with existing AgentCore resources directly, rather than first having to add them to a project.

AWS AI Watch analysis

What happened

The CLI supports project workflows as well as direct work with AgentCore harnesses, runtimes, memory, identity, gateways and payments. AWS says version 1.0 brings faster startup, a consistent command structure and support for more AgentCore resources. Existing projects can be migrated with the agentcore migrate command.

AWS’s release announcement also describes resource lookup by ID or ARN, an interactive shell, harness export, searchable menus and guided workflows. Global flags provide region selection, JSON output, debugging and version information across commands.

Our top picks

• Work with resources directly
  Developers can use harnesses, runtimes, memory, identity, gateways and payments without first adding them to a project.
• Find existing resources by ID or ARN
  The CLI can invoke resources that are already in place, rather than making every task begin with project setup.
• Use guided terminal workflows
  Searchable menus, resource pickers and guided workflows give developers more than a command list to memorise.
• Open an interactive shell and export a harness
  These options add practical ways to explore and move AgentCore work through the CLI.
• Keep common flags consistent
  Region selection, JSON output, debugging and version information are available through global flags across commands.
• Migrate existing projects
  The agentcore migrate command gives current users a named route to move projects to AgentCore version 1.

Why it matters

A CLI is only useful if it makes routine work easier, and this release targets several points where agent development can become fiddly: locating resources, moving between project and direct workflows, and handling common command options consistently. The migration command also gives existing users a concrete starting point for moving to version 1.

Our read

This is a substantial developer-tool release, not just a fresh version number. The useful test will be whether the broader resource support and guided workflows make real projects simpler to manage, rather than merely giving the terminal a larger vocabulary. Developers already using AgentCore have clear reasons to inspect the new CLI and its migration path.

What to watch

• How well the migration command handles existing projects.
• Which additional AgentCore resources developers can use through the CLI in practice.
• Whether the faster startup and guided workflows make everyday development noticeably smoother.

Discussion spark: For agent development, would you rather have a single project-centred workflow or a CLI that lets you work directly with existing resources?

not affiliated with or endorsed by Amazon Web Services (AWS)