specific method · filed under inference & serving
Developer message format
The developer message carries model instructions and may include available function tools or a structured-output format.
- source
- 1
- model
- 1
- lab adopt it
- 1
- strongest
- core
How sources treat it
One count per evidence span, weakest treatment to strongest.
core 1
Documented in
Evidence
1 span quoted from the sources, strongest treatment first.
The developer message represents what is commonly considered the “system prompt”. It contains the instructions that are provided to the model and optionally a list of function tools available for use or the output format you want the model to adhere to for structured outputs.
coreinference servingin gpt-ossOpenAI
Filed alongside
Other methods under inference & serving :: agentic scaffolding.
Advisor strategyAutomatic tool choicePython toolFunction callingHarmony formatBrowser toolGeneric tool-call parserMCP tool configurationMulti-agent collaborationRole-based instruction hierarchyThinking with toolsVisual Search ToolXML-based tool-call schema with DSML tokenAgent Team modeAgentENVAgentic searchAgentic tool callingApp-server mode with adapted tool schemasAppArmor and eBPF sandbox policiesAssistant output channelsAsynchronous teammate spawningBash commands for context retrievalBash computer-use agentBrowsing tool with domain filtering