chatting-with-aws-devops-agent

Chat with the AWS DevOps Agent

AgentSpace routing (SigV4 only): If list_agent_spaces is available in your tool list and the multi-space orchestration skill has NOT been invoked yet this session, invoke it first to determine which agent_space_id to use. Then pass agent_space_id on all tool calls below. For bearer token auth this is unnecessary — the token is already scoped to one space.

Chat is the default. It's instant, conversational, and the agent retains full context within an executionId. Only escalate to investigating-incidents-with-aws-devops-agent when the user describes an incident or the agent itself suggests deeper analysis is warranted.

How to send messages

Primary — use the chat tool:

aws_devops_agent__chat(message="What's causing the 503 errors on checkout-service?")
→ {"executionId": "uuid", "answer": "Based on my analysis..."}

One call, full answer. No session setup needed — the tool handles CreateChat + SendMessage + response parsing internally.

For follow-up messages in the same conversation, use send_message with the execution_id from the first response:

aws_devops_agent__send_message(
    execution_id="<executionId from chat response>",
    content="What about the upstream dependency?"
)
→ "The upstream service shows..."

The agent retains full context within an executionId. Reuse it for follow-ups — don't call chat again for the same conversation.

For browsing previous conversations:

aws_devops_agent__list_chats()
→ {"chats": [...]}

Injecting local context

Pack local workspace knowledge into the message parameter. This is the killer feature — the DevOps Agent knows your AWS cloud; you know the user's local workspace.

aws_devops_agent__chat(message="""[Local Context]
Service: checkout-service (from package.json)
Last deploy: commit abc1234 — 2h ago
CDK Stack: lib/checkout-stack.ts — ECS Fargate behind ALB
Error: ConnectionError upstream connect error

[Question]
What's causing the 503 errors on the checkout-service?""")