Gormes

Phase 5 — The Final Purge

Phase 5 — The Final Purge (100% Go)

Status: ⏳ planned

Deliverable: Python tool scripts ported to Go or WASM. Python disappears entirely from the runtime path.

Phase 5 is when Python disappears entirely from the runtime path. Each sub-phase is a separable spec.

Phase 5 Sub-phase Outline

SubphaseStatusDeliverable
5.A — Tool Surface Port⏳ plannedPort the 61-tool tools/ registry. Most tools are tractable Go ports; a few (browser, voice) split into 5.C–5.E.
5.B — Sandboxing Backends⏳ plannedPort tools/environments/{local,docker,modal,daytona,singularity}.py + file_sync.py. Five execution backends with namespace isolation and container hardening.
5.C — Browser Automation⏳ plannedPort tools/browser_tool.py + tools/browser_camofox*.py + tools/browser_providers/{browserbase,browser_use,firecrawl}.py to Go (Chromedp, Rod) or sidecar process
5.D — Vision + Image Generation⏳ plannedPort tools/vision_tools.py + tools/image_generation_tool.py; multimodal in/out
5.E — TTS / Voice / Transcription⏳ plannedPort tools/{tts_tool,voice_mode,transcription_tools,neutts_synth}.py; may stay as sidecar processes
5.F — Skills System (Remaining)⏳ plannedPort remaining tools/{skill_manager_tool,skills_hub,skills_sync,skills_guard}.py + skill registries + 26 skill categories. Note: Core learning loop (skill extraction, improvement) is Phase 2.G (P0)
5.F.1 — Skills Hub Integration⏳ plannedPort skills.sh, clawhub, lobehub, hermes-index registries
5.F.2 — Skill Auto-Discovery⏳ plannedPort auto-generated skill discovery and metadata management
5.G — MCP Integration⏳ plannedPort tools/{mcp_tool,mcp_oauth,mcp_oauth_manager,managed_tool_gateway}.py; Model Context Protocol client + OAuth flows
5.H — ACP Integration⏳ plannedPort acp_adapter/ + acp_registry/; Agent Communication Protocol server side
5.I — Plugins Architecture⏳ plannedPort plugins/{context_engine,memory,example-dashboard} + the plugin SDK; let third parties extend Gormes without forking
5.J — Approval / Security Guards⏳ plannedPort tools/{approval,path_security,url_safety,tirith_security,website_policy}.py; gate dangerous actions
5.K — Code Execution⏳ plannedPort tools/code_execution_tool.py + tools/process_registry.py; sandboxed exec
5.L — File Ops + Patches⏳ plannedPort tools/{file_operations,file_tools,checkpoint_manager,patch_parser}.py; file editing with atomic checkpoints
5.M — Mixture of Agents⏳ plannedPort tools/mixture_of_agents_tool.py; multi-model coordination
5.N — Misc Operator Tools⏳ plannedPort tools/{todo_tool,clarify_tool,session_search_tool,send_message_tool,cronjob_tools,debug_helpers,interrupt}.py
5.O — Hermes CLI Parity⏳ plannedPort the 49-file hermes_cli/ tree (auth, backup, banner, codex_models, profiles, platforms, pairing, webhook, models, providers, runtime_provider, skills_hub, mcp_config, plugins, …); replaces the upstream hermes binary
5.P — Docker / Packaging⏳ plannedMirror Dockerfile + docker/{entrypoint.sh,SOUL.md} + packaging/homebrew + scripts/{install.sh,install.cmd,install.ps1,release.py,build_skills_index.py} for Gormes; OCI image with same volume layout as upstream
5.Q — TUI Gateway Streaming Surface⏳ plannedPort tui_gateway/ (2,931-line server.py + render.py, slash_worker.py, entry.py) + hermes_cli/skin_engine.py; SSE streaming to the existing Bubble Tea TUI (shipped Phase 1) so remote TUIs see live agent state

Relationship to Phase 6

Phase 5.F (Skills System port) is the mechanical work: porting the upstream Python skills plumbing. Phase 6 (The Learning Loop) is the algorithm on top — detecting complexity, distilling patterns, scoring feedback. Phase 5.F is a dependency of Phase 6, but they are not the same work.