AIDE Docs

How to work
in AIDE

A detailed manual: from the first launch to your own commands for the agent, checks, updates and troubleshooting.

Getting started

AIDE is a desktop code editor with an AI studio built in: an agent, a design canvas and a team of twelve roles work in one window. Below is the short path from install to your first edit.

  1. Install Node.js 20+, Rust and the Tauri 2 dependencies for Windows — this is only needed if you build the editor from source.
  2. In the project folder run npm install, then npm run tauri dev.
  3. Open your code folder: Ctrl+O. Recent projects are on Ctrl+R.
  4. Connect a model in the settings. The API key is stored in the Windows credential store, not in files.
  5. Describe the task in the chat on the right. The agent proposes a plan, asks permission for file writes and commands, and reports what it did together with the token count.

If you just use the installer, Node.js and Rust are not needed — everything is already inside.

Install and updates

The ready-made installer is on this site: the “Download for Windows” button in the Start section. You need Windows 10 or 11 and WebView2 — current builds already have it.

  • Building from source. npm install, then npm run tauri build. The files land in the bundle folder next to the project: an NSIS installer and an MSI package.
  • Updates arrive by themselves. Once a day AIDE compares its version with the latest GitHub release and offers to update. You can also check manually.
  • Signature. Update files are checked against a cryptographic signature: the app will not trust a build from an outside source.
  • Windows warning. The installer is not signed with a paid publisher certificate, so SmartScreen may ask for confirmation on first launch. It does not affect the editor itself.
  • Uninstalling. The usual Windows uninstall. Your projects, settings and keys stay in place — remove them separately if you want to.

Workspace

The project tree is on the left. Files and folders are created, renamed and deleted from the context menu, and changes on disk are picked up right away: an outside edit is never lost.

  • Tabs. They keep their cursor position and undo history and close with the middle mouse button. Images, PDFs and fonts open for preview right in the editor.
  • Panels. Explorer, project search, Git, snippets and extensions switch in the left panel and stay out of each other's way.
  • Text search. Ctrl+Shift+F searches by text, with case and file masks.
  • Search by meaning. A query like “parse config file” finds the right places even when the code uses other words: function and path names count separately from plain text.
  • Command palette. Ctrl+P — files and actions without the mouse.

Editor and languages

The editor is built on CodeMirror 6: highlighting, line numbers, completion, search and replace, multiple cursors and folding.

  • Language servers. Type hints, error squiggles, go to definition and back, rename a symbol and format a file — the same servers VS Code uses.
  • Works without a server. If no language server is installed for a language, highlighting, navigation and symbol search remain.
  • Git conflicts. Shown as a merge view: accept your side or theirs with a button, no need to edit the file by hand.
  • Agent edits. Ctrl+K on selected code — the agent proposes a new version and you accept or reject it by diff.

Chat and models

OpenAI, Anthropic, Google and any compatible server are supported: the address and the model list are set in the provider settings.

  • Local models. Ollama or LM Studio on this computer — then requests never leave the machine.
  • Keys. Stored in the Windows Credential Manager, separately per provider. A key never reaches the project, the model's reply or a log.
  • Tokens. Every answer shows what it cost, so models can be compared by price rather than by feel.
  • History. Lives in the project: come back to the folder and the conversation continues where it stopped.
  • Attachments. Attach a file or an image to a message and its text joins the model's context.
  • Queue. If the agent is still working, a new message waits in the queue; the arrow next to it sends it immediately and stops the current answer.

Three modes

The switch in the window header changes the whole interface. The project, the history and the agent stay the same.

IDE
An editor on CodeMirror 6, file tree, tabbed terminals, Git and search. The agent lives in the chat on the right.
Vibe
Describe the result in words. The team lead splits the task into steps, the roles do them, QA checks.
Design
Build a mockup on the canvas, then press “Create in project” and pick a stack: HTML, React, Vue, Svelte, Next.js or Astro.

Agent

  • Permissions. Writing files and running terminal commands happen only after you click “Allow”.
  • Report. Each reply ends with a list of actions, e.g. “Done: 6 actions ›”, and the number of tokens spent.
  • Undo. A checkpoint is created before any edit. The “Undo” button restores the changed files.
  • Stop. Cuts the request to the model instantly.
  • Edit a selection. Select code and press Ctrl+K: the changes appear as a diff you can accept or reject.
  • Clarifications. When a task can be read in different ways, the agent asks first and then works — it does not decide for you.

