Skip to content

Commit c57b1b7

Browse files
committed
Atom-plus-plus is alive
0 parents  commit c57b1b7

14 files changed

Lines changed: 751 additions & 0 deletions

‎.gitignore‎

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
# The upstream Code-OSS checkout is produced by scripts/bootstrap.sh — never commit it.
2+
/vscode/
3+
/.vscode-pinned-tag
4+
5+
# Build outputs (siblings of vscode/ created by gulp)
6+
/VSCode-darwin-*/
7+
/VSCode-linux-*/
8+
/VSCode-win32-*/
9+
10+
# Node / OS noise
11+
node_modules/
12+
.DS_Store
13+
*.log
14+
out/

‎.node-version‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
24.17.0

‎.python-version‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
3.12.13

‎LICENSE‎

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
MIT License
2+
3+
Copyright (c) 2026 Sergii Demianchyk (Atom++)
4+
5+
Permission is hereby granted, free of charge, to any person obtaining a copy
6+
of this software and associated documentation files (the "Software"), to deal
7+
in the Software without restriction, including without limitation the rights
8+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9+
copies of the Software, and to permit persons to whom the Software is
10+
furnished to do so, subject to the following conditions:
11+
12+
The above copyright notice and this permission notice shall be included in all
13+
copies or substantial portions of the Software.
14+
15+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21+
SOFTWARE.
22+
23+
---
24+
25+
Atom++ is a derivative of Code-OSS (https://github.com/microsoft/vscode),
26+
which is licensed under the MIT License, Copyright (c) Microsoft Corporation.
27+
Atom++ is not produced by, endorsed by, or affiliated with Microsoft.
28+
"Visual Studio Code" and related marks are trademarks of Microsoft.
29+
The upstream Code-OSS source is fetched at build time and is not redistributed
30+
in this repository.

‎PLAN.md‎

Lines changed: 131 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,131 @@
1+
# Atom++ — Build Plan
2+
3+
**An AI-native, hackable, Notepad++-powered code editor for macOS, forked from Code-OSS.**
4+
5+
> Decisions locked: foundation = fork VS Code / Code-OSS · your role = direct, AI writes most code · v1 must-haves = Atom-style hackability, native AI, Notepad++ power-editing. (Polished Mac UX rides along but is not a v1 gate.)
6+
7+
---
8+
9+
## 1. The strategy in one paragraph
10+
11+
We don't rebuild an editor — we stand on the most battle-tested editor core in existence (the same Monaco-based engine that powers VS Code, Cursor, Windsurf, and Void) and bend it into *your* editor. That gives us, on day one: a fast text engine that handles huge files, full Language Server Protocol support, debugging, Git, the extension model, multi-cursor, and column editing. Our job is then four things stacked on top: (1) **rebrand and de-Microsoft** the build so it's legally a clean product called Atom++, (2) **add the Notepad++ power-editing** that VS Code lacks, (3) **build a native AI layer** that is first-class rather than a bolted-on plugin, and (4) **restore the Atom "hackable" soul** — everything themeable, scriptable, and yours. Void (a YC-backed open-source Cursor alternative, also a VS Code fork) proves this exact path works and, crucially, is open source we can read.
12+
13+
---
14+
15+
## 2. Read this first — the legal constraints that bite every forker
16+
17+
These are not optional. Getting them wrong means a takedown or a broken editor.
18+
19+
**Code-OSS itself is MIT-licensed** — free to fork, modify, ship, even commercially. Good.
20+
21+
**But "VS Code" the product is not Code-OSS.** Microsoft takes the MIT `vscode` repo and lays down a proprietary `product.json` plus closed-source bits (telemetry, branding, marketplace gallery). When you build the raw repo you get an unbranded editor. To make Atom++ you replace `product.json` with your own (name, icons, URLs, gallery endpoint). VSCodium is the reference example of doing exactly this cleanly.
22+
23+
**The Microsoft Extension Marketplace is off-limits.** Its terms of service legally restrict use to Microsoft products only. Atom++ must point its gallery at **Open VSX** (the Eclipse-run open marketplace VSCodium, Gitpod, and others use). Practical consequence: a handful of popular extensions are Microsoft-proprietary and *cannot* be redistributed or used outside official VS Code — notably the C/C++ extension, Pylance, the Remote-SSH/Containers/WSL pack, the official Python debugger, and the Live Share service. We either find open equivalents (clangd, the open Python LSP, Open Remote SSH) or build our own. **This is the single most important thing to internalize before writing code.**
24+
25+
**Trademark — "Atom".** "Atom" was GitHub's trademark for the sunset editor. Reusing the exact name and logo carries IP risk. We should treat "Atom++" as a working codename and plan a final name + original logo before any public release. (We can keep the spirit and feel without the protected mark.) This is a release-blocker, not a build-blocker.
26+
27+
---
28+
29+
## 3. Architecture — what we keep, change, and add
30+
31+
**Keep wholesale (the reason we forked):** the Monaco text engine, LSP/DAP infrastructure, the extension host and API, multi-cursor and box-selection, Git integration, search, settings/keybindings/theming systems, the task and terminal infrastructure.
32+
33+
**Change / strip:** swap `product.json` for Atom++ branding; remove Microsoft telemetry; repoint the gallery to Open VSX; restyle the shell (title bar, activity bar, color tokens) toward the Atom aesthetic; set sensible Atom++ defaults.
34+
35+
**Add (our four pillars):**
36+
- a **native AI subsystem** living in the core, not the extension sandbox, so it can stream completions, edit across files, and run agentic tasks with full editor access;
37+
- a **Notepad++ power-editing pack** for the gaps (macros, column-mode quality-of-life, encoding/EOL controls, big-file mode);
38+
- a **hackability layer** (user init script, live config, package authoring, theme studio);
39+
- **Mac-native polish** (proper traffic-light integration, native menus, fast cold start).
40+
41+
Architectural rule we adopt from Void: **no proprietary middle-man backend.** AI requests go directly from the user's machine to whatever model provider they choose (their own API key, or a local model via Ollama). This is a privacy and trust feature, and it keeps us out of the business of running inference servers.
42+
43+
---
44+
45+
## 4. The AI layer — design
46+
47+
This is what makes it *AI-native* instead of "VS Code with a chat plugin." Four capabilities, built into the core:
48+
49+
1. **Inline completions / tab-autocomplete** — ghost-text suggestions as you type, accept with Tab. Driven by a fast model.
50+
2. **Chat with your codebase** — a side panel that has read access to the open project, can be given files/symbols as context, and answers grounded in your actual code.
51+
3. **AI edits & refactors** — select code (or a whole file) and instruct a change; Atom++ applies it as a reviewable diff you accept or reject. Multi-file edits supported.
52+
4. **Agentic tasks** — give it a goal ("add a setting that does X"), it plans, edits across files, runs commands, and reports back — gated behind your approval.
53+
54+
**Model strategy:** bring-your-own-key by default (Anthropic/Claude, OpenAI, Google, plus OpenAI-compatible and Ollama for local). Native support for Claude is a first-class target since AI-native is the whole point. Users see and can edit the actual prompts sent — transparency as a feature (another Void idea worth stealing).
55+
56+
**What we study, not reinvent:** Void is open source and is the same fork lineage — we read its AI integration for the wiring patterns. Continue.dev (open source) is a second reference for context-gathering and provider abstraction. We don't copy code blindly (license check first), we learn the architecture.
57+
58+
---
59+
60+
## 5. Notepad++ parity — the feature matrix
61+
62+
What you love about Notepad++, mapped to effort. Much already exists in the core; the real work is a focused list.
63+
64+
**Already native in the fork (just expose/tune defaults):** multi-cursor; column/box selection (Shift+Alt+drag); powerful regex find/replace (Rust regex — ~95% compatible with NPP's Boost; differences are fixed-width lookbehind and some slash-escaping); find-in-files; minimap; bracket matching; split views; session restore.
65+
66+
**Needs building or a first-party pack:**
67+
- **Macro record & replay** — VS Code dropped keystroke macros on purpose; NPP users genuinely miss them. We build a first-party record/replay so it's reliable, not a flaky third-party extension.
68+
- **Big-file mode** — a read-optimized path for 300 MB–1 GB+ files (disable tokenization/extensions, virtualized rendering). NPP's signature strength; we make Atom++ not choke.
69+
- **Encoding & line-ending controls** — one-click convert encoding (UTF-8/16, codepages) and EOL (CRLF/LF/CR), always visible in the status bar.
70+
- **Column-mode quality of life** — column insert, fill, incrementing number insertion (NPP's column editor extras), beyond raw box-select.
71+
- **NPP-flavored extras** — block comment toggles, "mark all" highlighting, sorting/dedup lines, convert case, on-the-fly language detection — bundled as one "Notepad++ Pack" that ships on by default.
72+
73+
---
74+
75+
## 6. Atom hackability — the soul
76+
77+
Atom's draw was that *everything* was editable and it felt like yours. We restore that explicitly:
78+
79+
- **Live config** — a human-readable settings file plus a real Settings UI; changes apply without restart where possible.
80+
- **User init script** — an Atom-style "run my code at startup" hook so power users can script the editor itself.
81+
- **Packages** — first-class package authoring with a generator, hot-reload during development, and one-click publish to Open VSX.
82+
- **Theme studio** — themes as data, a live preview, easy color-token overrides, and import of community themes. Atom's beautiful default themes (One Dark / One Light) are open source we can adapt for the signature look.
83+
- **Keymaps** — fully remappable, with a built-in "Notepad++ keymap" and "Atom keymap" preset so muscle memory transfers instantly. We also ship migration that imports existing VS Code keybindings/settings/themes (Void does this; it dramatically lowers switching cost — including *your own* switching cost).
84+
85+
---
86+
87+
## 7. Roadmap — phased, milestone-gated
88+
89+
Each milestone is a thing you can actually run and judge. Because AI writes most of the code and you direct, every milestone ends in a review gate where you try the build and we course-correct.
90+
91+
**M0 — It builds and it's ours (foundation).**
92+
Clone/fork Code-OSS, get a reproducible macOS build, replace `product.json` with Atom++ branding, strip MS telemetry, repoint gallery to Open VSX, ship custom icon + title bar. *Exit test: a signed Atom++.app launches on your Mac, installs an extension from Open VSX, and has zero Microsoft branding.*
93+
94+
**M1 — Notepad++ power-editing.**
95+
Build the Notepad++ Pack: macro record/replay, big-file mode, encoding/EOL controls, column-mode extras, line ops. Add the NPP keymap preset. *Exit test: open a 500 MB log, record a macro to reformat lines, replay it, switch encoding — all smooth.*
96+
97+
**M2 — Native AI core.**
98+
Provider abstraction + BYO-key (Claude first), inline completions, codebase chat, accept/reject AI diffs. Direct-to-provider, no backend. *Exit test: tab-complete a function, ask the chat about your repo, refactor a file via AI diff — using your own API key.*
99+
100+
**M3 — Hackability + Atom feel.**
101+
Settings UI, user init script, package generator + hot reload, theme studio, One Dark-derived default theme, VS Code/Atom settings import. *Exit test: import your current VS Code setup, write a tiny package, restyle a color live.*
102+
103+
**M4 — Agentic AI + Mac polish + release prep.**
104+
Agentic multi-file tasks with approval gates; native menus, traffic-light polish, cold-start optimization; auto-update channel; final name + original logo + trademark check; first public/personal release. *Exit test: give it a multi-file goal and approve its plan; the app feels native and updates itself.*
105+
106+
A realistic ordering note: M0→M2 is where you stop wanting to switch editors. M3–M4 is what makes it *award-worthy* and shareable.
107+
108+
---
109+
110+
## 8. How we actually work (AI builds, you direct)
111+
112+
Because you're directing rather than typing, the process is spec-and-review, not line-by-line:
113+
114+
For each milestone we write a short spec (what it does, how you'll test it), the AI implements it on a branch, you run the build and try the exit test, and we iterate from your feedback. We keep a clean rebase relationship with upstream VS Code so we can pull their improvements — **this ongoing rebase is the single biggest long-term maintenance cost of any fork, and we design our changes to minimize merge conflicts** (isolate Atom++ code into clearly separated modules rather than scattering edits through core files). Each milestone gets its own verification: build succeeds, exit test passes, and for the AI/editing features, automated tests where practical.
115+
116+
---
117+
118+
## 9. Risks, honestly
119+
120+
The fork **rebase treadmill** is real — VS Code moves fast; we minimize pain by isolating our code. **Proprietary-extension gaps** (C/C++, Pylance, Remote) will frustrate some workflows; we line up open replacements up front. **Building the editor from source** is heavy (large toolchain, long builds) — M0 exists precisely to de-risk this before we invest in features. **Trademark** on "Atom" must be resolved before public release. And **scope** — the temptation is to do everything; the milestone gates exist to keep each step shippable.
121+
122+
---
123+
124+
## 10. Immediate next steps
125+
126+
1. Confirm we can locate your synced Atom and Notepad++ sources from the build environment (they'll be our reference for feel and feature behavior).
127+
2. Stand up M0: fork Code-OSS, first clean build, Atom++ branding via `product.json`, Open VSX gallery.
128+
3. In parallel, I read Void's source to lock the AI-layer architecture before we write ours.
129+
4. Pick a working repo + license (MIT, matching Code-OSS) and a codename so we're not blocked on the final name.
130+
131+
When you're ready, say the word and I'll start M0.

‎README.md‎

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
# Atom++
2+
3+
The hackable, AI-native, Notepad++-powered code editor for macOS — a Code-OSS fork.
4+
5+
> **Status: M0 (foundation).** This repo holds the Atom++ *branding overlay and build kit*, not a copy of the editor source. `scripts/bootstrap.sh` fetches Code-OSS at a pinned version and turns it into Atom++. The full vision and roadmap live in [`PLAN.md`](./PLAN.md).
6+
7+
## What this repo is
8+
9+
We don't vendor the VS Code source. Instead we keep a thin overlay that is applied on top of a clean Code-OSS checkout, so we can cleanly rebase onto new upstream releases. This repo contains:
10+
11+
- `branding/product.overlay.json` — the Atom++ identity (name, bundle id, URL protocol) and the **Open VSX** gallery wiring, deep-merged onto upstream `product.json`.
12+
- `scripts/` — `bootstrap.sh` (clone + brand + install), `run-dev.sh` (launch from source), `build-macos.sh` (produce `Atom++.app`), `apply-branding.mjs` (the merge logic).
13+
- `docs/` — the M0 runbook and exit-test checklist.
14+
15+
## Quick start (on your Mac)
16+
17+
```bash
18+
# Prereqs: Xcode Command Line Tools, Node 20+ (nvm recommended), Python 3.
19+
./scripts/bootstrap.sh # clone Code-OSS @ pinned tag, apply Atom++ branding, npm ci
20+
./scripts/run-dev.sh # sanity-check: launches Atom++ from source
21+
./scripts/build-macos.sh # produce Atom++.app
22+
```
23+
24+
See [`docs/M0-RUNBOOK.md`](./docs/M0-RUNBOOK.md) for the full walkthrough and [`docs/EXIT-TEST.md`](./docs/EXIT-TEST.md) for how we know M0 is done.
25+
26+
## Why a fork (and the rules)
27+
28+
Code-OSS is MIT-licensed and free to fork. Two hard constraints we honor from day one: the **Microsoft Extension Marketplace is off-limits** to non-MS products, so we use **Open VSX**; and **"Atom" is a trademark**, so the name here is a working codename until a final name + original logo are chosen. Details in `PLAN.md` §2.
29+
30+
## License
31+
32+
MIT — see [`LICENSE`](./LICENSE). Not affiliated with Microsoft.

‎branding/product.overlay.json‎

Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,51 @@
1+
{
2+
"_comment": "Atom++ branding overlay. This is DEEP-MERGED onto the stock vscode/product.json by scripts/apply-branding.mjs. Keep it minimal — only the keys we intentionally change. Do not paste a whole product.json here; merging keeps us compatible across upstream versions.",
3+
4+
"nameShort": "Atom++",
5+
"nameLong": "Atom++",
6+
"applicationName": "atom-plus-plus",
7+
"serverApplicationName": "atom-plus-plus-server",
8+
"serverDataFolderName": ".atom-plus-plus-server",
9+
"dataFolderName": ".atom-plus-plus",
10+
"darwinBundleIdentifier": "net.systemu.atom-plus-plus",
11+
"win32AppUserModelId": "SystemU.AtomPlusPlus",
12+
"win32MutexName": "atomplusplus",
13+
"win32DirName": "Atom++",
14+
"win32NameVersion": "Atom++",
15+
"win32RegValueName": "AtomPlusPlus",
16+
"win32AppId": "{{EA2A1F4B-0000-0000-0000-ATOMPLUSPLUS}}",
17+
"win32x64AppId": "{{EA2A1F4B-0001-0000-0000-ATOMPLUSPLUS}}",
18+
"win32arm64AppId": "{{EA2A1F4B-0002-0000-0000-ATOMPLUSPLUS}}",
19+
"win32UserAppId": "{{EA2A1F4B-0003-0000-0000-ATOMPLUSPLUS}}",
20+
"win32x64UserAppId": "{{EA2A1F4B-0004-0000-0000-ATOMPLUSPLUS}}",
21+
"win32arm64UserAppId": "{{EA2A1F4B-0005-0000-0000-ATOMPLUSPLUS}}",
22+
23+
"urlProtocol": "atom-plus-plus",
24+
"quality": "stable",
25+
26+
"licenseName": "MIT",
27+
"licenseUrl": "https://github.com/systemu-net/atom-plus-plus/blob/main/LICENSE",
28+
"reportIssueUrl": "https://github.com/systemu-net/atom-plus-plus/issues/new",
29+
30+
"enableTelemetry": false,
31+
"telemetryOptOutUrl": "",
32+
"aiConfig": {
33+
"ariaKey": ""
34+
},
35+
36+
"extensionsGallery": {
37+
"serviceUrl": "https://open-vsx.org/vscode/gallery",
38+
"itemUrl": "https://open-vsx.org/vscode/item",
39+
"resourceUrlTemplate": "https://open-vsx.org/vscode/unpkg/{publisher}/{name}/{version}/{path}",
40+
"controlUrl": "",
41+
"recommendationsUrl": ""
42+
},
43+
44+
"linkProtectionTrustedDomains": [
45+
"https://open-vsx.org"
46+
],
47+
48+
"_atomPlusPlus": {
49+
"note": "Namespace reserved for Atom++ feature flags (M1 Notepad++ pack, M2 AI core, M3 hackability). Upstream ignores unknown keys, so this is a safe place to carry our config across rebases."
50+
}
51+
}

‎docs/EXIT-TEST.md‎

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
# M0 Exit Test
2+
3+
M0 is complete when **all** of these pass on your Mac. Check them off.
4+
5+
### Build & launch
6+
- [ ] `./scripts/bootstrap.sh` completes with no errors.
7+
- [ ] `./scripts/build-macos.sh` produces **Atom++.app**.
8+
- [ ] Atom++.app launches and opens a folder.
9+
10+
### It's ours, not Microsoft's
11+
- [ ] Window title / Dock / `About` all read **Atom++** (no "Visual Studio Code" / "Code - OSS").
12+
- [ ] Bundle identifier is `net.systemu.atom-plus-plus` (verify: `mdls -name kMDItemCFBundleIdentifier Atom++.app`).
13+
- [ ] Telemetry is off by default (Settings shows no MS telemetry; `enableTelemetry` is `false` in `vscode/product.json`).
14+
- [ ] Custom URL protocol works conceptually: `product.json` `urlProtocol` is `atom-plus-plus`.
15+
16+
### Open VSX, not the MS marketplace
17+
- [ ] Extensions view loads results from **Open VSX** (search e.g. "Python" returns results; the gallery URL in `product.json` points at `open-vsx.org`).
18+
- [ ] Installing one extension from Open VSX succeeds and it activates.
19+
20+
### Hygiene
21+
- [ ] `vscode/product.json.vanilla` exists (pristine upstream copy for diffing).
22+
- [ ] `.vscode-pinned-tag` records the upstream version we built from.
23+
- [ ] `git status` in this repo shows the `vscode/` checkout is gitignored (not accidentally committed).
24+
25+
When everything above is checked: **M0 done.** Next is M1 — the Notepad++ power-editing pack (macros, big-file mode, encoding/EOL, column extras).

0 commit comments

Comments
 (0)