What Is Zide? The Agentic Developer Desktop, the Plan Gates, and the Vendor Claims to Verify

One-line job: Decide whether Zide belongs in your development setup, and what it will and won’t do before you install it. Audience: Developers evaluating agentic coding tools. Not for: People looking for a review of Zed (zed.dev) or IBM zIDE, different products. Last verified: 2026-08-24 Evidence weight: documentation-verified

First, a disambiguation: this article is about Zide from Zide Software, the “Agentic Desktop for Developers.” It is not Zed (zed.dev), the editor; not josephschmitt/zide, the Zellij layout tool; and not IBM’s zIDE for z/OS. The name is crowded. If you came here from a GitHub search, check the URL.

What it is

Zide is a native desktop application that puts code editing, Git, issues, pull/merge requests, CI, terminals, worktrees, and an AI agent in one window, working against GitHub, GitLab, and Bitbucket. It’s built with Tauri and Rust, which is why the installers are small, the macOS build is 24.3 MB, the Windows x64 installer 17 MB (zide.dev/download).

The vendor’s own framing is explicitly anti-editor: “Not another editor with a chat box.” The claim is that most AI coding tools bolt an assistant onto an editor, while the actual work of AI-assisted development happens around the code, reviewing diffs, guiding the agent, running tests, deciding what ships. Founder Jim Bourke (also founder of Knife Edge Software) puts it as: “We built Zide because the real work of AI-assisted development isn’t writing code, it’s managing the entire workflow around it: reviewing, guiding, testing, deciding what ships.”

That’s vendor positioning, stated on day one of a beta with no independent reviews yet. Treat it as a claim, not a verdict. But the feature list backs the shape of it: the six-step loop Zide describes is issue triage → agent works in the repo → diff review → hunk staging and commit → PR/MR → CI watch, all visible in one window (zide.dev/features).

One important boundary: Zide is closed-source proprietary software. Bug reports and discussions are open on GitHub, but code contributions are not accepted.

What you actually get

The editor

LSP-powered diagnostics, hover, go-to-definition, and symbol search for Rust, TypeScript, JavaScript, Python, Go, Bash, HTML, CSS, and JSON. Multi-cursor, folding, minimap, EditorConfig support. Git-aware editing with inline hunk indicators, staging from the gutter, blame, file history, and conflict navigation. Previews for Markdown, HTML, SVG, CSV, images, and more.

Zide Assist, the repo-level agent

The agent reads files you give it, edits them, runs commands, and returns reviewable diffs rather than silently rewriting your tree. Notable mechanics:

• Plan mode, investigate-only mode where the agent can’t edit or run anything until you turn it off.
• Crosscheck, a second model automatically reviews every Assist commit and posts findings grouped by severity; one click sends findings back to the agent as a new request.
• Fork to Worktree, branch from any message in the conversation into a fresh git worktree and continue exploring there.
• Rollback, rewinds the conversation only. Per the docs, it does not revert files or git state; undo repo work through the Git surfaces.
• Automatic context, every prompt includes repo/worktree identity, your open tabs and pane focus, and recent activity, so you’re not re-explaining your surroundings each turn.
• MCP support, connect external tools via stdio or Streamable HTTP; tools bind at session start.
• ZIDE.md, durable project instructions at repo root, same convention as AGENTS.md/CLAUDE.md.
• Multiple concurrent sessions with a Session Watch view showing which ones need input.

Git and worktrees as first-class surfaces

Hunk-level staging, inline conflict resolution, a visual commit graph with ahead/behind, branches, tags, stashes, reflog, and git worktrees treated as real objects, each opening as its own folder tab. That matters because worktrees have become the standard way to run parallel agents without them stepping on each other.

DevOps surfaces

Issues with labels, milestones, and bulk actions (GitHub and GitLab only, Bitbucket has no issue support), PR/MR creation and review, CI across GitHub Actions, GitLab pipelines, and Bitbucket Pipelines with logs and re-runs beside the code. Integrated repo-aware terminals round it out.

Model choice: the actual differentiator

This is what separates Zide from most of the category. Five ways to reach a model (zide.dev/models):

1. Zide Models, bundled catalog with included credits.
2. Bring your own API key, including OpenRouter.
3. Eligible model subscriptions, use a provider subscription you already pay for.
4. Included monthly credits on paid plans.
5. Local models, Ollama, llama.cpp, LM Studio, or any OpenAI-compatible endpoint.

Providers named include Anthropic Claude, OpenAI Codex, Google Gemini, and DeepSeek. You can switch models mid-session without rebuilding context.

Two catches worth stating plainly:

• BYO key and local models are gated behind the Standard plan ($20/mo). They’re not free-tier features.
• “Local keeps data local” is only fully true for local-model connections. Per the business FAQ, BYOK cloud traffic currently passes through Zide Cloud Service en route to the provider. If data residency is why you want BYOK, read the FAQ yourself before relying on it.

Pricing

Plan	Price	What you get
Free	$0	Public repos plus up to 3 open folder/worktree projects. Core git/editing works with no account at all. Occasional promotional Assist credits on the Economy model, not guaranteed, no rollover.
Solo	$10/mo	Unlimited private repos, full DevOps across GitHub/GitLab/Bitbucket, monthly Assist credits.
Standard	$20/mo	Full model catalog, BYO API key, local models.
Pro / Max	see zide.dev/pricing	Higher capacity tiers.
Teams / Business	by discussion	Contact team@zide.dev.

One genuinely unusual term: after 12 continuous months on a paid plan you get a perpetual license for the qualifying version, though updates, AI services, and credits still need an active subscription. Checkout runs through Polar, so expect Polar on your card statement.

Credit mechanics matter if you’ll use Assist heavily: Zide reserves the maximum possible cost of each request before sending, charges actual usage, and refuses the request upfront if the reservation exceeds your balance, nothing charged, with recovery options like Compact and Retry. Unused monthly credits don’t roll over.

Security posture

Tokens go in the OS secure store (Windows DPAPI, macOS Keychain, Linux Secret Service); OAuth device flow is recommended for GitHub, PATs supported and validated against the API. The business FAQ states Zide doesn’t train on customer inputs or outputs, and, correctly, says it doesn’t replace your security controls or code-review process. No admin policy enforcement of approved models yet; it’s on the roadmap. Voice dictation and connected services can transmit data off-device.

For a beta, this is a more considered answer than most vendors give. It’s still self-reported.

How it compares

The category in mid-2026: Cursor and Windsurf (AI-first editors), Devin Desktop, Zed, Claude Code (terminal-first), and various desktop agent wrappers. Zide’s claimed distinctions are breadth, issues, CI, and PRs across three git hosts rather than a single-repo chat, provider-agnostic model access, native performance, and multi-repo/worktree-first design.

Whether those hold up under daily use is unknowable on launch day. There is no independent coverage yet: the press release was syndicated widely (PRNewswire and mirrors), but that’s one source family, not reception. No third-party benchmarks exist at publish time.

Should you look at it?

If your day is issue → agent → review → PR → CI and you’re tired of gluing five windows together, it’s the right shape of tool and cheap to try, the Free tier runs core git and editing with no account. If you need local models or your own API keys, budget for Standard. And calibrate expectations: this is a v0.7.0 public beta that shipped today.

Done means

You can answer, with sources: what Zide is, which git hosts and model providers it works with, what each pricing plan actually gates, and whether its security posture meets your bar, without taking the vendor’s marketing at face value.

What this article does NOT cover

• Step-by-step installation or configuration, that’s the companion guide.
• Benchmark comparisons against Cursor, Windsurf, or Devin, none exist yet; Zide launched into public beta on 2026-08-24.
• Pro/Max tier prices, not verifiable at publish time; see zide.dev/pricing.

Related guides

• Different ways of using LLMs for coding: eight patterns
• AI coding is a nightmare, not the only one
• Hermes vs OpenClaw: pick a path
• Start here: local AI and agents

Sources

Primary:

• https://zide.dev/, positioning, tech stack, model providers
• https://zide.dev/features, feature inventory, workflow loop
• https://zide.dev/download, v0.7.0 builds, sizes, signing entity
• https://zide.dev/pricing, plan structure, perpetual license
• https://zide.dev/models, five model-access paths
• https://zide.dev/about, founder, public commitments
• https://zide.dev/faq, business/security FAQ incl. BYOK transit
• https://docs.zide.dev/guides/zide-assist/, Assist mechanics, Plan mode, Crosscheck, rollback semantics
• https://docs.zide.dev/guides/credits/, credit reservation/refusal mechanics
• https://github.com/zide-software/Zide, README, license stance

Press (single source family):

• https://www.prnewswire.com/news-releases/zide-opens-public-beta-of-its-native-ai-development-workspace—code-git-issues-and-ci-in-one-app-302858181.html
• http://www.prunderground.com/zide-opens-public-beta-of-its-native-ai-development-workspace-code-git-issues-an/cmt6mi9vx000904jxu3zznxqa, $10/$20 price confirmation
• https://apps.microsoft.com/detail/xp8lh6blvfn4kw, Free-plan limits, promo-credit fine print

Contextual:

• https://www.augmentcode.com/tools/best-ai-coding-agent-desktop-apps, category landscape