Skip to content

3xian/MarsBuild

Repository files navigation

MarsBuild

MarsBuild

Desktop mission control for Grok agents.

Screenshot · What it does · Quick start · Architecture · Roadmap

A desktop console for Grok Build: multi-task board, ACP timeline, workspace files/Git, permissions, and usage. It attaches to grok over ACP — it does not run its own agent loop.

Tauri 2 · React · TypeScript · Rust · current version 0.1.15

Screenshot

MarsBuild — tasks, Timeline, workspace

What it does

Area Behavior
Tasks Lists sessions under ~/.grok / %USERPROFILE%\.grok. New task, select, prompt, stop. First send auto-connects ACP (no attach toggle).
Timeline One stream: user / agent / thought / tool / shell / plan / events. Live ACP when connected; otherwise hydrate from session updates.jsonl. Filters + stick-to-bottom.
File changes Agent hunks from hunk_records.jsonl.
Raw Tail of on-disk ACP session/update records.
Workspace Project file tree + Git porcelain status (right rail).
Mode Grok Shift+Tab ring: Normal → Plan → Auto → Always-approve. Plan is orthogonal to permission (next free-text becomes /plan …). When the agent calls exit_plan_mode, MarsBuild shows a plan approval panel (Approve / Request changes / Quit) via Grok’s x.ai/exit_plan_mode reverse-RPC. /view-plan is local. Auto / Always-approve update the host ACP gate only (no session/prompt side effects).
Permissions Host gate also supports Accept edits and Don't ask (New Task spawn). Per-task prefs under ~/.marsbuild (permission + Plan arming).
Usage Week remaining (Grok billing API) + recent day token series from local sessions.
Updates Checks GitHub Releases on startup; optional download & install. Title bar shows MarsBuild <version>.

Prebuilt installers: Releases (Windows x64 NSIS, macOS Apple Silicon & Intel). Linux: build from source (no CI installer yet).

Quick start

1. Install Grok Build first

MarsBuild attaches to Grok Build over ACP — install the CLI before running MarsBuild.

Windows (PowerShell):

irm https://x.ai/cli/install.ps1 | iex

macOS / Linux / WSL:

curl -fsSL https://x.ai/cli/install.sh | bash

After install, the grok binary and data live under ~/.grok (or %USERPROFILE%\.grok / GROK_HOME on Windows).

2. Dev prerequisites

macOS Windows 11 Linux
Node 24+ 24+ 24+
Rust stable stable (x86_64-pc-windows-msvc) stable
Platform Xcode CLT MSVC Build Tools + WebView2 webkit2gtk (see Tauri docs)
Grok Build installed (step 1) installed (step 1) installed (step 1)

Windows toolchain (once):

winget install Microsoft.VisualStudio.2022.BuildTools --override "--wait --passive --norestart --add Microsoft.VisualStudio.Workload.VCTools --includeRecommended"
powershell -ExecutionPolicy Bypass -File scripts/windows-setup.ps1

3. Build and run MarsBuild

npm install
npm run tauri:dev          # development
npm run tauri:build        # local installer under src-tauri/target/release/bundle/
npm run check              # frontend + Rust (fmt/clippy/test) — same as CI

Env (optional)

Variable Meaning
GROK_BIN Path to grok / grok.exe
GROK_HOME Grok data root (default ~/.grok)
MARSBUILD_HOME MarsBuild prefs root (default ~/.marsbuild)

Architecture

UI (React)
  ├─ invoke()  →  sessions, spawn/attach/prompt/stop, permissions,
  │               week usage, token series, project FS, git status
  └─ listen()  ←  agent-update | agent-status | agent-permission
                    | agent-shell | agent-prompt-complete | sessions-changed
        │
        ├─► AgentManager — N × `grok agent stdio` (ACP) + permission gate
        └─► Session index — FS watch on ~/.grok/sessions, cards, hunks, stats

License

Copyright (c) 2026 david. All rights reserved. Published without an open-source license.

About

A desktop console for Grok Build: multi-task board, ACP timeline, workspace files/Git, permissions, and usage.

Topics

Resources

Stars

2 stars

Watchers

0 watching

Forks

Packages

 
 
 

Contributors