Current Project · Workspace-first Codex runtime

threadBridge

threadBridge is a workspace-first Codex runtime. The macOS desktop process is the owner, Telegram is an adapter, and the important work is keeping workspace, session, local TUI, and remote messages on the same maintainable continuity path.

Agent RuntimeRustTelegramLocal-first

Narrative

Design and engineering judgement

Product frame

The project handles real friction in agent use: starting work from Telegram, running it in a local workspace, knowing whether the session can continue, and recovering when runtime state drifts.

Engineering frame

The system combines a Rust desktop runtime owner, local management API, Telegram adapter, app-server observer, workspace runtime surface, and managed hcodex entrypoint.

Design frame

This is not a chatbot wrapper. It is interaction design for an agent runtime: setup, launch, reconnect, archive, repair, approval, plan mode, and final replies need to be legible and recoverable.

System

Components and visibility

Component Type Visibility Role
threadbridge_desktop macOS runtime owner Public repo Owns the local management API, tray menu, and runtime reconcile flow.
Telegram adapter Remote interaction surface Public repo Routes workspace-thread text, images, questions, and mode switches back to the saved Codex session.
Local management UI Browser / API surface Public repo Handles setup, launch, reconnect, archive/restore, runtime repair, and transcript inspection.
.threadbridge / hcodex Workspace runtime surface Public repo Installs managed entrypoints, state files, and local TUI continuation into real workspaces.
Release pipeline macOS distribution Public release Builds the universal app bundle, signing, notarization, DMG, and release candidates.

Public URLs

Public surfaces