SOFTWARE / SYSTEMS / AIEngineering news. Technical depth.
NEWS / Developer tools · 2 MIN READ

AWS releases AgentCore CLI 1.0 with direct resource workflows

Generally available AgentCore CLI 1.0 adds direct resource operations, consistent global flags and a migration command for existing projects.

Announcement: · From AWS

AWS announced general availability of Amazon Bedrock AgentCore CLI 1.0 on October 28, 2026. Available through npm as @aws/agentcore version 1.0.0, the release supports both project-based workflows and direct operations on AgentCore resources, according to the AWS announcement.

Work with resources without adding them to a project

The notable workflow change is that developers can work directly with harnesses, runtimes, memory, identity, gateways and payments without first adding those resources to a project. The project-based workflow remains available.

Developers can invoke existing resources by ID or ARN, open an interactive shell and export a harness. AWS also lists searchable menus, resource pickers and guided workflows among the CLI’s interactive features.

For engineers maintaining existing deployments, the distinction matters: a targeted resource operation need not begin with adding that resource to a project. This could reduce preparation for maintenance tasks while leaving project workflows available for development. It is a workflow-flexibility benefit, not evidence of faster agent execution.

Consistent flags and an explicit migration path

AWS says consistent global flags provide region selection, JSON output, debugging and version information across commands. The announcement also identifies agentcore migrate as the command for migrating existing projects to AgentCore version 1. Both capabilities are described in the release announcement.

For automation, consistent options and JSON output could reduce command-specific handling. Teams should still validate the output and error behavior their scripts depend on rather than assume compatibility. A prudent upgrade sequence is to migrate a representative project, then check deployment and operational scripts before wider adoption.

AWS also reports faster CLI startup, but the announcement provides no timing measurements. Teams evaluating the upgrade should distinguish that vendor performance assertion from the documented changes to resource workflows and command structure.

SOURCES & CONTEXT

See the original announcement for availability and release details.