Skillget

2code

agent
Guvenlik Denetimi
Basarisiz
Health Uyari
  • No license — Repository has no license file
  • Description — Repository has a description
  • Active repo — Last push 0 days ago
  • Low visibility — Only 5 GitHub stars
Code Basarisiz
  • spawnSync — Synchronous process spawning in e2e-tests/test/smoke.test.mjs
  • os.homedir — User home directory access in e2e-tests/test/smoke.test.mjs
  • process.env — Environment variable access in e2e-tests/test/smoke.test.mjs
  • network request — Outbound network request in e2e-tests/test/smoke.test.mjs
Permissions Gecti
  • Permissions — No dangerous permissions requested
Purpose:
A desktop workstation for vibe coding that integrates terminals, AI coding agents, and Git into a single interface, built on Tauri (Rust) and React with persistent terminals and worktree-based project management.

Security Assessment:
The tool is a terminal and Git manager, so shell execution is expected. All flagged issues (synchronous process spawning, home directory access, environment variable reads, and network requests) occur in the e2e smoke test file, not in the core application. No hardcoded secrets were detected, and no dangerous permissions are requested. Given the context that this is a desktop IDE-like tool that legitimately needs terminal access, the overall risk is Medium — it has broad local system access by design, but nothing looks malicious or out of scope.

Quality Assessment:
The project is actively maintained with a push within the last day. However, it is very early stage with only 5 GitHub stars and no license file, which is a concern for anyone wanting to use or contribute. The lack of a license means you technically have no legal right to use, modify, or distribute the code. The README is well-documented and the tech stack (Tauri 2, React 19, Rust, SQLite) is solid and modern.

Verdict:
Use with caution — promising and actively developed, but the missing license and early-stage maturity make it unsuitable for production or team adoption until licensing is clarified.
SUMMARY

The Vibe Coding Workstation — A desktop workspace where terminal, AI agents, and git live together for uninterrupted flow state

README.md

2code

Desktop software for vibe coding.

2code is a desktop workstation where terminals, AI coding agents, Git, and worktree-based project lanes live together. It is built for developers who want to stay inside one calm coding workspace instead of spreading a session across terminal windows, Git tools, editors, and agent panes.

2code is still early and under active construction. The current focus is macOS-first polish; Windows and Linux support are planned after the core workstation experience is solid.

Why 2code

AI-assisted development creates more parallel state than a normal coding session: long-running commands, multiple agents, branch experiments, diffs to review, and half-finished ideas that should not be lost when attention shifts.

2code treats that state as the primary interface. Terminals are persistent work surfaces, Git state stays close to the task, and each feature can live in its own isolated profile with its own worktree and terminal context.

Features

  • Persistent terminals: keep shell sessions, scrollback, and terminal layout close to where you left them.
  • Git visibility: review diffs, staged changes, history, and shipping state without leaving the workstation.
  • Worktree profiles: split features, bugfixes, and experiments into isolated lanes backed by Git worktrees.
  • Project management: organize local code projects and launch focused workspaces quickly.
  • PTY notifications: receive terminal-side notifications through the bundled helper pipeline.
  • Localized UI: i18n message sources live in messages/ and are generated into the frontend.

Tech Stack

  • Desktop shell: Tauri 2
  • Frontend: React 19, TypeScript, Vite
  • UI state: Zustand + Immer
  • Server state: TanStack Query
  • Backend: Rust workspace
  • Database: SQLite via Diesel migrations
  • Terminal runtime: integrated PTY service
  • Package manager: Bun

Getting Started

Prerequisites

  • macOS
  • Bun
  • Rust stable toolchain
  • Tauri 2 development prerequisites
  • just for helper commands

Install

bun install

Run the desktop app

bun tauri dev

Run only the frontend

bun run dev

Build

bun tauri build

Useful Commands

Command Description
bun tauri dev Run the full desktop app with frontend and Rust hot reload
bun run dev Run the Vite frontend only
bun tauri build Build the production desktop app
cd src-tauri && cargo test Run Rust tests
cargo tauri-typegen generate Regenerate frontend IPC bindings after Rust command changes
just build-helper Build the PTY helper sidecar in release mode
just build-helper-dev Build the PTY helper sidecar in debug mode
just fmt Format TypeScript and Rust
just coverage Generate Rust coverage report

Project Structure

2code/
├── src/                        # React + Vite frontend
│   ├── features/               # Feature-first app modules
│   ├── shared/                 # Shared lib, providers, components, hooks
│   ├── layout/                 # App shell and sidebar
│   ├── generated/              # Generated Tauri IPC bindings
│   └── paraglide/              # Generated i18n messages
├── src-tauri/
│   ├── src/handler/            # Tauri command entry points
│   ├── crates/infra/           # DB, PTY, Git, watcher, helper infrastructure
│   ├── crates/service/         # Business logic
│   ├── crates/repo/            # Diesel repositories
│   ├── crates/model/           # DTOs, Diesel models, error types
│   ├── bins/2code-helper/      # PTY notification helper sidecar
│   └── migrations/             # Embedded Diesel migrations
├── messages/                   # i18n source messages
└── justfile                    # Development helper commands

Development Notes

  • Add Tauri commands in src-tauri/src/handler/*.rs, register them in src-tauri/src/lib.rs, then run cargo tauri-typegen generate.
  • Consume IPC from src/generated/; do not hand-write frontend API clients for Tauri commands.
  • Use src/shared/lib/queryKeys.ts for TanStack Query keys.
  • Keep terminal components mounted. Terminal tab switching should hide inactive terminals with CSS instead of unmounting them.
  • Database access uses a single Arc<Mutex<SqliteConnection>>; keep lock scopes short and never hold the lock across await.
  • Diesel migrations in src-tauri/migrations/ are embedded and applied on startup.
  • Worktree profiles are created under ~/.2code/workspace/{id}.

Links

Yorumlar (0)

Sonuc bulunamadi