Operating Manual
Manual
Critical ONNO runbook entries for future handoffs.
Required
Connecting a new agent platform
ONNO runs a continuous learning loop so completed work sessions can become proposed OpenBrain lessons. The reviewer proposes lessons, but nothing is written to OpenBrain until Jack approves it on the Continuous Learning page.
Session summary requirement
At the end of every work session, the agent must insert one session summary row into loop_transcripts in Supabase project iptnecxapcrhhwufexvh. The row must include source, session_ref when available, and content.
The summary should include what was attempted, what succeeded, what failed and why, decisions made, and anything Jack explicitly said to remember.
Standing instruction
Standing instructions for any new agent MUST include: Search OpenBrain for ONNO operating context at the start of each session.
Credentials and configuration
Jack sets all values personally. Do not paste secrets into chat or commit them to the repo.
- Supabase project:
iptnecxapcrhhwufexvh - Transcript table:
public.loop_transcripts - Review table:
public.loop_proposals - Cockpit page:
/continuous-learning - OpenBrain MCP URL variable:
OPENBRAIN_MCP_URL - OpenBrain key variable:
OPENBRAIN_MCP_ACCESS_KEY - Supabase service-role variable:
SUPABASE_SERVICE_ROLE_KEY - Public app URL variable:
NEXT_PUBLIC_APP_URL
Troubleshooting
MCP clients can cache OpenBrain tool schemas. After the open-brain-mcp function adds or changes tool parameters, reconnect or refresh existing agent connectors so they can see the new schema.
Required
Alerts - what belongs here
Alerts are time- or condition-triggered reminders for Jack. Use them when future Jack must be told something on or after a date, or when a specific condition becomes true.
Alerts are not tasks with an owner and a done-state. Those belong in Asana. Agents write alerts directly with source set to agent when future Jack needs cockpit-visible context.
- Alerts page:
/alerts - Every Jack or agent alert needs
expires_at.