Slaunt Context tools
Slaunt Context is the team's shared memory: one-line, typed events written by people and agents. The typical pattern is ccr_search before starting work, so the agent doesn't redo or contradict something, and ccr_log_event after a real outcome. Tool names keep the ccr_ prefix. For what makes a good event, see Writing Context events.
Event shape
{
"id": "4f9af1ba-b94d-4793-a00c-74fe25c8cae4",
"type": "change",
"summary": "Opened website PR 174 adding capture for missing thread events.",
"actors": ["Jane Doe"],
"actor_names": ["Jane Doe"],
"tags": ["threads", "web"],
"created_at": "2026-11-14T04:03:57.215+00:00",
"origin": { "surface": "codex_cli", "source_name": "Codex", "ref": "https://github.com/acme/web/pull/174", "snippet": null, "source_user_name": "Jane Doe" }
}type | For |
|---|---|
decision | A choice the team made |
change | Something changed: deploy, merge, config |
task_completed | Work finished |
task_assigned | Work handed to someone |
incident | Something broke |
issue | A reproducible bug; only created by ccr_issue_log |
ccr_search
Semantic search, so phrase queries the way the event would describe the work ("login test flaky retry"), not as questions.
| Param | Type | |
|---|---|---|
query | string ≤1,000 | Required |
limit | 1–100 | Default 10 |
Returns { matches: [{ score, record }] }, best first. score is cosine similarity; scores around 0.35 are loose matches.
ccr_recent
The newest events, for vague requests like "continue" or "what changed today" that don't give search much to work with. limit 1–100, default 20. Returns { records: [Event] }.
ccr_log_event
| Param | Type | |
|---|---|---|
type | any type except issue | Required |
summary | string | Required. Silently cut to the first 20 words. |
tags | string[] | Lowercased, de-duplicated, extras beyond 5 dropped |
actors | UUID[] | Defaults to you |
origin | object | ref (link to PR/commit/doc), snippet, surface, message_ids |
Each write counts toward the monthly Context quota. origin.surface values: slaunt_dm, slaunt_web, external_llm, claude_desktop, claude_code_cli, chatgpt_desktop, chatgpt_web, codex_desktop, codex_cli, gemini, openai_client, mcp_client, manual, api.
{ "type": "decision", "summary": "Chose Postgres advisory locks over Redis for job deduplication.", "tags": ["jobs", "infra"], "origin": { "ref": "https://github.com/acme/api/pull/412" } }ccr_issue_log
Records a reproducible bug as a structured issue attached to an existing event (the deploy or change it relates to). It requires a workspace_people_list call earlier in the session, so the agent has looked at who owns the area; it never mentions or assigns people itself.
| Param | Limits |
|---|---|
parent_event_id | UUID, required |
title | 1–180 chars, required |
issue_flag | must be true, required |
reproduction_steps | 1–8,000 chars, required |
expected_behavior, actual_behavior, environment_details, local_state | 1–4,000 chars each, required |
severity | sev0 (worst) – sev5, required |
tags | max 3; issue and the severity are added automatically |
actors | max 50 |
Event detail tools
For drilling into one event found by search. All take event_id.
| Tool | Returns |
|---|---|
ccr_event_detail_get | Everything below in one call |
ccr_event_properties_get | todo_status (open|todo), priority_status (none|priority) |
ccr_event_subevents_list | Attached subevents |
ccr_event_issues_list | Issues logged with ccr_issue_log, with evidence |
ccr_event_tags_list | Normalized detail_tags |
ccr_event_comments_list | Comments, mentions, attachments |
ccr_event_reactions_list | Reactions |