ADCode

Every feature, explained: the full ADCode tour

All twelve feature areas in one walk-through - what each group does, why it exists, and where its documentation lives.

ADCode documents every switch it has - seventy-plus pages in the docs, each with steps, benefits, and a comparison. This tour walks the twelve groups in the order the settings do, so you know what exists before you need it.

Editing

Nineteen pages covering typing itself: suggestions and word completion, multi-cursor and column selection, auto-close and auto-rename of tags, code folding, sticky scroll, indent guides, bracket colours, TODO highlighting, path autocomplete, file templates, and the error lens that puts messages at the end of the line they describe. The theme of the group: helpful by default, one switch each when you disagree. Start with multi-cursor and plain-English errors.

Finding your way

Breadcrumbs, fuzzy file open (Ctrl+P), symbol search (Ctrl+T), global search-and-replace with preview, outline, and go-to-definition that tells you whether an answer was *resolved* by a language server or merely *matched by name*. Navigation answers "where am I" and "where is it" without the mouse.

Formatting

The built-in formatter, format-on-save, organize-imports-on-save, and live lint diagnostics. Zero configuration: Ctrl+S tidies the file, deferring to your language server when one knows better, and saving unchanged when nothing can.

Understanding a project

The CSS-aware group: tree lines in the explorer, missing-class detection, unused-selector detection, and the two-way link between style rules and the elements they touch - across HTML, JSX, Vue, Angular, and Handlebars. See Structure for the popup that ties it together.

Languages

Standards, not forks: the LSP client uses language servers installed on your machine, unknown languages take one config line, tree-sitter parses highlighting properly, and F5 debugs JavaScript, TypeScript, and Python. See language server intelligence.

The assistant

Ten pages, one idea: AI on your terms. Connect any major provider, an OpenAI-compatible gateway, or localhost; chat in a dockable widget with searchable local history; inline completion on Tab; memory capture that writes decisions to markdown files in your repo; MCP support so external agents share those notes; and detection that offers the connecting command when an agent starts in your terminal. Begin at Connect a model.

Git

Stage-commit UI, branch switcher, blame, gutter diffs, file timeline, and side-by-side merge conflict resolution with Keep yours / Keep theirs / Keep both buttons. Plain git underneath - the repository stays perfectly portable.

Your session

Auto-save after a pause, crash recovery that offers unsaved buffers back, local file history separate from git, and full workspace restore. The group whose job is that nothing you type is ever lost.

The workbench

Real terminals (several, stateful, pointed at your project), the Run button that infers the command, live preview beside your code, keyboard-shortcut editing with conflict warnings, and peer-to-peer collaboration over your local network - no relay server. See the built-in terminal and Run.

Appearance

Light, dark, or system-following - accent colour included - plus Comfortable/Compact density. Two switches, applied instantly.

Ads and earnings

Sponsored messages and their frequency: the card schedule counted on your machine, the server able to tighten limits but structurally unable to loosen them, and off meaning off. Each verified view pays half the CPM to an append-only ledger.

Updates

Background downloads applied on reopen, never mid-thought; release notes shown at most once per version and only when worth reading, with security fixes the single exception allowed to hurry.

---

Seventy-two pages later, the pattern should be visible: every feature ships on by default, every default has one switch, and every page says what it costs you. That is deliberate - an editor you can fully understand is an editor you can trust with your work.