Configuration is data
Every agent comes back as JSON.
Each MCP read returns the configuration as JSON, under the same names the tools take. Your coding agent writes it into the repo, so nothing is translated on the way back in.
{
"handle": "invoice-exceptions",
"name": "Invoice exceptions",
"llmModel": "claude-sonnet-4-5",
"scripted": true,
"availability": {
"hub": false,
"embed": true,
"delegation": false,
"schedules": true,
"triggers": false,
"api": true
},
"resources": {
"operations": [
"finance-system.get_purchase_order",
"finance-system.register_supplier_query"
],
"functions": ["invoice-comparison"]
},
"idempotencyKey": "invoice-exceptions-create"
}Speaker notes
The prompt fields (purpose, personality, background, policyRules, outputFormatting) sit beside it as Markdown files, the script as script.json, functions and widgets one file each, tests as tests.json. No file holds a credential. Keep the idempotencyKey: if a create fails, the retry can’t make a second agent.