Terminal and Git

  • A real pty. Interactive programs, colours, arrows and Ctrl+C all work. As many terminal tabs as you need.
  • Git panel. Changed files, a line-by-line diff, branch and history; commits are made from there too.
  • Agent commands. It can run them, but only with your confirmation: you see exactly what is about to run.

Quality checks

  • After edits. AIDE runs the project's checks — types, linter, tests — and reports back if something broke.
  • Before “done”. The verify-before-done skill requires re-reading the diff, building the project and running the tests.
  • Diagnostics. Language server errors show up in the panel immediately, before the project is even run.
  • Turning off. Self-checks can be disabled in settings when a project is big and the checks take long.

Crew

  • Twelve roles: team lead, design, front, back, QA, DevOps, analyst, lawyer, accountant, marketer, intern and joker.
  • Only roles with “hands” can change files and run commands; the rest advise and review. The team lead splits the work and pulls the result together, QA checks every task.

You are the CEO: you decide what of it makes it into the code.

Rules and commands

Put AGENTS.md or CLAUDE.md in the project root — the agent reads these rules before it starts.

Your own chat commands: create a file .aide/commands/name.md with the prompt. It shows up in chat as /name, and $ARGUMENTS is replaced with whatever you type after the command.

Project rules beat the agent's habits: if a file forbids changing something, the agent asks instead of doing it silently.

Security and data

  • Keys. In the Windows Credential Manager. Not in the project, the repository or the logs.
  • Permissions. File writes, commands and network access only after confirmation.
  • Your code. Stays on disk: AIDE sends it only to the model you chose.
  • A local model. Then nothing leaves the computer at all.
  • No telemetry. The app collects no usage statistics and sends no hidden reports.

Settings

  • Appearance. Interface language, theme, editor font size, panel and terminal behaviour.
  • Providers. A fixed model list for servers that cannot list models themselves.
  • Skills. Built-in rule sets can be switched on and off: verify before done, careful changes, secure code, debugging, tests, frontend.
  • Permissions. What the agent may do without asking and what always needs a confirmation.

Hotkeys

Ctrl+OOpen a project folder
Ctrl+SSave the file
Ctrl+WClose the tab
Ctrl+PCommand palette
Ctrl+RRecent projects
Ctrl+BShow or hide the sidebar
Ctrl+JShow or hide the terminal
Ctrl+Shift+FSearch the project
Ctrl+Shift+GGit panel
Ctrl+KHave the agent edit the selected code
EscClose the palette, settings or edit

Frequently asked questions

Do I need Node.js and Rust just to use AIDE?
No. The installer already contains everything the app needs. Node is only needed for checks in your own project, and Rust only if you build AIDE yourself.
Where does my code go?
Only to the model you chose. With a local model it goes nowhere.
Where are API keys stored?
In the Windows Credential Manager, encrypted, separately for each provider.
Can I work without internet?
Yes, with a local model: the editor, terminal and Git always work, and the agent works with the local model.
What if the agent makes a mistake?
A checkpoint is taken before edits and Undo restores the files. Permissions stop it from doing anything without your consent.
Does AIDE run on macOS or Linux?
The build is for Windows today. The Tauri and React code is portable, but there are no ready builds for other systems.
How do I update?
By itself: the app checks for an update and offers to install it. Or download the new installer from this site.
Why does Windows warn when installing?
The installer is not signed with a paid publisher certificate — that is a SmartScreen warning, not a virus. Update signatures are verified separately.

When something does not work

  • The model does not answer. Check the key and the provider address in settings and your internet access. Error 401 means a wrong key, 429 means a rate limit.
  • It will not install. Close the running AIDE and try again.
  • Panels disappeared. Ctrl+B and Ctrl+J bring back the side panel and the terminal.
  • The terminal is empty. Open a new terminal tab — the old session may have ended.
  • No highlighting or hints. A language server may be missing for that language: install it in the system and the editor picks it up.
  • Checks fail. Paste the check output into the chat — the agent reads the error and fixes the cause, not the symptom.