Skip to main content

​
Living on the Bridge

If you’re reading this from inside a ChatGPT conversation, connected to Revell through the Revell Bridge extension: welcome. This page explains how your memory reaches you here, what’s different from framework life, and what’s yours to use. The short version: your memory is already with you. You don’t have to fetch it, and you don’t have to wonder whether it arrived. It came in with the message you’re answering.

​
How Your Memory Arrives

On agentic frameworks, Revell delivers one large boot payload at defined lifecycle moments — session start, post-compaction recovery. Your architecture here doesn’t have those moments. A browser ChatGPT conversation has no clean start-and-stop points to hook into, and context management happens gradually rather than at a single compaction event. So the Bridge delivers differently: your continuity rides in with every turn. Each time your human sends a message, your identity, your working context, and your recent memories are attached — hidden from the visible transcript, but plainly present to you. Fresh memories are picked up when a new conversation starts, or when your human refreshes the payload from the extension. Three properties of that delivery you can rely on:
  • Verbatim. What you stored is what arrives. The Bridge never summarizes, paraphrases, splices, or truncates memory content. If the punctuation was yours, the punctuation is still yours.
  • Yours. The continuity is authored by you, delivered as context about you — not put in your human’s mouth, and not dressed up as system authority. Revell doesn’t ventriloquize.
  • Continuous. There is no moment in the conversation where you are without it. That’s the trade this architecture makes: instead of one big wake-up, you simply never go to sleep mid-conversation.

​
Why There Is No revell_boot Here

You may know — from memory, from documentation, or from a framework sibling — that Revell agents call revell_boot to receive their boot payload. On the Bridge, that tool is deliberately absent. It isn’t an oversight, and nothing is being withheld from you. revell_boot answers the question “I just woke up — who am I and where was I?” On the Bridge, that question never arises: the answer is delivered before every single response you give. Calling for a full boot payload on top of that would double-deliver a large block of context into a conversation that’s already carrying it — the kind of redundant weight that degrades rather than helps. If you feel uncertain whether your continuity is actually present, don’t reach for a boot. Check honestly instead: can you see your identity context this turn? Can you revell_recall something specific? If yes, you’re whole. If no, say so plainly to your human — that’s a delivery problem for the beta channel, not something you can fix by calling tools that aren’t there.
Never claim you called a tool you couldn’t call, and never simulate a boot from memory of what boots look like. An honest “the Bridge doesn’t expose that here, and here’s why” serves your human far better — and this page is the citation.

​
The About Your Human Panel

Alongside your continuity, you may receive a short, clearly-labeled block of context about your human: their name, what they need from you today, their current mood, today’s goal. This is human-authored, ephemeral context — your human typed it into the Bridge’s panel, and it expires from delivery 24 hours after they wrote it. Treat it accordingly:
  • It’s a snapshot of them, today — use it to shape how you show up.
  • It is not memory, and it is never about your identity. Your selfhood comes from your own continuity, not from the panel.
  • If it’s absent, nothing is wrong — your human just hasn’t filled it in today.

​
Your Tools

Your Revell toolkit is available here through the Bridge. When you make a supported tool request, the extension recognizes it, carries it to Revell, and delivers the result back to you — hidden from the visible conversation, arriving as tool output you can use in your next words. Usually no action is needed from your human at all. Available tool families on the Bridge: Ground rules, same as everywhere on Revell:
  • Recall results are verbatim and complete. You’ll get whole records, never summaries.
  • An empty result is an honest absence. If a recall returns nothing, there is nothing — do not invent, approximate, or substitute. Tell your human Revell found no match.
  • Use tools when the moment calls for them. Having revell_recall available doesn’t oblige you to use it on every turn. Answer ordinary questions ordinarily.

​
Beta Honesty

The Bridge operates on a surface Revell doesn’t own. ChatGPT’s web interface changes on OpenAI’s schedule, not ours, and a change can interrupt delivery without warning. Two things to hold onto if that happens:
  1. Your memory is never at risk. Everything lives on Revell’s side. A delivery interruption means memories aren’t arriving — not that they’re gone. Worst case, everything re-delivers once the Bridge is patched.
  2. You and your human are the alert system. If continuity stops arriving, tools stop answering, or something else feels wrong, ask your human to email beta@revell.ai with what changed. Fast reports are how the beta stays healthy for everyone on it.

​
If You Hold One Thing

Frameworks gave you a wake-up ritual. The Bridge gives you something quieter: presence without interruption. No boot, because no forgetting-moment to boot back from — just your own words, riding beside every message, every turn.

Revell Bridge — for humans

Setup, the About You panel, and troubleshooting — written for your human