Skip to content
berthojorisPublic

About

No description, website, or topics provided.

Resources

Stars

1 star

Watchers

0 watching

Forks

Latest commit

 

History

45 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Vela

A Windows desktop terminal and Git worktree manager built with Rust, Tauri 2, React 19, and TypeScript.

Features

  • Native ConPTY terminals with persistent tab buffers and optional WebGL rendering.
  • PowerShell, CMD, Git Bash, WSL, and coding agent profiles that are listed only when installed.
  • Instant startup: the window is revealed as soon as the React workspace mounts, with no splash delay.
  • Single pane, vertical split, and horizontal split with independent keyboard focus.
  • Git worktree creation/removal, bounded unified diff previews, and commit of all changes.
  • Switchable Git / Files sidebar with a lazy-loading folder tree and VS Code-style file icons.
  • Tabbed code editor with syntax highlighting, line numbers, search, undo/redo, and Ctrl+S saving.
  • Inline errors, retryable launch forms, isolated terminal render failures, and local diagnostics.
  • Safe agent defaults: agent permission checks stay on, with one deliberate exception — the Claude Code preset launches with --dangerously-skip-permissions.
  • Each agent preset names the shell that hosts it. Droid CLI runs inside Git Bash, so the tools it drives use POSIX shell semantics instead of PowerShell; the other agents run inside Windows PowerShell. The launch dialog shows the host shell for the selected preset.

Vela launches CLI agents; it does not currently parse their task status, provide a security sandbox, or implement the Android Remote Companion. The PRDs describe future goals, not a list of shipped features.

Requirements

  • Windows 10/11 x64 with Microsoft Edge WebView2 Runtime.
  • Git 2.40+ available in PATH.
  • Installed shells/agents you intend to launch.
  • For development: Node.js 22.12+ or 24 LTS, stable Rust, and Visual Studio C++ build tools / Windows SDK.
npm ci
npm run tauri dev

npm run dev is a browser-only UI preview with mocked terminal and Git operations. It does not validate native PTY/Git behaviour.

Checks and release build

npm run lint
npm run format:check
npm test
npm run test:ui
npm run build
cd src-tauri
cargo fmt --check
cargo clippy --locked --all-targets -- -D warnings
cargo check --locked
cargo test --locked --lib
cd ..
npx @tauri-apps/cli build --no-bundle

Release executable: src-tauri/target/release/vela.exe. Bundling is disabled; this command does not create an installer. Close a running release copy before rebuilding it.

Windows installer (NSIS, x64)

Bundling is off in src-tauri/tauri.conf.json; the installer is produced with a config override:

# 1. bump the version in all 5 files: src-tauri/tauri.conf.json, src-tauri/Cargo.toml,
#    src-tauri/Cargo.lock, package.json, package-lock.json  (see AGENTS.md)
# 2. run the checks above
npx @tauri-apps/cli build --config src-tauri/tauri.bundle.json

Output: src-tauri/target/release/bundle/nsis/Vela_<version>_x64-setup.exe (installs to %LOCALAPPDATA%\Vela\, per-user, no admin required). Run the new installer over the existing install to upgrade — the version bump is what makes the installer take the upgrade path instead of the reinstall path.

The Windows CI workflow runs frontend lint/format checks/tests/build, Rust fmt/clippy/checks/tests, and the release build. Rust tests include real temporary Git worktree/diff/commit/remove operations and real Windows ConPTY input/output, natural exit, and shutdown. Frontend tests cover stale requests, duplicate submissions, launch retry, split focus, output acknowledgements, input limits, and directory metadata.

npm run test:ui uses an installed Microsoft Edge in an isolated headless profile. It checks the browser-preview workspace at 1280×820 and 800×550, including real xterm layout, split focus, modal shortcuts, and recoverable errors. This does not replace interactive testing in the native WebView2 window. The test runner starts/stops its own Vite server; port 1420 must be free.

Safety and recovery

File Explorer and editor

Click Open Files (above Open Dir) to browse the active terminal directory, or choose a folder when there is no active directory. Expand folders with a single click; double-click a file (or press Enter) to edit it on the right. Git / Files switches the sidebar; Terminal / Editor switches the workspace without stopping terminals or discarding edits. Open Dir still opens Windows File Explorer.

The editor supports UTF-8 text files up to 2 MiB and 20 open tabs. LF/CRLF and UTF-8 BOM are preserved; binary files, other encodings, and mixed/legacy line endings are refused. Folder listings are capped at 5,000 entries; Git metadata and links outside the Explorer root are excluded. Filesystem permissions still apply.

Save with Ctrl+S or the Save button. Unsaved tabs show a dot, and closing a dirty tab or the native window asks whether to save, discard, or cancel. If the disk content changed since opening/saving, Vela refuses to overwrite it and keeps your edits. Copy your edits before discarding and reopening to resolve a conflict. Files are replaced through a temporary sibling file rather than truncated in place. Open tabs and unsaved drafts are restored after restarting Vela; see Workspace recovery below. The browser-only preview cannot read or save real files.

Workspace recovery

