Croft
#croft
A VS Code style three pane workspace that runs entirely inside your terminal. Written in Rust, shipped as a single static binary.
#Tenets
The non-negotiables behind every decision in croft:
- Speed is a must. Every feature is weighed against its cost on the hot path before it lands.
- Low latency is non-negotiable. Keystrokes and clicks register instantly; rendering is coalesced so a noisy shell can never starve input.
- Local and remote parity always binds. Behaviour on your Mac and on a Linux box over SSH is identical. There is no second-class remote mode.
- The gap between terminal and GUI stays minimal. croft should look and feel like VS Code, down to the icons and motion.
- Everything has a shortcut. Every action is reachable from the keyboard, and no menu item ships without an accelerator.
- Correctness beats workarounds. Bugs are fixed at the root, never papered over with a fallback or a downgrade.
- One binary, no ceremony. Features are emulated in process rather than bolted on, so there is nothing to wire up after you install.
#Layout
Three panes in the VS Code arrangement: an Explorer sidebar on the left, a code editor top right, and a panel bottom right with PROBLEMS, OUTPUT, TERMINAL, CAPTURES, and PORTS tabs. An activity bar down the far left switches the sidebar between Explorer, Search, Source Control, Remote (SSH), Run and Debug, Extensions, and Testing, and holds the theme picker. Every seam drags to resize, and a Customize Layout popup mirrors VS Code's title-bar controls.
The essentials are all there: full LSP editing (completion, hover, go-to-definition, rename, quick fixes, inlay hints) with tree-sitter highlighting, multi-cursor, minimap, git gutter, inline blame, and an optional vim mode; a real terminal with shell integration, splits, triggers, copy mode, and durable command history; Source Control with hunk staging and a commit graph; a Test Explorer; a zero-config task runner; and debugging for Python, JavaScript/TypeScript, Rust, C, and C++ over DAP.
See LAYOUT.md for the pane-by-pane reference: every editor, terminal, Source Control, Testing, and status-bar feature, the debugging workflow, and language-server setup.
#Requirements
| Requirement | Why |
|---|---|
| macOS, Linux, or Android (Termux) | The PTY layer is POSIX. On Windows, run the Linux build inside WSL2; see WINDOWS.md. |
| Rust 1.85+ stable | To compile the binary (edition 2024). |
| A Nerd Font as your terminal font | File and activity-bar icons are Nerd Font glyphs; without one they render as [?] boxes. |
| A 256 color or truecolor terminal | Terminal.app, iTerm2, Alacritty, kitty, WezTerm, and Ghostty all qualify. |
| iTerm2, WezTerm, Ghostty, kitty, or a sixel terminal (optional) | Inline image / PDF / spreadsheet previews. Elsewhere croft shows a metadata header line. |
pdftoppm from poppler-utils (optional) |
Multi-page PDF preview with clickable links. Without it, page 1 only on macOS via sips. |
| Node.js + npm (optional) | TypeScript / JavaScript LSP; croft auto-installs the vtsls server on first use. |
Per-platform setup (Nerd Font, terminal keybindings, optional dependencies) lives in the platform guides.
#Install Rust
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
Then open a new terminal — or run . "$HOME/.cargo/env" in the current one — so cargo is on PATH.
#Install
Prebuilt binaries, no toolchain and no compile:
cargo binstall croft-software
cargo binstall itself needs installing once (cargo install cargo-binstall,
or a prebuilt from its releases).
That downloads the tagged release for your platform (macOS arm64/x86_64, Linux
musl arm64/x86_64) and puts croft on PATH in seconds.
Every release also carries a SHA256SUMS covering all four archives, so a
download can be verified independently. It lists every archive, so check only
the one you fetched rather than running it whole:
grep "croft-aarch64-apple-darwin.tar.gz" SHA256SUMS | sha256sum -c - # macOS: grep "..." SHA256SUMS | shasum -a 256 -c -
To build from source instead:
cargo install croft-software --locked
This compiles the latest crates.io release into ~/.cargo/bin/croft. Re-run to upgrade. To track main instead:
cargo install --git https://github.com/vitali87/croft.git --locked
Or to build from a source checkout:
git clone https://github.com/vitali87/croft.git cd croft cargo build --release && cargo install --path . --locked
macOS: the build directory churns the Spotlight index and can spike your CPU and fans. Before building, point Cargo at a .noindex directory Spotlight ignores; see MACOS.md.
#Run
croft # opens the current directory croft ~/projects # opens a specific folder croft ~/proj --open-file a.rs # opens a folder with a file already open croft ~/proj --open-file a.rs --zen # ...focused on just the file (no sidebar/terminal) croft remote <host> # launch croft over SSH on a Linux server (host from ~/.ssh/config) croft attach # open the current folder as a persistent session (survives closing the window) croft attach ~/projects # ...for a specific folder croft attach --solo ~/projects # join a shared folder in your own viewport (live co-editing) croft ls # list running persistent sessions croft view report.pdf # from any pane: open a file in the croft you are sitting in cat data.csv | croft view - # ...or pipe it in (staged to ~/.cache/croft, 0600, swept at the next launch once a day old) croft theme-import theme.json # use a VS Code colour theme in croft croft theme-import dracula-theme.theme-dracula # ...or fetch one from the marketplace croft --help
croft remote <host> installs itself on the box on first connect with no manual prep, and a stock cloud image works as-is. See LINUX.md for how the cross-compile and host provisioning work.
#Collaboration
croft attach keeps a session alive after you close the window, and lets other people join it.
Add --solo and each participant gets an independent viewport on the same files, live. An AI can
take a seat too, either as an MCP guest or as a resident pair-programming navigator croft hosts
itself (croft pair), local open-weight models included.
See COLLABORATION.md for the full guide.
#Platform setup
croft runs on macOS, Linux, Android, and Windows (via WSL2). The cross-platform basics are above; each platform has a short guide for its Nerd Font, terminal keybindings, and optional dependencies:
- macOS — Nerd Font for Terminal.app, and
croft setup-iterm2/croft setup-ghosttyto deliver theCmdchords that macOS otherwise reserves for menus. - Linux —
Ctrlas the command modifier, Nerd Font and poppler-utils, language servers, and thecroft remote <host>cross-compile / provisioning flow. - Android (Termux) —
Ctrlas the command modifier,pkg-based dependencies, the auto-installed activity-bar font, and the built-in on-screen keyboard for touch. - Windows (WSL2) — run the Linux build inside WSL2, hosted in WezTerm for the full icon/image UI; why native PowerShell / conhost is not supported.
#Keybindings
Every action is reachable from the keyboard; press F1 inside croft for the full reference. The complete tables (global, Explorer, Search, editor, vim mode, previews, terminal) live in KEYBINDINGS.md. The command modifier is Cmd on macOS and Ctrl on Linux / Android; the platform guides cover getting Cmd chords through your terminal.
#Goal
A complete VS Code replacement in the terminal: the full IDE experience as a single fast Rust binary. Everything VS Code does, croft will do, without leaving the TUI.
Maintainers and developers: see ARCHITECTURE.md for the project layout and internals, and CONTRIBUTING.md for the developer workflow (including keeping target/ from filling your disk).
#License
MIT.