pinecallDocs
Running an agent / pinecall console

pinecall console

Open the console on this project's agent.

pinecall console [agent] [--prod] [--no-open]

The console of this project's environment, in a browser, signed in. The one gateway serves both consoles at its one name: production's at <url>/, the sandbox's at <url>/sandbox/ — the same origin, the same sign-in. This verb opens the sandbox's — your copies of the agents, their calls as they happen, chat, evals and their suites, docs, memory, the widget and its preview, and how to reach your copy by phone — and --prod opens production's, if your org lets you act there.

Terminal
$ pinecall console
console  https://cloud.pinecall.io/sandbox/?login=lc_9f2   (opens within five minutes, once)

The key never travels. The gateway mints a one-use code standing for this terminal's key, in the environment the verb acts in — five minutes, one use — and the page spends the code for a key of that browser's own, which is revoked on its own from Tokens. Name an agent (pinecall console clinica-norte) and it opens that agent's screens instead of the org's floor. A machine with no browser prints the URL, and --no-open says not to try. A server's token signs no browser in: it names no person, and the gateway says so.

One sign-in opens both consoles, because they are one origin: the chip in the top bar switches between / and /sandbox/, and the page tells the environment it is in from its path.

Which screens each console has is one table in the console's source (the console's src/console/lib/mode.ts): running the org — numbers, tokens, providers, the team, usage — and the platform's own screens are production's; Dev chat, running a suite and Phone testing are the sandbox's; Home, Overview, Live, Sessions, Personas, Simulations, Evals, Memory, Docs and every tab of an agent, its Lexicon among them, are both's. An admin opens a colleague's copy from the sandbox's console, never from production's, which has no corners (environments-and-teams.md).

The header picks an environment only for a person. A server's token acts in the environment its prefix names, and a header saying the other is refused; a person's key acts where pinecall-env says — the sandbox when it says nothing — and in production only while their switch is on.