The Problem
Developers who want an AI‑augmented coding experience directly in the terminal often face a choice between heavyweight IDE plugins or web‑based tools that require constant internet access. t1code brings the T3Code concept into a local, self‑hosted terminal UI, letting users run code‑generation and orchestration workflows without leaving the shell.
What This Does
t1code is a monorepo that bundles a desktop TUI (React‑based, apps/desktop/src/main.ts), a server backend (apps/server/src/index.ts), and a marketing site (apps/marketing/). The server provides orchestration layers for checkpointing, projection pipelines, and provider adapters (e.g., apps/server/src/provider/Layers/ClaudeAdapter.ts, apps/server/src/provider/Layers/CodexAdapter.ts). Integration tests live under apps/server/integration/, and the desktop UI consumes the server via a CLI script (apps/server/scripts/cli.ts). A turbo.jsonc at the root coordinates task pipelines across the three apps.
How To Use It
Setup git clone https://github.com/maria-rcks/t1code.git cd t1code bun install
The repo uses bun as the package manager; package.json files for apps/desktop, apps/marketing, and apps/server list dependencies without a lockfile (see “Code Health & Issues”).
Configuration
No .env or secret files are present in the structure. Environment‑specific keys (e.g., API tokens for Claude or Codex) would typically be placed in a .env at the project root or referenced in CI secrets; the repo supplies no default config beyond the tsconfig.json files and tsdown.config.ts.
Running it
Start the desktop TUI: bun dev:tui (as documented in README). Launch the server CLI: bun run start or invoke the CLI script apps/server/scripts/cli.ts. Global one‑liner (if published): bunx @maria_rcks/t1code.
Real‑World Use
A developer can open a terminal, run t1code, and ask the assistant to “refactor this function to use streaming I/O.” The request is routed through apps/server/src/orchestration/OrchestrationEngine.ts, which coordinates ProjectionPipeline and ProviderRuntimeIngestion layers, ultimately calling the selected adapter (ClaudeAdapter or CodexAdapter). The result appears inline in the TUI, and the developer can accept, edit, or reject the suggestion without leaving the shell.
Code Health & Issues
Low/Risk – Missing lockfile: apps/desktop/package.json lists dependencies without a pnpm-lockfile or bun.lockb, risking non‑reproducible builds. SDLC: 46 test files exist (e.g., apps/desktop/src/confirmDialog.test.ts, apps/server/src/orchestration/commandInvariants.test.ts), indicating decent coverage, but no CI workflow for lint/type‑check beyond the publish-npm.yml GitHub Actions file. Configuration hygiene: No .env or example env file is tracked; secrets would need to be injected externally. Separation of concerns: The monorepo splits UI, server, and marketing cleanly, yet shared types are minimal; some orchestration logic lives directly in apps/server/src/orchestration/ rather than a dedicated library.
The Bottom Line
t1code delivers a functional terminal‑first AI coding companion built on a React desktop UI and a Node/TS server with solid test coverage. The main trade‑off is the absent lockfile and limited out‑of‑the‑box configuration for API keys, making it best suited for teams comfortable managing their own dependency pins and environment secrets. Solo developers or small teams wanting a self‑hosted terminal assistant will find it usable with minimal setup, while larger organizations may need to add a lockfile and CI pipelines for reproducible, secure deployments.