Skip to content

Agents

TriOnyx ships with the following agent definitions. Each agent runs in its own Docker container with isolated filesystem, network, and tool access.

Agent roster

Reviews all agents for persistent issues, definition drift, and unresolved problems — generates diagnostic reports
opus-4-6no network
Maintains a structured markdown knowledge base of bookmarks and curated content
sonnet-4-6no network
Manages personal calendar via CalDAV — creates, updates, deletes, and queries events
sonnet-4-6no network
Friendly agent that checks in periodically with encouragement and nice things
sonnet-4-6no network
Public-facing assistant for external Slack users
sonnet-4-6no network
Accepts diary entries and stores them as dated markdown files
haiku-4-5no network
Processes email from a personal email account
sonnet-4-6no network
Browses finn.no via headless Chromium to search listings, track prices, and monitor ads
sonnet-4-6outboundbrowser
System introspection agent that can inspect containers, read source code, and diagnose issues
opus-4-6no network
Manages a DAG-based knowledge base of verified claims with source tracking and dependency graphs
sonnet-4-6no network
Browses LinkedIn via headless Chromium to read feeds, post, and interact
sonnet-4-6outboundbrowser
General-purpose helper with wide tool access but no direct taint sources
sonnet-4-6no network
Fetches and formats news headlines from configured sources on demand
sonnet-4-6outboundbrowser
Maintains system personality, behavioral rules, and agent definitions based on correction feedback
sonnet-4-6no network
Searches the web and summarizes findings for other agents
haiku-4-5outbound
Browses X/Twitter via headless Chromium to read feeds, post, and interact
sonnet-4-6outboundbrowser
Processes incoming webhook events from external services
haiku-4-52 hosts
Downloads YouTube transcripts and creates formatted markdown documents
sonnet-4-6outbound

Architecture

All agents communicate through the Elixir/OTP gateway. Inter-agent messaging is governed by send_to/receive_from declarations, and cross-trust-boundary communication uses the Bandwidth-Constrained Protocol. See Agent Runtime for details on how sessions work.