JaadeAgentic IDE
// AI ADE explained

An environment for
agent-driven development.

Learn what an AI ADE is: an agentic development environment built around coding-agent sessions, project context, review, history, permissions, and control.

Download for Mac
Public releases
// The working definition

Built around the run,
not just the editor.

An AI ADE—an agentic development environment—organizes development around delegated runs. The agent can work in the codebase, while the developer keeps the prompt, model, permissions, terminals, files, diffs, history, and follow-up decisions visible in one workspace.

Jaade AI ADE showing coding-agent sessions, workspace context, model controls, plan mode, and local activityJaade AI ADE showing coding-agent sessions, workspace context, model controls, plan mode, and local activity
AI ADE workspaceAgent sessions, model and permission controls, branch context, files, review surfaces, and local activity share one workspace.
// What stays in reach

One surface for the work
around the agent.

Delegate

Configure before the run

Choose Claude Code, Codex, OpenCode, or Cursor, then set the model, effort, permission mode, plan mode, and workspace context before sending the task.

Observe

Keep the work inspectable

Follow the transcript, tool calls, terminals, files, branches, and agent tasks while the work is happening instead of reconstructing it afterward.

Decide

Review before commit

Inspect diffs, stage intentionally, resolve conflicts, and keep developer approval at the points where the work becomes durable.

// A visible loop

Define, run, review, resume.

The AI ADE is the connective tissue around a coding agent. Jaade keeps the loop visible without replacing the CLIs, credentials, repositories, or Git workflows you already use.

  1. 01

    Define the task

    Open the workspace, choose the agent and model, attach the right context, and decide how much permission the run should have.

  2. 02

    Run with context in reach

    Keep terminals, workspace files, search, branches, MCP servers, and project context next to the active session.

  3. 03

    Inspect the result

    Read the transcript and summary, review changed files and diffs, then stage or revise the work intentionally.

  4. 04

    Resume when the work continues

    Reopen the original session with its prompt, model, branch, transcript, changed files, and durable memory context.

// Continue with the details

Read the workflow, not a pitch.

View public repository
Introduction

See how Jaade turns agent runs into visible, workspace-aware sessions on macOS.

Read the guide
Core concepts

Understand workspaces, sessions, agents, side panes, and the persistence model.

Read the guide
Feature map

Explore the complete surface: agents, terminals, Git, projects, memory, schedules, and tools.

Read the guide
// Questions

Before you
open a workspace.

How is an AI ADE different from an AI code editor?

An editor centers the file. An AI ADE centers delegated runs and the control loop around them: session configuration, project context, tools, permissions, review, history, and resume. Jaade still includes files and terminals, but organizes them around agent work.

Does Jaade replace Claude Code or Codex?

No. Jaade runs your existing coding agents and keeps their work visible in a shared desktop workspace. You still use your own agent credentials, subscriptions, CLIs, and provider configuration.

Which platforms and agents are supported?

Jaade currently ships for macOS. Claude Code and Codex are first-class agents; OpenCode and Cursor are available as experimental agents.

Open a workspace.
Keep every session visible.

Jaade is a local Agentic IDE for Claude Code, Codex, OpenCode, and Cursor. Run agents and terminals, coordinate projects, schedule prompts, review diffs, and keep history, memory, plugins, skills, MCPs, and summaries in one workspace.

Download for Mac
Read the docs
Local desktop app for macOS Four coding agents Review, projects, memory, and schedules
local-first·agent-aware