How does HELLO OS work with different models and existing tools?
DIRECT ANSWER
HELLO OS talks to tools through the Model Context Protocol: its MCP service exposes forge, cortex, memory and checkpoint tools plus read-only connectors for SQL, GitHub, OpenAPI and webhooks. Today a single configured LLM provider is used for golden-set replays. Routing work across model families and requiring cross-provider quorum for risky actions are vision.
Which decisions use a quorum today?
Debates use reputation-weighted votes between agents, with a quorum weight. A quorum that requires agreement between different model providers is not implemented.
Which integrations exist?
The integrations page lists every connector with its real status. Write-capable tools are disabled; connectors are read-only.
What exists in the repo
- IMPLEMENTEDMCP tool serviceTools listed live./api/hello/mcp/tools
- IMPLEMENTEDRead-only connectorsSQL, GitHub, OpenAPI, webhook./integrations
- IMPLEMENTEDReputation-weighted debatesQuorum by weight./ops/consensus
- PROTOTYPESingle-provider completionsUsed by golden-set replay.
- VISIONMulti-model routingNo routing across model families exists.
- VISIONCross-provider quorumNot implemented.