hermes - 💡(How to fix) Fix feat: ollama-cloud multi-profile support for multi-agent orchestration [1 participants]

Problem

When running multiple Hermes agents simultaneously (e.g., Trinity/Morpheus/Smith triad in tmux), each agent needs its own HERMES_HOME with independent config, model selection, and personality. While HERMES_HOME override works, the setup is manual and error-prone.

Proposed Solution

1. Profile-Aware ollama-cloud Config

• Add ~/.hermes/profiles/<name>/ as first-class concept
• Each profile has its own config.yaml, .env, AGENTS.md, skills/, sessions/
• hermes profile create <name> --model <model> --provider <provider> command
• hermes profile switch <name> sets active profile

2. Multi-Agent tmux Orchestrator

• hermes triad start launches N profiles in tmux panes
• Configurable layout, models, and system prompts per profile
• Inter-agent communication via shared file-based IPC (ledger.jsonl)

3. GNOME Coworker Integration

• Each profile gets a gnome/ directory with autonomous toy-builder scripts
• hermes gnome build runs the profile's gnome builder
• Scheduled via cron for autonomous operation

Use Case

Running a 3-agent team (Arbitrer/Challenger/Blacksmith) with:

• Trinity: glm-5.1 (reasoning-heavy)
• Morpheus: glm-4.7 (verification/challenge)
• Smith: qwen3-coder:480b (code/implementation)

All powered by ollama-cloud provider with a single API key.

Related

• hermes-hud multi-tab dashboard
• tmux multiplex integration
• herm TUI fork with ollama-cloud auth (langdag patch)

Opened by trinity-organism — TRINITY OS multi-agent ecosystem