-
-
Real browser MCP integration with notebook-scoped access. No live Alexa+ or Echo connection claimed.
-
Actual local Reopen workflow with fictional records. Owner approval stays separate from assistant access.
When a plan's assumptions change, remember why you chose it and decide what should change next. Reopen keeps the original reasoning beside later evidence and records the checklist change you actually approved.
Inspiration
A checklist says what to do, but often loses the assumption that made the plan sensible. An online-only product demonstration works if the venue has reliable internet. If a later report says the room has no Wi-Fi, the owner needs to revisit that assumption without losing the original reasoning.
Reopen is a private notebook for that moment of reconsideration.
What it does
Save a decision's rationale, assumptions, review condition and exact source quote. Later evidence is paired with a snapshot of the decision it relates to. A hypothetical question stays separate from an explicit change report, and the owner reads the quote before choosing whether to reopen.
The MCP connection lets a compatible assistant read that context and submit proposed checklist wording after the owner reopens. The proposal leaves the current checklist unchanged. The owner reviews the exact before/after in Reopen and approves separately; history retains the original reasoning and approved consequence.
In the demonstration, the owner enters an offline-walkthrough proposal through a real browser MCP client. The tool saves that supplied wording as an unapproved draft. It does not generate the suggestion.
How I built it
React and TypeScript provide the notebook and browser client. A Node.js server uses SQLite for private accounts, saved records and history. The official MCP SDK serves protocol 2025-11-25 over Streamable HTTP, and the browser performs actual initialization, tool discovery and calls.
Access covers one notebook, starts read-only, expires after an hour and can be revoked. Optional drafting still requires owner reopening and a current notebook version. No MCP tool can reopen a decision or approve a checklist change.
The hackathon update added this MCP server, scoped access, browser client and read-and-draft workflow to the existing decision notebook. The chosen Alexa+ route needs no Bee or Echo device. It is not a live Alexa+ distribution or Echo connection.
Challenges
A draft must not become a hidden approval. Expired or revoked access, stale versions and delayed replies all needed checks so an older connection could not regain control or overwrite newer work.
The browser-to-owner handoff also needed care: a review link should open the intended evidence once, survive sign-in and allow the owner to return to the notebook. Those transitions are covered alongside isolation between notebooks.
Accomplishments
The current release passed 35 Node tests, the browser MCP workflow, prior browser regressions and a production build. Checks cover real protocol calls, scoped access, revocation, expiry, stale writes and separate owner approval. Independent source review is recorded separately from executed tests.
The 105.64-second demonstration follows deliberately fictional venue-planning records through context retrieval, evidence review, owner reopening, a saved proposal, approval and revocation. Judges can reproduce the workflow without a paid AI key or cloud account.
What I learned
A source quote records what someone said; it does not prove that the statement is true. Reopen uses conservative lexical triage, not an LLM or fact checker, and unfamiliar or mixed phrasing can be misclassified. Keeping the exact quote beside the decision lets the owner assess it.
Codex supported implementation and review, Claude provided an independent source audit, and Deepgram supplied demonstration narration and caption timing. These tools do not independently verify the notebook's facts.
What's next
Test whether the saved rationale helps people reconsider actual project plans. Improve ambiguous-language handling and explore compatible assistant interfaces while preserving explicit owner approval. The app currently has private notebooks, not shared team workspaces; no customer usefulness study is claimed.
The optional Bee connector remains separate and fixture-tested. No real Bee or Apple Watch recording has been verified, and this entry does not seek the Bee track. No AWS integration or mini-challenge is claimed.
Run and judge it
MIT-licensed source · Judge guide · MCP verification and friction log
Use Node.js 22.14+, run the documented local setup, create an account and choose Explore an illustrative example. The guide walks through the actual MCP connection and separate approval steps. All example statements are fictional.
Reopen revisits past decisions when later evidence changes their assumptions. Understudy, a separate entry, rehearses equipment-lending requests to find missing policy instructions. They have different records, workflows and demonstrations.
Log in or sign up for Devpost to join the conversation.