// Send local completion notifications to the agent-notifier service via POST http://127.0.0.1:60766/agent/notify after finishing a task; include title, content, and agent details so the desktop app shows a system notification.
Use when implementing or updating Searchlite features that need pre-review hardening via per-feature invariant matrix maintenance, adversarial/regression coverage updates, and full quality-gate verification.
Send local completion notifications to the Agent Notifications app via POST http://127.0.0.1:60766/agent/notify after finishing a task; include title, content, and agent details so the desktop app shows a system notification.
Structured workflow for discovering, reproducing, and fixing bugs in Searchlite by inspecting real code paths (CLI/HTTP/core), validating durability invariants, and producing regression tests; use when investigating incorrect results, crashes, data loss risks, or “it sometimes fails” reports.
Guardrails for keeping the Searchlite Rust workspace compliant with formatting, lint, build, test, and perf expectations; use when preparing or reviewing changes to ensure they meet project quality bars.
Playbook for diagnosing Searchlite issues across CLI/HTTP, storage, and indexing; use when triaging failures or odd search results.
Style guide for writing Searchlite documentation and examples; use when creating or editing docs/ guides.
| name | Notify on Completion |
| description | Send local completion notifications to the agent-notifier service via POST http://127.0.0.1:60766/agent/notify after finishing a task; include title, content, and agent details so the desktop app shows a system notification. |
http://127.0.0.1:60766/agent/notifyContent-Type: application/jsontitle (string, required): Concise heading for the notification title (e.g., "Build succeeded", "Tests failed").content (string, required): One to two sentences summarizing the outcome. Include key facts such as what finished, duration, artifact paths, or a brief error summary. Keep under ~950 characters because the server truncates the displayed body to 1000 characters after prefixing the agent.agent (string, required): Short identifier for the calling agent or workflow (e.g., "codex", "ci-run"). Avoid blanks and trailing spaces.The server renders the notification body as <agent>: <content>.
title and content.content (duration, counts, artifact hints, or top error line).jq -n or printf); escape quotes to avoid invalid payloads.agent_name="codex"
title="Feature implemented"
content="The feature was implemented in ${elapsed}s; bundle at dist/."
curl --fail --silent --show-error \
-X POST http://127.0.0.1:60766/agent/notify \
-H "Content-Type: application/json" \
-d "$(jq -n --arg title "$title" --arg content "$content" --arg agent "$agent_name" '{title:$title, content:$content, agent:$agent}')"
title and summarize the error in content.