# Harness Studio **A desktop coding agent for macOS and Linux. Any model, on your code and UI.** [Download for macOS](https://github.com/vigneshv1cky/harness-studio/releases/latest) · [Download for Linux](https://github.com/vigneshv1cky/harness-studio/releases/latest) · [What's new](CHANGELOG.md) ![Harness Studio in light mode: the sidebar, a conversation where the agent found a SpaceX Starship video on YouTube and skipped its ad, the Browser pane playing the video, and the Session pane with changes and usage](docs/screenshots/app-light.png) ![The same window in dark mode](docs/screenshots/app-dark.png) Harness Studio is a desktop app that works like Claude Code desktop, with whichever model provider you have an API key for. Download it, choose a model, open a project folder and ask. ## What it does - **Point at your UI, tell the agent what to change.** Open your app's dev server in the Browser pane, pick an element, and say "make this bigger": the agent gets the element's **source file and line**, component, text, styles and HTML. - **A browser the agent can use:** it opens pages, reads them, clicks and types in the Browser pane, next to the conversation, with real mouse and keyboard input. In the desktop app it also reads what DevTools shows on your own development pages (localhost and your local network): console errors with stack traces, network requests with their status, and response bodies. It never attaches DevTools to public sites. - **Documents, decks and spreadsheets:** the agent writes PowerPoint, Word and Excel files, with editable charts in decks and spreadsheets, renders slides to check its own layout, and exports PDF, using a Python, Node and office converter bundled with the app, so nothing needs installing. Results open in the side pane's preview. - **Design boards:** ask the agent to design or mock up screens and it drafts them on one board, each screen and variant side by side at phone, tablet and desktop widths, using your project's own colours and fonts, before any app code changes. The board is a single HTML file with pan and zoom that opens in the preview pane or any browser. - **Desktop and mobile apps:** the agent builds Mac, Android and Linux desktop apps (and iPhone apps when Xcode is installed) inside its sandbox, keeping every tool's downloads in the project, then runs them and checks them: Mac apps through computer use, Android apps in a headless emulator with its screenshots, and web-based ones in the Browser pane. - **Live dashboards:** ask for a dashboard and the agent builds a page of charts with a small refresh script per data source (a spreadsheet, CSV, a database or warehouse through your own login, or a web API). The Dashboards pane fetches fresh data every time you open it, once you have approved the refresh scripts at their exact text; **Keep fresh** refreshes it while closed, and **Save snapshot** gives you one HTML file with today's data to send. - **Charts, icons and diagrams:** editable charts inside PowerPoint and Excel files, and SVG files for standalone charts, icon sets and flow or architecture diagrams, drawn from your data with nothing to install. - **Speech to text, on this computer:** the microphone button between the model picker and Send dictates into your message (a menu in the recording bar picks the language), and the agent can transcribe an audio or video file, or a part you marked in the Files tab, with the time each piece was said, in Chinese, English, Cantonese, Japanese or Korean. Recognition is Harness's local SenseVoice model (about 241 MB, downloaded once after you agree); no audio leaves the computer. When the agent needs ffmpeg and you have none, it asks once and downloads a pinned, checksum-checked build into Harness Studio's data folder. - **Full-screen programs:** the agent can run vim, less, top, interactive prompts and installers in a real terminal, read the screen and type into it, under the same sandbox as every other command. - **Edit files yourself:** press Edit on a file in the Files tab for a code editor with syntax colours and ⌘S; the agent's changes appear in place, and neither of you overwrites the other's unsaved work. - **Side panes:** Files, Changes, Session details, Browser and Terminal, stacked with a draggable divider. - **Git history:** a Git page in the sidebar shows every workspace's branch, upstream and uncommitted files, and each workspace's commits with a branch graph, search by message, author or changed code, every commit's files and diffs, and blame. Its Branch menu switches branches when nothing is uncommitted. - **Connectors:** add MCP servers by URL or command, with OAuth sign-in and per-session on/off. - **Separate sessions:** the agent can hand a piece of work to a new session in the sidebar with a written brief, optionally in its own git worktree, and gets that session's report back. For a self-contained job whose material is not needed afterwards, such as judging a batch of rendered frames, it uses a helper agent and keeps only the verdict. - **Watches:** the agent (or you, from the eye button in the session header) can watch a command's output, a port or files; the checks run on your computer without the model, and the agent is woken with a short notice only when something changes. - **Remember:** when you correct the agent or ask it to remember something, it proposes a one-line note; you approve it and choose this project or all your projects, and it's saved as a line in an instruction file you can edit. - **Your own Chrome:** an optional paired extension lets the agent browse in your real Chrome, where you are signed in, and lets you pick elements on any page with ⌥⇧S. - **A calmer look:** Claude Code–like density, text sizes, sidebar and zoom. - **Secret files stay out of reach:** commands the agent runs, and its file tools, cannot read your SSH keys, cloud and registry credentials, password files, `.env` files outside the project, or the app's own API keys, so a prompt injection in a README or web page cannot make the agent send them anywhere. What the agent can still send, and where, is spelled out in the app's About page under Safety model. - **Command rules, like Claude Code's:** block a tool call or ask first, for example never `curl`, ask before `git push`, never read `./.env`, in Claude Code's `permissions` format, in `~/.harness-studio/permissions.json` or a project's `.harness-studio/permissions.json`. - **No account, no telemetry:** there is no sign-in and no usage reporting, and your API keys are stored only on your machine and sent only to the provider they belong to. Harness Studio is built on [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness), the open-source, any-model agent app. It is an independent project, not affiliated with or endorsed by DeepSeek or Anthropic; their names are used only to describe compatibility and inspiration. ## Screenshots **Dark mode, with a reply that cites files and code from the project:** ![A dark-mode conversation where the agent describes the project's files in a table and quotes the form handler from app.js](docs/screenshots/compact-density.png) **Files pane:** the project's tree beside open files with line numbers and syntax colours. Type `?` in the filter to search inside files. ![The Files pane with the project tree on the left and index.html open on the right](docs/screenshots/files-pane.png) **Changes pane:** the working tree against its branch, with per-file counts and coloured diffs. ![The Changes pane showing edits to README.md, app.js and styles.css](docs/screenshots/changes-pane.png) **Separate sessions:** the agent proposes handing a task to a new session with its own git worktree, and you start it or keep the work in this session. ![A New session card with the task's title, brief, worktree and branch, and Do it here and Start buttons](docs/screenshots/sessions-card.png) **Connectors:** MCP servers such as GitHub and the Chrome extension, each with its status and tool count, added by URL or command. ![Settings → Connectors listing GitHub with 49 tools and the Chrome extension with 9 tools, both connected](docs/screenshots/connectors-page.png) **The `+` menu:** files, goals, plan mode, commands and per-session connectors in a compact popover above the message box. ![The + menu with File, Goal and Plan under Add, and Compact, Permission, Model, Export, preview-select and Connectors under Commands](docs/screenshots/connectors-menu.png) **Session pane:** the session's changes and its usage at a glance. ![The Session pane's Changes card with +4 −2 across 3 files, and a Usage card with turns, steps, speed, tokens, cache hit and context used](docs/screenshots/session-usage.png) **Automation tasks:** ask for a follow-up later, and the agent schedules it and replies in the same session when it fires. ![A conversation where the agent schedules a one-time follow-up for a minute later, then replies when the automation task fires](docs/screenshots/automation-task.png) ## Status Developer preview, version 0.3.4, built on Harness `0.2.1-rc.2` through Harness Studio's fork of it, [harness-studio-core](https://github.com/vigneshv1cky/harness-studio-core) (pinned in [docs/HARNESS_PIN.md](docs/HARNESS_PIN.md)). Tested on macOS (Apple Silicon) and Linux (x64 and arm64). Windows isn't available yet. Planned, not yet built: - **A full design canvas**, like Claude Design: frames you drag and resize by hand, comments, and a design-system library. Until then, design boards (above) cover drafting and comparing screens; you change them by asking. - **Image generation.** The agent has no image model yet, so it can only draw graphics through code (SVG, HTML or the bundled Python image library). - **Slide and document templates**: a gallery of ready-made deck and document designs. For now the agent styles each file from scratch. - **Video making, as a separate app.** Animated videos and 3D product shots made as code (with Remotion) were tried in Harness Studio and taken out: rendering needs a 1 GB install and much of an 8 GB machine's memory. They are planned as their own app built from the same fork, so Harness Studio stays light. Video and audio files still play in Files and the preview, where you can mark a part for the agent. ## Setup ### 1. Install Harness Studio Harness Studio is a ready-to-run desktop app with the plugins built in, so you don't need DeepSeek Harness, Node.js or a build. Download it from the [Releases page](https://github.com/vigneshv1cky/harness-studio/releases): - **macOS (Apple Silicon):** a `.dmg`; drag Harness Studio to Applications. - **Linux (x64, arm64):** an AppImage for most distributions, or a `.deb` for Debian and Ubuntu (`sudo apt install ./harness-studio__amd64.deb`). Windows isn't available yet. How each app is built, and what to know before installing on Linux, is in [desktop/README.md](desktop/README.md). #### First launch on macOS The Mac app isn't signed or notarised by Apple, so macOS blocks it the first time. Allow it once: 1. Open the `.dmg` and drag **Harness Studio** to **Applications**. 2. Open Harness Studio. macOS says it "cannot verify" the app; click **Done** (not Move to Trash). 3. Go to **System Settings → Privacy & Security**, scroll to **Security**, and click **Open Anyway** next to the Harness Studio message. 4. Confirm with **Open Anyway** and your password or Touch ID. After that it opens normally. If macOS instead says the app "is damaged and can't be opened", the download's quarantine flag is the cause, not a broken file; clear it and open the app again: ```sh xattr -dr com.apple.quarantine "/Applications/Harness Studio.app" ``` To check the download first, compare `shasum -a 256 Harness-Studio--mac-arm64.dmg` with the `.sha256` file published next to it. ### 2. Choose a model On first launch, click **Choose a model provider** and add an API key for any provider in Settings → Models. The welcome window: the Harness Studio mark, Welcome to Harness Studio, Any model, on your code and UI, and a Choose a model provider button **Chrome extension (optional):** follow [chrome-bridge/README.md](chrome-bridge/README.md) to load the extension and add its connector, so the agent can use your own Chrome. ### 3. Optional: prepare your app for picking (development only) The companion script and source loader come from this repository: `git clone https://github.com/vigneshv1cky/harness-studio.git`, then run the commands below from its folder. **a. Companion script** — copy it into your app and load it only in development. ```sh cp plugins/devpreview-companion/companion.js /path/to/your-app/public/devpreview-companion.js ``` Next.js App Router, in `app/layout.tsx` (inside ``): ```tsx import Script from "next/script"; {process.env.NODE_ENV === "development" && ( ` in development pages only. **b. Source locations (Next.js 16 / Turbopack)** — install the loader and add the rule. ```sh npm install --save-dev /path/to/harness-studio/plugins/devpreview-source-loader ``` ```ts // next.config.ts const nextConfig: NextConfig = { allowedDevOrigins: ["127.0.0.1"], // only needed if you open the dev server as 127.0.0.1 turbopack: { rules: { "*.{jsx,tsx}": { condition: { all: ["development", { not: "foreign" }] }, loaders: [{ loader: "devpreview-source-loader", options: { root: process.cwd() } }], // no `as` — it would rename modules and break relative imports }, }, }, }; ``` Without the loader, Pick still works; the agent locates the element from its text, selector and component names instead of an exact line. ### 4. Use it 1. Start your dev server (`npm run dev`). 2. In Harness Studio, set the Session's **workspace to your app's folder** (so the agent can edit without extra approvals and paths match the stamps). 3. Click the **Browser** icon in the conversation header and open your dev server: type `localhost:3000`, or pick it from the **Dev servers** menu in the pane header. 4. Click **Pick** (the arrow) in the bar at the bottom of the browser, hover, click an element. The card shows its source, text, size, selector and styles. 5. Click **Send to agent** — a reference like `[Selected