Skip to main content

First Launch

What Daintree shows you the first time it opens: the Welcome Screen, the agent setup wizard, the searchable launcher, the getting-started checklist, and the narrated Daintree Tour.

Updated
Reviewed

First launch

The first launch opens the Welcome Screen. Nothing pops up over you, and no wizard takes the window. The Welcome Screen leads with opening a project, shows one setup nudge at a time, and leaves the rest until you ask for it.

Daintree runs as a single instance. Launch it again while it is running and it brings the existing window forward instead of starting a second copy.

Welcome Screen

The Welcome Screen with no project open: four ways in, and the shortcuts worth learning first

The Welcome Screen is what a window shows when no project is open. On a first run it leads with the Daintree mark, Welcome to Daintree and A habitat for your AI agents. Once you have opened projects, that header gives way to Your projects: up to five of them, in the order the project switcher uses. Click one to open it.

Three quick actions sit below it:

  • Open project. Open an existing folder on your machine. This is the screen's lead action. The small window button in the card's corner, Open in new window…, opens the folder in a window of its own and leaves this one where it is.
  • Create project. Start fresh in a new folder: you pick the location, the folder name and an emoji. See Creating a project from scratch.
  • Clone repository. Pull a repo from a Git URL. See Cloning a Repository.

Below those it shows exactly one nudge at a time, in this order, so you never face a stack of competing cards:

  1. Set up your AI agents. A card that says setup is optional, with a Set up agents button (opens the wizard) and Not now. Dismiss it and it stays dismissed across sessions; a Set up agents button stays in the Welcome Screen's footer so you can come back to it.
  2. Getting started. Your progress through the first steps, covered in Getting Started checklist below. It appears once the setup card is dealt with, or as soon as you open a project.
  3. Installed agents found. When Daintree finds launchable agent CLIs on your PATH and none of them is pinned to the toolbar, this card lists them as chips with Pin all to toolbar and Not now. It waits until the checklist is finished or hidden.

Further down, a Keyboard shortcuts list names the bindings worth learning first (New panel, Quick switcher, New terminal, Command palette, Keyboard shortcuts and Settings), each drawn as your live binding. It steps aside while the checklist is showing, because the checklist is the teaching surface at that point. Once the setup card is dealt with, a first run also shows a link to the Daintree Tour under the welcome line.

Agent Setup Wizard

The agents step of the first-run setup. Installed agents are already selected.

The wizard never opens itself. It runs only when you ask for it:

  • Set up agents on the Welcome Screen's setup card, or in its footer once the card is gone.
  • Settings > CLI agents > Run setup wizard.
  • The New Panel palette (Command-N Control-N Control-N ): choose More agents…, or an agent that isn't installed yet. Closing the wizard brings you back to the palette.
  • The launcher's Set up agents row, which appears when no agent CLI is installed at all.

Creating a worktree won't trigger it.

A first run walks up to six steps. The dialog is titled Set up Daintree, and the header counts Step n of N. Re-running it later opens Agent setup, a shorter three-step flow, because the consent steps only belong on a first run: a returning user already has those toggles in Settings. The install step is skipped, and drops out of the count, when everything you picked is already installed.

StepWhat it asksFirst runRe-run
AppearanceTheme cards with mini UI previews: Daintree (dark) and Bondi Beach (light), plus your current theme if you have already picked a different one. Clicking a card applies it immediately. The rest live in Settings > Appearance.YesNo
Choose your AI agentsThe system requirements check, then the agent multi-select.YesYes
PrivacyA single Enable crash reporting switch, off until you turn it on, with a Preview what would be sent link. The preview shows the diagnostic fields and redaction policy; review it before choosing.YesNo
Install agentsRuns the install for anything you picked that isn't on your machine yet. Skipped entirely when everything picked is already installed.YesYes
Agent permissionsThe global Skip permission prompts for agents switch. Off is the safe default. See Security.YesNo
Setup completeCounts the ready agents and lists each one with its preset count and launch shortcut. Titled Setup saved instead when no agent is ready yet.YesYes

On the first step the left-hand button is Not now on a first run, which closes the whole wizard, or Cancel on a re-run. Later steps show Back. The last button depends on where you are: Open a project when no project or scratch workspace is open yet (an agent launched from the Welcome Screen would otherwise start in your home folder), Launch an agent when one is, and Finish setup when no agent is ready.

Closing the wizard before you reach Setup complete on a first run commits crash reporting as off and leaves a note in your inbox saying so. Silence is not consent.

The system requirements check

The System requirements panel sits at the top of the agents step. When every tool passes it stays collapsed and reads All system tools ready; expand it for the details and a Re-check button. When a required tool (Git or Node.js) is missing or too old, the panel opens and can't be folded, its header reads Action required with a count of ready tools, and a Check again button sits beside the instruction to install it. A missing recommended tool, npm or the GitHub CLI, is a warning rather than a block. See System requirements.

Continue stays unavailable while the check is running, while a required tool is missing, and until you've selected at least one agent. The footer says which.

Choosing agents

The agent list is split into two tiers:

  • Featured: Claude, Gemini, Codex.
  • More agents: everything else that can be launched: currently fourteen, from OpenCode and Aider through Antigravity, Grok, Cursor, Copilot, Goose, Amp, Crush, Qwen, Kimi, Open Interpreter, Mistral, and Kiro. Every new built-in agent lands here automatically.

Installed agents float to the top of their tier and are pre-selected. Gemini is still featured in the checked-in ordering, but Daintree marks its integration deprecated. See Antigravity for the other Google CLI integration.

