Enter your email and we'll send you a one-time code. Identities
represent organizations (donor, recipient, coordinator) — the agent
filters the tools each org can see.
How this works
This app runs in one of three modes depending on what's set in
config.js — the badge in the header shows which one is
active:
Connected to AWS — full agent path: sign in with Amazon Cognito (email one-time code → JWT), then the app calls the AgentCore Runtime, which runs the Strands agent on Amazon Nova and answers from live tools.
Live backend data — the app calls the deployed backend API directly (BACKEND_API_URL) and formats the real data itself. No Cognito, no agent — handy for demos.
Demo mode — no AWS configured; replies are mocked locally so you can explore the UI (sign in with any email + code 123456).
In Connected to AWS mode, a message follows this path:
You ─▶ Cognito ─(JWT)─▶ AgentCore Runtime ─▶ Strands agent + Amazon Nova
│
AgentCore Gateway (MCP)
(OAuth2 token from AgentCore Identity)
│
openApiSchema target "BackendTools"
│
API Gateway ─▶ Lambda ─▶ community data
(surplus · catalog · needs · pantry ·
volunteers · vehicles · guidelines)
(optional) Amazon Verified Permissions filters tools per request
The agent is grounded: it only states what a tool returned during
your conversation. Config values live in config.js
(Cognito, AgentCore runtime ARN, and/or BACKEND_API_URL).