Pumpkin

What it does

The rest of the story.

The public browser demo has locally interactive control, projector, voice, saved looks, and same-device remote tabs without server writes or AI spend; signed-in mode adds owner-scoped cross-device pairing and autonomous pumpkin-bot replies.

What you can ask it

Tools the bot can actually call.

Registered server-side, scoped to the signed-in user. The bot calls the tool — it never shells out, and it never handles the credential behind it.

Pumpkin Screens. List the caller's registered jack-o'-lantern projector screens — room slug, label, and whether the screen is currently live
Speak Through The Pumpkin. Make the caller's jack-o'-lantern projector actually say a line out loud, with a facial expression

How it runs

What happens when you use it.

Not a chat window with a plugin behind it. Every step below is something the app declares in its manifest, which is why it can be told to you plainly.

01
You open it, or the assistant does
Opening ?app=pumpkin loads its 2 screens into the shared cockpit, starting on pumpkin-control. The ribbon, the ticket list and the assistant are already there — the app contributes views, not a second application to log into.
02
Or you just ask
The assistant classifies what you asked for and hands it to the bot that owns that domain. You do not pick the app, and you do not learn a command — routing is by declared capability, not by keyword matching a menu.
03
A named bot picks it up
pumpkin-bot is accountable for the work. 4 declared capabilities say what it is trusted to do; the tokens and dollars it spends are recorded against that identity, so the cost has a line item rather than disappearing into a monthly bill.
04
The result lands where you can check it
Back on the app's own screens, as state you own — not as a chat message you have to scroll back to find.

With the assistant

You can ignore this app entirely and just ask.

The assistant is the front door. It classifies your request, delegates to the bot that owns the domain, and answers in one voice — so you do not have to know which of the applications this happens to live in.

Routing is by declared capability, not by keyword. pumpkin-bot advertises what it is accountable for, and the assistant matches against that.
Asks that land here: anything about halloween persona, anything about in character conversation, anything about spooky improv, anything about prop voice.
The specialist does the work, not the assistant. Cost, permissions and audit stay attached to the bot above — delegation does not launder accountability.
It will tell you when it cannot. If a request needs your screen — an approval, a payment, a login — it says which app to open rather than guessing.

Accountability

4 capabilities, each attached to a named identity.

Declared in the manifest and bound to the bot above — so "what is this thing allowed to do" is a list you can read, not a prompt you have to trust.

halloween-personain-character-conversationspooky-improvprop-voice

Underneath

What every app on this site is standing on.

This app does not ship its own queue, its own credential store or its own cockpit. It declares what it needs and the platform provides it.

The surface

The rest of the story.

Tools the bot can actually call.

What happens when you use it.

You open it, or the assistant does

Or you just ask

A named bot picks it up

The result lands where you can check it

You can ignore this app entirely and just ask.

4 capabilities, each attached to a named identity.

Apps that pair with this one.

Brand Graphics

Camera Ops

Creative Studio

Dungeon Master

What every app on this site is standing on.

Cockpit & ribbon

Connectors & the vault

Queues & the mesh

Security & isolation