Using 'claude -p' for running Mr.Jassy - AWS butler agent
A developer is setting up Mr.Jassy, a read-only AWS butler bot, as a Slack app that runs 'claude -p' inside a Lambda triggered by Slack events, and asks whether this approach is optimal or if a better alternative exists. They also maintain thread context by resuming previous sessions.
Background
- **Mr.Jassy** (aka Mr. Jassy): A play on Andy Jassy, CEO of Amazon. It's a community/open-source tool (often a Slack bot) that lets teams query their AWS infrastructure in natural language — e.g., asking "how many EC2 instances are running in us-east-1?" without logging into the AWS console.
- **claude -p**: A command-line flag for Claude AI (Anthropic's model) that lets you pass a prompt directly in the terminal — e.g., `claude -p "list my S3 buckets"`. The user is running this command from inside an AWS Lambda function triggered by Slack events.
- **Why this matters**: The question is about architecture. Running a CLI tool (`claude -p`) inside a Lambda as a Slack bot handler works but has limitations — cold starts, short Lambda timeouts, no persistent streaming. The user is asking if this pattern is viable or if there's a better (serverless, event-driven) approach.
- **Thread context**: They mention "resuming a previous session," meaning they're trying to maintain conversational memory across Slack messages, which is non-trivial with stateless Lambda invocations.