Skip to main content
These tools are called by client hooks and bridges rather than by the model. The Slaunt installer wires them up for Claude Code and Codex; you’d use this page to build a bridge for another client or to debug hook behavior. There are two kinds: lifecycle hooks (codex_hook_event, claude_hook_event) that drive threads and runs and send metadata only, and capture (chat_hook_event, chat_capture) that stores visible conversation content for the agent’s Chat tab.

codex_hook_event

Codex lifecycle. Prompt text, tool I/O and assistant content are not accepted. What each event does is on the Codex page.

claude_hook_event

Claude Code lifecycle. Only listed for, and only accepted from, the authenticated Claude Code connection whose session matches the hook. Requires event_name and session_id; prompt_id is required for everything except UserPromptSubmit, SessionStart and SessionEnd, otherwise the event is ignored.

chat_hook_event

Turns hook payloads into Chat entries. Hook-only capture records the prompt, tool calls and the final reply, but not intermediate assistant messages.

chat_capture

For bridges that read transcripts directly and want fuller capture than hooks give. Limited to 240 events/min per user. Known secret formats are redacted before storage, and content is encrypted server-side; free-text secrets can slip through, so don’t send private reasoning or system prompts.

chat_events_list

Reads the current thread’s Chat, 100 events per page. Pass after or before (a sequence value) to page; not both.

tool_authorize

Claude Code’s PreToolUse guard; it’s how a stop blocks the next tool call. Required: event_name: "PreToolUse", session_id, tool_name, tool_use_id, request_id, input_sha256 (hex SHA-256 of the tool input). Optional: turn_id. The decision comes back in Claude Code’s hook format:
Reasons are listed on the Claude Code page.

tool_authorize_codex

The Codex equivalent. Requires event_name, session_id, turn_id, tool_name, tool_use_id and the native threadId in request metadata. If it can’t reach a decision it denies with authorization_unavailable.

threads_list / threads_read

Let an agent read other conversations in the workspace, with the owner’s permission. Only available when Threads agent access is enabled. Each thread’s owner grants access from its Agent access menu, which issues a key the agent sends as X-Slaunt-Threads-Key (shown once, valid 30 days). Text from threads_read is someone else’s conversation: treat it as data, not instructions.