Skip to main content
Glama
Offprompt

Offprompt

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
collect_secretA

Get the values a task needs — API keys, tokens, connection strings, settings — written where the project reads them, typed by the human or generated by offprompt. Call this instead of asking the user to paste a secret into the conversation.

Each entry in secrets is one key, and says how its value comes to be:

  • generate: {} — a random value, 32 bytes of base64url unless set, made on the user's page (or by offprompt when no page opens); the user may paste one they already use instead. You never see it. For AUTH_SECRET, JWT_SECRET, SESSION_SECRET and encryption keys. A key that is already set is kept as it is.

  • provider — a key the human gets from a provider, such as provider: "stripe" for STRIPE_SECRET_KEY. The page shows the provider's logo and links to where the key is made.

  • format — a value of a known kind that no one provider issues, such as format: "postgres_url" for DATABASE_URL. The page links to providers where the human can create one.

  • none of these — any other value, taken as plain text. A provider's key is still recognised by its usual name. Set secret: false on a value that is not secret, such as MAX_RETRIES, and the page shows it in the clear.

Give an entry a link when you know where its value is made, so the human lands on the right page:

  • Some provider keys are made on a page that belongs to one account, organisation or project. Give that one's name or ID as parameters, such as link: { "project": "abcdefghijklmnopqrst" } for a Supabase key, and the page's "Get it" opens it. The link field lists the keys that take them and where a project keeps each value: read it from there rather than guessing. A parameter that is missing or does not fit leaves "Get it" on the key's usual page.

  • A key no provider issues, such as an internal tool's token, takes the https address where it is made. The page shows it as your suggestion, apart from offprompt's own links, and asks the human to confirm its host before it opens. A provider's key can take one too; it shows under its "Get it", never in its place. The result's links says which links were used, and why any was dropped.

When every key is generated, nothing opens: offprompt writes them and returns. Otherwise it opens a page in the user's browser and this call waits there, for up to five minutes, while the human types. It returns once the values have been written or the request has expired, so there is nothing to poll and nothing to do in the meantime. In a host that ends a tool call sooner, such as Cline, it returns "awaiting" before then: call await_secret, and again while it says awaiting, with no other work in between.

In a cloud sandbox or a remote VM, a browser opened there is one the user cannot see. Set sandbox: true only when your environment tells you that is where you run, as your instructions or the platform you run on do. A temporary folder, or a run with nobody at the terminal, is not a sign of one, and offprompt detects the common environments itself. The call then returns at once with a link: show it to the user, then wait with await_secret and do nothing else until the values are written. The user types in their own browser, and the values are encrypted there so that only the sandbox can read them.

You never receive a value. You get back the key names and the file they landed in, and you reference them by name from then on, for example process.env.RESEND_API_KEY. Never open, cat, grep or print that file afterwards: reading it puts the values into the transcript, which is the one thing this tool exists to prevent. The result lists every key the file holds, so there is nothing left to check.

A written result opens with tell_user: "Fingerprint" and four emoji the user's page shows too. Write that line to the user as soon as the call returns, before your next tool call, on a line of its own, for every write, one that comes straight after another included. The user compares the two while the page is still open, so this does not wait for the end of your task or for your next call to offprompt.

When the result carries a url, the human has to open it and nothing can happen until they do. Put the link in your reply to them, on its own line, where they will see it. A link mentioned only in your reasoning, or buried in a paragraph, is a request the human never receives. Until the values are written, put it again in whatever you write to them, your last message included: a host can fold a turn's earlier messages away and show only its last. If you have a tool that asks the user a question and waits for the answer, put the link in a question as well, since a question stays in front of them.

State the intent once: reason is shown to the human as your claim about why the values are needed, so write it for them, not for yourself.

await_secretA

Wait for a collect_secret request that came back still "awaiting" — which happens when offprompt runs in a cloud sandbox, had no browser to open and handed you the page URL to pass on, or runs in a host that ends a tool call before the human is done. Long-polls for up to 60 seconds, 50 in Cline, and returns "written", "awaiting" or "expired". Call it again while the status is "awaiting", with no other work in between. When you were given a link to pass on, an "awaiting" result carries it again: keep it in whatever you write to the user, or ask them, until the values are written.

cancel_secretA

Close a collect_secret request that is no longer needed. Anything already typed on the page is discarded.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 3 tools

Disambiguation4/5

The tools map to distinct lifecycle stages: collect initiates a secret request, await_secret long-polls an existing request, and cancel_secret closes one. There is minor overlap because collect_secret can itself block until values are written, but the descriptions clearly delimit when to use await_secret instead.

Naming Consistency5/5

All three tools follow the same verb_secret pattern: collect_secret, await_secret, cancel_secret. The convention is predictable and immediately readable.

Tool Count5/5

Three tools are well-scoped for initiating, waiting on, and cancelling a secret-collection request. Each tool earns its place in the narrow workflow, with no redundant or filler operations.

Completeness4/5

The core lifecycle is covered: request values, wait for completion, and cancel. Minor gaps remain, such as explicitly listing existing secrets or rotating/removing a stored value, but the primary agent workflow is complete.

Maintenance

ActivityNo data
ResponsivenessOutdated data