Overview

T3op: T3 Code, OMP-only & Web-only

Welcome to the technical knowledge base for T3op (D-132), delivering a web-only and OMP-only deployment of the T3 Code agent-coding interface on the loca.zone infrastructure.

Mission Objective

T3op vendors the open-source T3 Code interface from upstream (pingdotgg/t3code), strips all non-OMP agent adapters (Codex, Claude Code, and external cloud provider SDKs) along with desktop/Electron wrappers, and connects directly to the host’s native omp engine (~/.local/bin/omp).

graph TD
    Browser[Browser Client: t3op.loca.zone] -->|HTTP / WebSocket| Nginx[Nginx Reverse Proxy]
    Nginx -->|Proxy Pass :7531| NodeApp[T3op Web App / Node Server]
    NodeApp -->|Process / stdio stream| OMP[Host OMP 18.2.6]
    NodeApp -->|Disk Persistence| Storage[(data/sessions/)]
    Wiki[wiki.t3op.loca.zone] -->|Static Quartz v5| Nginx

Architectural Highlights

• Web-First & Native: Completely stripped of Electron/Tauri shells, running as a standard web application accessible over HTTPS.
• OMP-Exclusively: Binds directly to the local Oh My Pi (omp) CLI/daemon on the host host, utilizing streaming turns and live tool execution cards.
• Self-Contained: Session records stored locally on disk under data/sessions/; zero reliance on third-party CDNs, foreign agent APIs, or tracking analytics.
• Production Routing: Served via user-level systemd unit (t3op.service) bound to loopback port 7531, fronted by nginx with Let’s Encrypt TLS certificates.

Wiki Sections

• Upstream & Licence: Pinned commit provenance, upstream repository details, licensing, and survey of prior seats.
• Architecture: Component breakdown, stripping audit, and OMP backend integration seam analysis.
• Execution Plan: The phased engineering plan and deliverables ledger.
• Progress Log: Real-time log of actions, verification receipts, and deployment milestones.
• Verification: Automated validation criteria, headless Chrome browser proofs, and system audit logs.