Guy Stephens Productions
Project description
Agent Bridge gives a user one local conversational workflow for image and page-design work across existing agent capabilities. The user describes a task, reviews its exact prompt, capability, project and execution mode, then confirms that request. Progress and result retrieval stay tied to the same request and its original Bridge job.
This is a local Alexa+ simulation. It does not connect to an Alexa device, Alexa+ service or Amazon developer tool, and it is not an official Amazon integration or endorsement.
Work added during the hackathon
The existing Agent Bridge already provided a local Model Context Protocol backend, image generation, an attended Claude Design handoff and import workflow, job inspection and cancellation, and earlier image and Design artifacts.
The October 12 contribution adds a conversational simulator, browser interface and fixed-scope adapter. It adds exact-request confirmation, durable request identity, duplicate-confirmation protection, job ownership, a journal written before dispatch, reconciliation after uncertain responses, truthful status and verified artifact retrieval. Unsupported capabilities are reported explicitly.
The demo replays earlier PNG and attended Design HTML outputs through the new flow. Retrieval creates local conversation records, but no new Bridge job or provider output. A separate Design action prepares a local job and brief for manual work only. The timeout scene is a labeled synthetic test fixture. No new provider-generated output was produced for the October 12 demo revision.
Architecture and safeguards
A local Node.js server serves a loopback-only browser interface and starts the constrained Agent Bridge adapter over stdio MCP. The TypeScript MCP SDK supplies the transport and Zod validates bounded tool arguments. Browser input cannot choose a different executable, project or state directory.
Confirmation is time-limited and bound to the reviewed payload. The ledger records the request before dispatch. After an uncertain response, the simulator reconciles against the same context instead of automatically resubmitting. Status and retrieval remain tied to the original request and job.
Replay mode retrieves configured existing results without provider calls. The reviewer package also applies a backend replay-only mutation guard that blocks image dispatch, Design preparation, cancellation and imports. The separate attended-brief demonstration does not run in that restricted reviewer replay.
Optional native image dispatch uses the existing Codex image capability and may consume account-plan usage; it is disabled in the prepared example. Native Claude Design remains attended: an approved request prepares a local brief, the operator works in the actual Design interface using its approvals, then explicitly imports a real export. The simulator does not automate Design login, approvals, generation or export.
Evidence and limits
The recorded reviewer preparation passed 69 focused simulator tests on October 12 in both the working source and a clean reviewer checkout. The clean setup used Windows with Node 24.14.1, a folder with spaces, an empty provider profile and a sanitized environment. Node 20 or later is documented; other operating systems and versions have not received acceptance testing.
Recorded checks exercised the actual local MCP backend and HTTP downloads, retrieved the original PNG and HTML with matching hashes, reused each original job after duplicate confirmations, and rejected foreign Origin and request access. Browser acceptance was recorded in the Codex built-in browser. No provider work was launched during the final reviewer verification.
Provenance is operator-attested, not provider-authenticated. A matching stored hash verifies bytes, not authorship. PNG and HTML artifacts are limited to 8 MiB. HTML is downloaded as an untrusted attachment with restrictive sandbox handling and is not executed in the simulator page. Cancellation is cooperative and does not prove that upstream work stopped.
Reviewer setup
Use the repository README and pinned lockfile. No provider account is required for replay. Run these commands in order from the project directory:
npm ci --omit=dev --ignore-scripts
npm run demo:check
npm run demo
The recorded clean setup installed 93 runtime packages with lifecycle scripts disabled, passed the startup check and all 69 focused tests, and retrieved both original artifacts through the real MCP and HTTP flow.
Local friction report
Automated Edge navigation to the local simulator returned ERR_BLOCKED_BY_CLIENT. Manual Edge access worked, and browser acceptance was completed in the Codex built-in browser. The cause was not established and no browser security or trust settings were changed. This was low-severity local browser friction, not an Amazon onboarding issue. A useful improvement would be diagnostics that distinguish an automation or client block from an unavailable local server and suggest a supported manual check.
Log in or sign up for Devpost to join the conversation.