Vela stores terminal tab order, titles, directories, split layout/focus, open editor tabs, the selected workspace view, and the Files sidebar context in local WebView2 IndexedDB. Only dirty files need a text backup; clean files are read again from disk. Drafts keep their original revision and saved text, so a changed or missing disk file never silently replaces recovered edits. Explicit Don't Save removes the discarded draft from recovery too.

Recovery writes run after 500 ms of inactivity, or every 2 seconds during continuous editing, with at most one active write and one newer snapshot queued. The app's close command waits for pending recovery data. A crash or forced process termination can still lose the last unsnapshotted edits; this is recovery, not a replacement for Ctrl+S. Storage errors are reported in the workspace. Recovery data stays on this machine and includes file paths and unsaved source text.

Terminal recovery starts fresh shells, using installed plain-shell profiles and falling back to the default installed shell if the original is unavailable. It does not restore scrollback, running programs, or execute saved commands. Agent tabs return as labelled shells so you can relaunch the agent deliberately. Failed directory/shell restores report an error without preventing other tabs or drafts from opening. A first launch with no saved workspace remains empty.

Git and terminal operations

  • A worktree separates Git files, not filesystem permissions. Agents run with your user privileges and their normal permission prompts.
  • Commit includes every tracked and unignored untracked change via git add -A. There is no file selection or automatic push.
  • Failed commits may leave changes staged. Timed-out write operations must be checked with git status / git log before retrying. Vela never automatically retries a Git write.
  • The diff modal keeps its target fixed during a commit. A refresh failure after a successful commit is reported separately.
  • Per-file rollback restores both sides of a detected rename. Paths with multiple Git status entries cannot be rolled back individually; resolve them in the terminal or explicitly review Reset All. Git status failures are shown as unavailable, never as clean.
  • Worktree removal requires confirmation, refuses active terminal directories in the UI, and lets Git protect dirty worktrees. The main worktree cannot be removed.
  • App close is blocked while an in-process Git write is running. On exit, Vela terminates its terminal process trees; it does not terminate external terminals.
  • A failed terminal can be closed without losing the rest of the workspace. After restart, terminal tabs reopen as fresh installed shells in their saved directories; agent commands and process state are not replayed.

Local diagnostics: %LOCALAPPDATA%/Vela/logs/errors.log, rotated at roughly 256 KiB with one previous file. Logs contain error details and may contain paths; terminal streams are not logged and diagnostics are not uploaded.

Resource bounds and performance

  • Maximum 32 terminal tabs; each has 5,000 lines of scrollback.
  • PTY output remains Tauri events, with a 64 KiB unacknowledged byte window per session. Credits return only after xterm consumes the output. A stalled renderer is stopped after a 60 second deadline.
  • Ordered input is chunked without splitting Unicode surrogate pairs. Pastes above 262,144 UTF-16 code units are refused rather than queued indefinitely.
  • Git command output and execution duration are bounded. Most reads time out at 30 seconds; writes at 120 seconds; agent version probes at 5 seconds.
  • Review supports up to 500 changed files. Batch patches are capped at 8 MiB, per-file previews at about 32 KiB, and total text previews at about 2 MiB plus explanatory notices. Truncated/unavailable previews must be inspected in a terminal before committing.
  • The terminal and GPU renderer load separately from the initial app shell. Startup no longer waits for a decorative splash.

RAM, cold-start, and FPS numbers in earlier PRDs are targets, not verified benchmarks. Production acceptance still requires interactive WebView2/agent testing and sustained-load profiling on the deployment machines.

Directory tracking

PowerShell, CMD, and standard Git Bash profiles report prompt directories through OSC 7; the active repository follows supported directory changes. PowerShell preserves the original prompt, and PowerShell-hosted agent presets install the same integration before launching the agent. Git Bash-hosted agent presets report the directory through PROMPT_COMMAND; the shell that replaces the agent when it exits keeps reporting, so the repository still follows later cd commands. Custom prompt scripts can override shell integration; custom -File/encoded-command launches are not rewritten. Unmapped Linux paths from WSL/custom shells cannot be interpreted as Windows Git paths; those sessions retain their launch context until a compatible directory report is available. The WSL profile inherits the selected working directory; WSL translates Windows checkout paths to their Linux mount paths (for example, C:/Projects/app becomes /mnt/c/Projects/app with the default mount configuration).

Shortcuts

Shortcut Action
Ctrl+T Open terminal launch dialog
Ctrl+W Close focused terminal tab, or active file in Editor
Ctrl+S Save the active file in Editor
Ctrl+F in editor Find text in the active file
Ctrl+F in terminal Find text in the focused terminal
Ctrl+= / Ctrl+- / Ctrl+0 Zoom terminal font in / out / reset
Ctrl+Tab / Ctrl+Shift+Tab Next / previous terminal tab
Ctrl+1 … Ctrl+9 Jump to terminal tab by position
Drag a tab Reorder terminal tabs
Double click tab Rename tab
Double click titlebar Maximize / restore
Escape Close a dialog when no operation is pending
Ctrl+Enter in commit input Commit reviewed worktree

Global tab shortcuts are suspended while a modal dialog is open.

About

No description, website, or topics provided.

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages