Update LLMs
01Agent
Agent that update models and LLM providers.
Agent
Agent that update models and LLM providers.
Instructions file GitHub Copilot
Copilot instructions for webgptorg/promptbook, covering copilot instructions for promptbook, project overview, architecture & key concepts, book language & commitments and monorepo structure.
Instructions file CodexOpenCode
AGENTS.md instructions for webgptorg/promptbook, covering how to contribute, code style, emoji in [brackets], generated code and dictionary.
Command
Actions influences from the pipeline or task into external world. Like turning on a light, sending an email, etc.
Command
Which version of the Book language is the .book.md using.
Command
Expect command describes the desired output of the task (after post-processing).
Command
Command "FOREACH" from webgptorg/promptbook, covering foreach command, example usage and 🍭 itterations and foreach command.
Command
Format command describes the desired output of the task (after post-processing).
Command
Specifies the application type and interface requirements that this promptbook should conform to.
Command
Instrument command is used to specify the instrument to be used in the pipeline or task like search, calculate, etc.
Command
Joker parameter is used instead of executing the task result if jokers value meets the expectations requirements.
Command
Tells promptbook which external knowledge to use.
Command
Tells which modelRequirements (for example which model) to use for the prompt task execution.
Command
Command "PARAMETER" from webgptorg/promptbook, covering parameter command, example usage and ⭕ parameters.
Command
Persona command is used to specify who the system is, it will be transformed into system message, topt,...
Command
Defines the postprocess function to be used on the result from LLM and before the result is validated.
Command
Defines the purpose of the markdown section - if its a task and which type or something else.
Command
Command "URL" from webgptorg/promptbook, covering url command, example usage and 🆔 pipeline urls and identification.
Agent
Every agent has a visual identity used across the UI (directory cards, chat header, manifest icons, social previews). It is resolved from the agent's book with deterministic fallbacks, so an agent always has an avatar.
Agent
Federation lets one Agents Server instance see and reuse agents hosted on other Agents Servers. It is configuration-driven and read-only: a federated server is never written to; its agents are referenced by URL or copied on demand.
Agent
Agents are organized in a folder tree per server instance. Folders group agents in the directory (homepage, header menu, dashboard) and drive bulk operations (visibility, export). State lives in prefixAgentFolder plus Agent.folderId/Agent.sortOrder (Data model).
Agent
How one stored agent source becomes the effective (resolved) source that is actually compiled and executed. Resolution expands FROM (inheritance) and IMPORT (textual inclusion) commitments, rewrites compact agent references into canonical URLs, and degrades gracefully when references cannot be loaded.
Agent
Compiling an agent (resolving inheritance, building model requirements, indexing KNOWLEDGE into provider-side vector stores) is expensive. The server therefore prepares agents in the background ahead of chat time and caches every derived artifact by content hash, so the first user message does not pay the indexing…
Agent
Agents whose book is open learn from their conversations: after a turn, the executing agent may append new content to its own source (samples of the exchange, teacher-suggested commitments). The server persists these changes append-only, so learning can never rewrite or corrupt the authored book.