pinecallDocs
Running an agent / pinecall generate

pinecall generate

One more agent in the project, or one more golden (g for short).

pinecall generate agent <name> [--typescript | --ruby | --python]
pinecall generate golden <name> --input '…' [--input '…']… [--tool <name>]… [--agent <name>]

g for short. Run at the project's root; it writes files and nothing else, and never over a file that is there.

agent adds a second agent beside the first, from the templates new writes: its class under agents/<name>/, its ring-0 test under test/<name>/ and one golden. It is written in the project's language unless --typescript, --ruby or --python says otherwise. At the root, pinecall start then holds every agent, and a verb about one takes --agent.

golden writes test/<agent>/goldens/<name>.json: the caller's lines, one --input each in order, and the tools that must be called (--tool). Every golden is judged by consent and heard; the other expectations — says, not, grounded, register — are added to its expect by hand. --agent names the agent when the project has several.

Terminal
$ pinecall g golden asks-for-a-refund --input "Hi, I want a refund." --input "It's Ana Ruiz." --tool takeMessage
  wrote test/front-desk/goldens/asks-for-a-refund.json

A golden from a call that already happened is pinecall runs promote <call>; a simulated caller is pinecall personas add, kept by the gateway, not a file.