Daniele
66d83358d9
The single-user notifications.md mechanism (a file in data/) died in the multi-user move: assistant's prompt still pointed at it, but nothing read it. Replace it with a memory note: - event-triage injects user-memory/notifications.md verbatim on every pass and treats it as authoritative over its default heuristics - a shared common/notifications.md fragment, included by assistant, kid and project-coordinator, tells the chat agents to record preference requests there: one dated rule per bullet under a source heading or General, asking for the source when ambiguous - docs/system-agents.md explains the steering to users
20 lines
1.1 KiB
JSON
20 lines
1.1 KiB
JSON
{
|
|
"name": "Event triage",
|
|
"description": "Hidden background agent. Spawned periodically by the scheduler. Processes pending MCP events (email, WhatsApp, calendar), evaluates relevance, and notifies the user via notify() when something is worth surfacing. Ephemeral: session is discarded as soon as the turn ends.",
|
|
"friendly_description": "Background agent that periodically reviews incoming email, WhatsApp, and calendar events and pings you when something matters.",
|
|
"i18n": {
|
|
"it": {
|
|
"name": "Triage eventi",
|
|
"friendly_description": "Agente in background che esamina periodicamente email, WhatsApp ed eventi del calendario e ti avvisa quando qualcosa è importante."
|
|
},
|
|
"fr": {
|
|
"name": "Tri des événements",
|
|
"friendly_description": "Agent en arrière-plan qui examine périodiquement les e-mails, WhatsApp et les événements du calendrier et vous avertit quand quelque chose compte."
|
|
}
|
|
},
|
|
"type": "system",
|
|
"inject_memory": ["user-memory/index.md", "user-memory/notifications.md"],
|
|
"icon": "icon.png",
|
|
"strength": "low"
|
|
}
|