Installing

Each selected agent gets a card with its status: Not installed, Installing, Installed, Failed, or Manual. With one agent to install, the step's main button is Install followed by that agent's name; with several it is Install selected agents, and each card also carries its own Install. Agents with more than one install method (npm versus Homebrew, for example) carry a method switcher. If an install fails, expand Show error log for the output, or copy the manual command from the card. Until one of the agents you picked is usable, the forward button reads Set up later.

Some install commands are never run for you: anything that pipes a remote script into a shell, and anything needing sudo. Those show as Manual with the command to copy.

The launcher

One searchable launcher covers agents, panels, and recipes

Agents, panels, and recipes all start from one searchable launcher. It has two triggers that open the same list: the + at the head of the toolbar, which creates panels in the grid, and the + at the left end of the dock, which creates them in the dock where the panel kind allows it. The inventory and every row are identical; only the destination differs.

With the search box empty, the launcher lays its inventory out in two columns (one, on a narrow window):

  • Agents: one list. The agents you launched most recently come first, marked Recent, then the rest with your pinned ones first. A filled pin marks an agent that has its own toolbar button. An agent that is installed but not ready to launch is marked Setup. When no agent CLI is installed at all, the list offers every built-in agent with a route to setup, followed by Set up agents.
  • Open in grid / Open in dock: panel kinds, headed by where they will land. Terminal, Browser, Dev preview, Review, File viewer, File browser, and any panel kind a plugin registers.
  • Recipes: your saved recipes, with their scope shown on the right, or Create a recipe when you have none.
  • More, holding Manage agents and Customize toolbar….

Type anything and the columns collapse into a single ranked Search results list. Alt+P pins the highlighted row to the toolbar, and F2 records a launch shortcut for the highlighted agent. The full row model is on Toolbar, Dock and Windows.

When Daintree spots an agent CLI on your PATH that you haven't seen before, the toolbar's + wears a small blue discovery dot, its accessible name says new agents were detected, and the agent's row carries the same dot. The dot holds off while the Installed agents found card is on screen, so the two don't compete for your attention.

Tip
Command-N Control-N Control-N opens the New Panel palette, a modal cousin of the launcher grouped into AI Agents, Resume Sessions, and Tools. Resume Sessions is how you pick up a closed agent conversation. See Session Management. The full set of palettes is in Palettes & Menus.

Getting Started checklist

A short checklist tracks the first things worth doing in Daintree. It has five rows: Install Daintree, already ticked for you, then four you do yourself:

  1. Open your project. Ticks as soon as a project is open.
  2. Launch your first agent. Ticks once an agent panel exists.
  3. Start a parallel task. Ticks once the project has a second worktree.
  4. Run two agents in parallel. Ticks when two agents are active at the same time, working or waiting on you.

Items tick themselves off as you do the matching action; you never check anything by hand. Only the next unfinished row shows its description and its shortcut, so the list reads as one next step rather than four instructions at once. Completed rows get a neutral check, not an accent color.

It shows up in two places, once setup is settled: after you finish or decline the setup card, or as soon as you open a project.

  • Inline on the Welcome Screen, as a progress report with a counter that starts at 1/5 and a progress bar. The rows there aren't buttons: with no project open they would act on nothing, and the Open project card above is the way forward.
  • Floating panel in the bottom-right corner once a project is open, with the same counter. Here each unfinished row is a button: Open your project opens the folder picker, Launch your first agent and Run two agents in parallel open the New Panel palette (a second agent is a second panel, not a second worktree), and Start a parallel task opens the New Worktree dialog. A View keyboard shortcuts link sits underneath.

The floating panel collapses itself once you've launched an agent and clicked into a panel. When all four items are done the checklist goes away on its own; Help > Getting Started brings it back, reading All set.

Tip
The X dismisses the checklist; the chevron, the header, or Esc only collapses the floating panel. To bring it back after dismissing it, choose Help > Getting Started.

The Daintree Tour

The Daintree Tour is a narrated, animated walkthrough of the app in fourteen short chapters, about five minutes end to end. It plays on mock-ups rather than your own workspace, so it needs no project and changes nothing. It covers worktrees, launching agents, agent states, fleets, browsing files, copying worktree context, dev preview, working from forge issues, review, Pilot, the Daintree Assistant and the command palette. Chapters that mention a shortcut are voiced for your platform's keyboard.

Start it from any of these:

  • Help > Daintree Tour, or search the command palette for Daintree Tour.
  • The invitation card on an empty panel grid: Start tour, or Resume tour if you stopped part way. Not now turns the invitation down for good, and a note says where to find the tour.
  • The link under the welcome line on a first-run Welcome Screen.

The player works like a video: Space or K pauses and resumes, ← and → step back and forward five seconds, M mutes the narration, and the chapter buttons jump straight to a chapter. The header shows Chapter n of 14. Plugins can contribute tours of their own, which appear under the Daintree Tour in the Help menu.

Pause a chapter to review its example, then continue at your own pace

Keyboard shortcut tips

Daintree teaches its shortcuts as you go. Hover over a control for a moment, or tab to it with the keyboard, and a small chip appears naming the action and its shortcut, for example Open command palette with Shift-Command-P Control-Shift-P Control-Shift-P . It shows up before you've used the action and steps back once you know it, so it's there when it helps and quiet when it doesn't. For the full reference and how to customize bindings, see Keyboard Shortcuts.