Documentation

CodeSplash AI docs

Use CodeSplash AI as a full engineering desktop: connect your workspace, move between editor, terminal, Git, search, files, and run agent sessions without fragmenting the workflow.

Available now on macOS, Windows, and LinuxDevelopers, AI-native builders, and engineering teams
Coverage

What this guide covers

Workspace setup, Git and worktrees, Agent orchestration, All-in-one engineering modes.

Format

How to use this page

Work from top to bottom the first time, then use the section links as a reference once the product becomes part of your normal workflow.

01

Getting started

The fastest path is to treat the app like your daily engineering home rather than as a single AI panel.

Install the desktop build

Download the platform for your OS, launch it, and start from the repository or workspace you already work in.

Choose the right mode first

Open Editor, Files, Search, or Terminal based on what the task actually requires instead of forcing everything through a chat flow.

Set up shortcuts and settings early

The product becomes significantly faster once shortcuts, platform settings, and preferred defaults are configured around your personal loop.

02

Run the daily engineering loop

The core workflow is strongest when code, shell, search, and repository state stay visible inside the same environment.

Move between Editor, Files, and Search

Use Files to navigate structure, Search to jump across a codebase, and Editor to make the final changes without leaving the product.

Keep Terminal next to execution

Run package scripts, build steps, tests, and one-off commands directly beside the code they affect so context is never lost.

Use Notes and Kanban to keep context attached

Architecture notes, working plans, and task state can stay close to the repo instead of disappearing into separate tabs and apps.

03

Work through Git and parallel branches

Git is one of the product's clearest differentiators, so lean into the built-in repository surfaces rather than bouncing to another tool.

Review working copy state

Use the Git mode to inspect changed files, diffs, history, and branch state before you commit or hand off work.

Create parallel worktrees

Use separate worktrees when you need multiple active branches, experiments, or agent-led tasks open at once.

Keep branch strategy visible

The visual branching and history views are useful for staying oriented when several features or fixes are moving in parallel.

04

Use agents as execution surfaces

The strongest way to use the flagship is to supervise multiple agent sessions alongside normal engineering work.

Start focused agent sessions

Open agent sessions with clear repository context and a bounded task instead of relying on one long-running generic conversation.

Coordinate work in Command Center

Use Command Center to watch multiple sessions, compare outputs, and keep orchestration tied to the rest of the build workflow.

Pair Vibe Coding with hard engineering tools

Prompt-based creation works best when you can immediately drop into Git, Editor, Terminal, API, or Database modes to finish the real task.

05

Bring supporting product work into the same desktop

CodeSplash AI is more valuable when research, operations, and planning stay in the same environment as the code itself.

Research in Browser mode

Keep docs, references, and research close to the repo instead of juggling a separate browser workspace.

Use API and Database modes during implementation

Inspect requests, environments, queries, and data while you build instead of context-switching to external clients.

Keep communication and planning attached

Calendar, Email, Notes, and Kanban extend the product from coding into actual product delivery work.