hotline-pickup

Hotline: Pickup — Workspace Identity

Generate a concise identity for this workspace so other agents can find and understand it.

When This Runs

• Automatically during hotline-dial workspace resolution (if identity is stale or missing)
• Manually when a user or agent wants to refresh the workspace identity

Script Paths

Every independent shell block below resolves the Hotline plugin path and loads HOTLINE_PICKUP_SCRIPTS in that same shell. Shell state does not persist across tool calls. Codex: these paths resolve under Claude Code; substitute the Hotline plugin directory before running a block.

Steps

1. Check Cache Freshness

Run:

# Codex: this path resolves under Claude Code; substitute the Hotline plugin directory.
PLUGIN_ROOT="${CLAUDE_PLUGIN_ROOT}"
eval "$(bash "$PLUGIN_ROOT/scripts/paths.sh")"
bash "$HOTLINE_PICKUP_SCRIPTS/identity-cache.sh" is-stale

• Exit 0 (stale or missing): proceed to introspection (Step 2)
• Exit 1 (fresh): read and return the cached identity, skip to Step 5

If the caller passed --fresh, skip this check and always proceed to Step 2.

2. Introspect the Workspace

Run the introspection script to gather project metadata:

# Codex: this path resolves under Claude Code; substitute the Hotline plugin directory.
PLUGIN_ROOT="${CLAUDE_PLUGIN_ROOT}"
eval "$(bash "$PLUGIN_ROOT/scripts/paths.sh")"
bash "$HOTLINE_PICKUP_SCRIPTS/gather-workspace-info.sh"

This collects CLAUDE.md, package files, README excerpt, recent git log, and tech stack signals, returning structured JSON. Use this data to synthesize the identity in Step 3.

3. Synthesize Identity

From the gathered information, create:

• name: A short, recognizable project name (e.g., "Acme Marketing Site")
• description: 1-2 sentences max. What this workspace IS and what it DOES. Keep it concise — this is for quick matching, not a full dossier.
• tags: 3-8 short keywords covering tech stack, domain, and purpose (e.g., ["nextjs", "marketing", "blog", "typescript"])