Skip to content

About

Welcome, to my own personal IDE, Atomic Code!

Resources

Stars

1 star

Watchers

0 watching

Forks

Latest commit

 

History

4 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Atomic Code (AC) — V0.1

A personal, keyboard-first IDE. Rust + Tauri backend, React + TypeScript frontend. See docs/vision.md, docs/architecture.md, and docs/roadmap.md for the why, the how, and the what's-next.

Atomic Code screenshot placeholder

What works right now

  • Open a folder as a workspace and browse it in a real file tree
  • Open, edit, and save text files (Monaco — the same editor engine as VS Code)
  • A real, PTY-backed terminal (not a fake/simulated one — it runs your actual shell), with support for multiple concurrent terminal tabs
  • Run arbitrary commands (e.g. compile and run a C++ file) with streamed stdout/stderr
  • A live system monitor: CPU (total + per-core), memory, load average, and a top-processes table, pushed from the backend once a second
  • Workspace file changes made outside the IDE are picked up automatically (filesystem watcher)

Prerequisites

  • Rust 1.75+ (1.80+ recommended) — https://rustup.rs
  • Node.js 18+ and npm
  • Platform build tools for Tauri:
    • Windows (primary target): the "Desktop development with C++" workload from Visual Studio Build Tools, plus WebView2 (preinstalled on modern Windows).
    • Linux: libwebkit2gtk-4.1-dev, libgtk-3-dev, libayatana-appindicator3-dev, librsvg2-dev, build-essential.
    • macOS: Xcode Command Line Tools.

See https://tauri.app/v1/guides/getting-started/prerequisites for the authoritative, OS-specific list.

Running in development

# from the repo root
npm install --prefix frontend
cargo install tauri-cli --version "^1"   # once, globally
cd backend
cargo tauri dev

cargo tauri dev starts the Vite dev server and opens the app window, with hot reload for the frontend and automatic rebuild for the backend.

Building a release binary

cd backend
cargo tauri build

Output lands in backend/target/release/bundle/.

Verifying without a GUI

If you just want to confirm the Rust backend compiles (e.g. in CI or a headless environment), cargo check from backend/ is enough and doesn't require a display. This entire project was built and type/link-verified this way — including a full cargo build that produced a real linked binary — inside a Linux sandbox with no GUI available.

Project layout

frontend/   React + TypeScript UI (Vite)
backend/    Rust + Tauri backend — filesystem, terminal, process, system
docs/       vision.md, architecture.md, roadmap.md

See docs/architecture.md for the module-by-module breakdown and the IPC contract between frontend and backend.

About

Welcome, to my own personal IDE, Atomic Code!

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages