AWS bedrock-agentcore documentation change
Summary
Updated documentation for the 'agentcore dev' command, adding details about the new browser-based agent inspector, the --no-browser flag, trace storage, and the --no-traces flag.
Security assessment
The changes describe a new local development workflow and CLI options. The addition of the '--no-traces' flag, which turns off saving traces to disk, is a data handling option that could have privacy implications, but the documentation does not present it as a response to a security issue or vulnerability. It is a new feature for controlling local data persistence.
Diff
diff --git a/bedrock-agentcore/latest/devguide/agentcore-get-started-cli.md b/bedrock-agentcore/latest/devguide/agentcore-get-started-cli.md index 0a995fcc9..8b5d04fc2 100644 --- a//bedrock-agentcore/latest/devguide/agentcore-get-started-cli.md +++ b//bedrock-agentcore/latest/devguide/agentcore-get-started-cli.md @@ -182 +182 @@ Interactive - 1. Run `agentcore` to open the TUI home screen, then select **dev** to start the local development server with an inline chat prompt: + 1. Run `agentcore` to open the TUI home screen, then select **dev** to start the local development server: @@ -186 +186 @@ Interactive - + @@ -191 +191 @@ Interactive -The dev server automatically creates a Python virtual environment, installs dependencies, and starts a local server with hot-reload on port 8080. Any changes you make to your agent code are picked up automatically. +The `agentcore dev` command automatically creates a Python virtual environment, installs dependencies, and starts a local server with hot-reload on port 8080. It then opens the agent inspector in your web browser, where you can chat with your agent, inspect your agent interactions, and view project resources. Any changes you make to your agent code are picked up automatically. @@ -193 +193,13 @@ The dev server automatically creates a Python virtual environment, installs depe -To view server logs in real time, use the `--logs` flag: +To use the terminal-based TUI instead of the browser-based agent inspector, use the `--no-browser` flag: + + + agentcore dev --no-browser + +Traces from your local agent sessions are stored in `agentcore/.cli/traces` in your project directory. + +To turn off saving traces to disk, use the `--no-traces` flag: + + + agentcore dev --no-traces + +To view server logs in real time (non-interactive mode), use the `--logs` flag: @@ -219 +231 @@ Interactive - 1. Run `agentcore dev` without a prompt to open the interactive chat TUI, which streams responses by default and maintains your session automatically: + 1. Run `agentcore dev` without a prompt to open the AgentCore agent inspector in your browser. To use the interactive chat TUI instead, use `--no-browser`: @@ -221 +233 @@ Interactive - agentcore dev + agentcore dev --no-browser @@ -230 +242 @@ Interactive -Local development does not require deployment. However, Amazon Bedrock AgentCore Memory is not available during local development because memory stores require deployed AWS infrastructure. To use memory, deploy your project first with `agentcore deploy` . For more information, see [Add memory to your Amazon Bedrock AgentCore agent](./memory.html). +Local development does not require deployment. The `agentcore dev` command opens the AgentCore agent inspector in your web browser for an interactive development experience. Use `--no-browser` to use the terminal-based TUI instead. To use Amazon Bedrock AgentCore Memory during local development, you must first deploy your memory store using `agentcore deploy`. For more information, see [Add memory to your Amazon Bedrock AgentCore agent](./memory.html).