palisadeDownload

Compare

Palisade against the tools you are using now.

Features documented by Palisade and four other tools
FeaturePalisadeEmdashCursorZedKiro
Parallel agents in isolated worktreesYes1Go tasks isolated by default; explicit opt-outYes2Git worktree per taskYes3Parallel agents in worktreesYes4Parallel threads with optional linked worktreesPartial5Parallel spec tasks; isolation not described
Use the agents you already haveYes1Compatible registry agents and adaptersYes2Installed CLI agentsPartial3Worktree docs cover Cursor AgentYes4ACP agentsPartial5Spec docs cover Kiro agents
Merge gated on a named verify commandYes1Exit 0 at a named commit; explicit overridePartial2Review diffs, pull requests and CI checksPartial3Review result, then apply worktree changesPartial4Review diff, then merge through GitPartial5Spec validation and property tests
Spec-driven workflowYes1Spec and go modes over OpenSpecUnknownNot established by the documentation reviewedPartial6Plan Mode scopes tasks, not spec filesUnknownNot established by the documentation reviewedYes5Specs are the core workflow
Multi-agent playbooks with gatesYes1Verify or approval gates on edgesPartial7Scheduled recurring runs, not gated chainsUnknownNot established by the documentation reviewedUnknownNot established by the documentation reviewedPartial5Spec tasks sequenced, no gate described
Built-in preview browserYes1Native preview per projectYes7Preview inside the taskYes8Browser opens inline or in a separate windowUnknownNot established by the documentation reviewedUnknownEmbedded preview not established by the documentation reviewed
MCP server managementYes1Project-scoped .mcp.json over ACPYes7Manage prompts, skills and MCP toolsYes9MCP servers via Marketplace or mcp.jsonYes10MCP context servers via Settings > AIYes11Local and remote MCP servers
Local code completion, no uploadYes1Bundled local modelUnknownNot established by the documentation reviewedUnknownNot established by the documentation reviewedYes12Local models supported; configure a local providerUnknownNot established by the documentation reviewed
Open sourceYes1Apache-2.0Yes7Open-source, per its homepageUnknownNot established by the documentation reviewedYes13Editor GPL-3.0; other components Apache-2.0UnknownPublic issue repository does not establish the product’s source license
macOS, Windows and LinuxPartial1macOS 11+ only, for nowYes7macOS, Windows and Linux, per its FAQYes14macOS, Windows and Linux, per downloads pageYes15macOS, Linux and Windows, per homepageYes16macOS, Windows and Linux downloads listed
  • Yes
  • Partial
  • No
  • Unknown

* Based on published documentation checked on October 4, 2026. Numbered cells link to sources. Unknown means the reviewed sources did not establish support; it does not mean the feature is absent. Report an out-of-date comparison.

Sources

  1. github.com/TJLSmith0831/palisade-code
  2. emdash.com/docs
  3. cursor.com/docs/configuration/worktrees
  4. zed.dev/docs/ai/parallel-agents
  5. kiro.dev/docs/specs/
  6. cursor.com/docs
  7. emdash.com
  8. cursor.com/docs/agent/tools/browser
  9. cursor.com/docs/context/mcp
  10. zed.dev/docs/ai/mcp
  11. kiro.dev/docs/mcp/
  12. zed.dev/docs/ai/edit-prediction
  13. github.com/zed-industries/zed
  14. cursor.com/downloads
  15. zed.dev
  16. kiro.dev/downloads/

Switching guides

Switching from Emdash

“Open-source agentic development environment”

Emdash and Palisade both run CLI agents in separate git worktrees. Palisade adds a verify command that gates merge, and playbooks with gates between agents.

  1. Download Palisade and open your repo as a project.
  2. Palisade discovers compatible ACP adapters. Use Add an agent if your adapter is not installed.
  3. Start one thread per task. Each gets its own worktree, as before.
  4. Name a verify command for the project, such as your test script.
  5. Review each diff in the review lane and merge once verify passes.

What you keep

  • Your installed agents and their logins
  • Your repo and branches
  • Your worktree-per-task habit

Switching from Cursor

“Cursor is your coding agent for building ambitious software.”

Cursor documents parallel agents in worktrees around its own agent. Palisade drives any ACP agent you install and waits for a verify command before merge.

  1. Download Palisade and open your repo as a project.
  2. Add a compatible ACP agent in Palisade and follow its sign-in flow.
  3. Choose the Cursor ACP registry entry to use Cursor’s CLI agent; the desktop editor is a separate app.
  4. Start threads in parallel. Keep Isolated enabled for separate Go worktrees.
  5. Name a verify command so merge has evidence to check.

What you keep

  • Your repo and branches
  • Your agent subscriptions
  • Your git remotes

Switching from Zed

“Your last next editor”

Zed is an editor that also runs ACP agents in parallel threads. Palisade starts from the fleet of agents and gates merge on recorded verify evidence.

  1. Download Palisade and open your repo as a project.
  2. Choose the same compatible ACP adapters in Palisade; install their runtimes and sign in as needed.
  3. Start a thread per change. Keep Isolated enabled for Go tasks to use separate worktrees.
  4. Name a verify command, then watch the fleet board for results.

What you keep

  • Your ACP agents and their logins
  • Your repo and branches
  • Your git remotes

Switching from Kiro

“Move beyond AI coding to agentic engineering”

Kiro and Palisade both start from a spec. Palisade keeps the spec in OpenSpec and lets you run the agents you already have.

  1. Download Palisade and open your repo as a project.
  2. Add a compatible ACP agent in Palisade and follow its sign-in flow.
  3. Start a thread in Spec mode. The agent writes an OpenSpec change.
  4. Switch to Go to build it, then run verify before merge.

What you keep

  • Your repo and branches
  • Your spec-first habit
  • Your choice of model, per thread
Download for macOSRead the docs