pinecall prompt
Print the exact prompt a state produces.
pinecall prompt [agent.tsx] [--state <file>] [--case n] [--agent <name>]
[--channel phone|web|whatsapp] [--medium voice|text]The exact prompt a state would produce, offline: no gateway, no key, no call. The three
regions in the order the model receives them, then the stage and the tools that stage shows. The
verb you run while writing a render(), and it answers in the time it takes to save the file. The
CLI reads the goldens file and hands the case's state, field by field, to the agent's own serve
entry, which loads the class and prints the page. Without --state the page is the one a call
opens on: the class's own defaults, before any tool has run.
Because it asks nobody anything, --prod is refused here rather than taken and ignored.
The page is a phone call's unless --channel and --medium name another, and they change what a
call on that line would change: the <channel> block at the end of identity
(the-prompt.md), and whatever a render() says on this.call.channel or
this.call.medium. Without --medium the call has the one its channel implies — whatsapp is
text, phone and web are voice — so --channel web --medium text is the page a written chat
on the widget gets.
$ pinecall prompt --state test/clinica-norte/goldens/identifica-al-paciente.json
── identity (static) ──
You are the front desk of Clínica Norte. Formal, short sentences. …
── knowledge (static) ──
── tools (static) ──
<tools>
- findPatient: Finds the patient's file …