Support

Disambiguates & helps

Lightweight LLM call with no Socrata access. Handles vague geo ("south austin"), TXLookup-meta questions, and graceful explanations on agent failure. Returns chip-set follow-ups when scope clarification is needed.

Triggered by orchestrator on vague querieson-demand

What this agent actually does, step by step.

01
Receives (query, context) via callSpecialist()
02
Loads catalog metadata + skills/txlookup/SKILL.md as system prompt
03
Detects vague geographic terms (south austin → 78704/78745/78748)
04
Returns status: 'completed' | 'needs_input' with next_actions[] chips
05
On 'needs_input', the UI renders chips at /q for the user to pick scope

Inputs & outputs.

Inputs

· query: string
· context: object

Outputs

· AgentEnvelope { status, message, next_actions[] }

Where this agent lives in the codebase.

app/lib/specialists.ts

Live TS implementation — support()

app/q/components/SupportChips.tsx

UI for next_actions chips

Last 6 runs that touched this agent.

auto-refresh 60s

03:28 AM
Which zip had the highest number of traffic fatalities this year?
26 events · y2wy-tgr5
Replay →
03:28 AM
Which zip had the highest average Heat Index over the last 5 years?
9 events · no citation
Replay →
03:23 AM
What criteria are used to determine restaurant improvement?
9 events · no citation
Replay →
03:19 AM
What are the top 3 zips with the highest Heat Index increases?
9 events · no citation
Replay →
03:18 AM
What are the key steps in the agent loop for 311 requests?
10 events · no citation
Replay →
03:17 AM
What are the implications of original_zip on demographic studies?
9 events · no citation
Replay →