Inspiration
A household responsibility often depends on somebody else's work. Bringing a school form only helps after someone has printed it. Changing the owner can create another conflict or hide a prerequisite. HomeRelay keeps those relationships visible and lets a person review a proposed change before it reaches the family board.
What it does
The working demo uses fictional Alex, Maya and Sam household data. Ask what needs attention tomorrow, prepare a handoff, clarify a missing date or time, correct the owner or schedule, then confirm or cancel. A structured form also creates handoffs with an optional prerequisite. Dependent tasks stay blocked until their prerequisites are complete. Reassignment previews explain eligibility and workload warnings. Confirmed changes survive a server restart.
How we built it
The HTML/CSS/JavaScript interface calls a Node.js/Express backend. Its assistant uses a real MCP SDK client and the self-hosted /mcp Streamable HTTP endpoint. Seven tools cover household reads, previews, confirmation, cancellation and completion. Runtime initialization and tool calls negotiate MCP protocol 2025-11-25. Zod and domain checks validate dates, dependencies and proposal revisions. The store persists a change before exposing it in memory.
The default conversation is a bounded deterministic router, with a clearly labelled local Alexa+ simulator. It is not a native Alexa connection or a general language model. An optional Bedrock Converse adapter is implemented and stub-tested; no live AWS model or AWS mini-challenge is claimed. Explicit user controls handle final confirmation, cancellation and completion.
Challenges and learning
A correction must replace the old preview without accidentally approving it. Tests distinguish questions about confirmation from an explicit confirmation and retain missing details across clarification turns. Storage tests simulate failed saves and verify that memory and the saved board remain unchanged until a retry succeeds. This showed why a suggestion, a preview and a saved household change need separate states.
Accomplishments
All 40 tests pass in public CI. An independent MCP probe discovers all seven tools, exercises review, confirmation, dependency blocking and cancellation, and verifies persistence after restart. The public silent 2:44 video shows actual application actions with English captions and fictional data.
What's next
Test the workflow with another person, add household access controls before a network deployment, and validate the optional provider with an authorized account. Notification delivery, calendar integration and native Alexa rendering are not implemented. No user interviews or measured household outcomes are claimed.
Source and verification
Public MIT repository and judge setup: https://github.com/Vcode2407/amazon-homerelay Current CI: https://github.com/Vcode2407/amazon-homerelay/actions/runs/38157512856 Run npm ci, npm test, npm run verify:mcp and npm run demo as described in the repository. The selected main Alexa+ MCP path runs locally without hardware or AWS access. No mini-challenge is claimed. Codex assisted implementation, testing, documentation and recording automation; the footage records the working application, with no narration.
Log in or sign up for Devpost to join the conversation.