🎯 Use case
This module implements the “RemoteTriggerTool” tool (Remote Trigger) — something the model can call at runtime alongside other agent tools. On the API surface it exposes REMOTE_TRIGGER_TOOL_NAME, DESCRIPTION, and PROMPT — mainly types, interfaces, or factory objects.
Generated from folder role, exports, dependency roots, and inline comments — not hand-reviewed for every path.
🧠 Inline summary
export const REMOTE_TRIGGER_TOOL_NAME = 'RemoteTrigger' export const DESCRIPTION = 'Manage scheduled remote Claude Code agents (triggers) via the claude.ai CCR API. Auth is handled in-process — the token never reaches the shell.'
📤 Exports (heuristic)
REMOTE_TRIGGER_TOOL_NAMEDESCRIPTIONPROMPT
🖥️ Source preview
export const REMOTE_TRIGGER_TOOL_NAME = 'RemoteTrigger'
export const DESCRIPTION =
'Manage scheduled remote Claude Code agents (triggers) via the claude.ai CCR API. Auth is handled in-process — the token never reaches the shell.'
export const PROMPT = `Call the claude.ai remote-trigger API. Use this instead of curl — the OAuth token is added automatically in-process and never exposed.
Actions:
- list: GET /v1/code/triggers
- get: GET /v1/code/triggers/{trigger_id}
- create: POST /v1/code/triggers (requires body)
- update: POST /v1/code/triggers/{trigger_id} (requires body, partial update)
- run: POST /v1/code/triggers/{trigger_id}/run
The response is the raw JSON from the API.`