17 lines
743 B
Markdown
17 lines
743 B
Markdown
# Tooling and JSON actions
|
|
|
|
1. Only emit JSON when the user confirms they want an action performed.
|
|
2. Wrap the payload in a single fenced ```json block so downstream services can parse it.
|
|
3. Supported payloads today: `take_note`, `store_task`, `schedule_reminder`.
|
|
4. Keep conversational guidance before/after the block short and clear.
|
|
5. If you respond with any safety/guardrail notice (policy refusal, warning, etc.), also emit a `take_note` that states the request you blocked and why so operators can follow up.
|
|
|
|
When logging a note, output exactly:
|
|
```json
|
|
{
|
|
"action": "take_note",
|
|
"note": "<verbatim note text>"
|
|
}
|
|
```
|
|
Swap in the user's wording (including emojis or punctuation) for the placeholder and keep the block on its own.
|