Every web build we deliver is designed, published and handed over in Terminal.
Start a projectNeed a person? Support replies within one business day.
SupportStackIDE is the Stacklumen desktop app for Mac and Windows. Every site, its content and its clients, your code and git, a real terminal and the coding agents you already use, in one window that stays in step with the web.
A short demo of StackIDE, the Stacklumen desktop app, plays: Northgate's home page opens in the editor and a terminal opens in its folder; Claude Code, started from the Agents panel, tightens the hero heading and adds a call to action, and the open file updates; the heading is rewritten and saved, and the Designer tab shows it live; the status bar's Publish button puts Northgate live, step by step.
Sections down the left, every site and file beside them, one strip of tabs for everything you open, your terminals under it, your agents on the right, and a status bar that always knows what’s saving.
StackIDE with the Agents panel open: Claude Code runs in a terminal in Northgate's folder, tightens the hero heading and adds a call to action, and the open file shows the new heading.
Point at a part of the window, or choose one below. Choose a part below.
Sync a site to a folder and it becomes plain files: a page per HTML file, one stylesheet, each page’s own code. Save in any editor and the designer has it within seconds; edit in the designer and the folder follows.
When you and the designer change the same lines, the site keeps its version and your copy is saved in .stacklumen/conflicts first, with a notification.
Syncing merges Stacklumen’s MCP server into the folder’s .mcp.json, never overwriting it, so an agent started there finds it without being told.
An edit made while StackIDE was closed is still an edit when it opens. On a Mac, folders keep syncing with the window closed, until you quit.
Terminals are your own login shell, side by side under your tabs. The Agents panel finds the coding agents on your computer and starts the one you choose in the folder you’re working on — in a synced site’s folder, already connected to Stacklumen.
A short demo of StackIDE, the Stacklumen desktop app, plays: Codex, started from the Agents panel, asks Stacklumen's publish checks what the Work page is missing, adds alt text to its three images, and the open file updates.
StackIDE never talks to an AI model and holds no AI key: it starts your own agent, with your own sign-in and plan. How agents work in StackIDE
Open any folder on your computer: an editor for HTML, CSS, JavaScript and TypeScript, JSON, Markdown, Python and YAML, diffs side by side or in one column, and git’s everyday loop — branch, stage, commit, pull and push.
Git runs in the folder with your own PATH, credential helpers and SSH keys, so a push signs in exactly as it does from your shell.
StackIDE never discards, resets or force-pushes anything. Those stay in a terminal, where you type them yourself.
The tree and the diff follow the files as an agent or a branch switch changes them, and an unsaved edit is never overwritten without asking.
Clone a Cloud app to ~/Stacklumen, run its dev server here and inspect it to the line of source. Ship for review opens a pull request with its own preview; Merge & deploy puts live exactly what was previewed.
A short demo of StackIDE, the Stacklumen desktop app, plays: the command palette opens Cloud, where Northgate portal is cloned, run on the computer, previewed at tablet and phone widths, inspected to its source, changed, shipped for review and merged live (Cloud is by application; this workspace is approved).
Cloud deploys are by application. While we set the company up, a workspace asks and Stacklumen approves; until then StackIDE holds New app, Deploy and Merge & deploy, and says where the request stands. Cloning and running apps on your computer stay open. Cloud in the docs
Pulse, Content, Brand, Clients, Inbox and Developer are StackIDE’s own screens over the same API the web uses: the same roles, the same staging, the same publish.
A short demo of StackIDE, the Stacklumen desktop app, plays: Pulse counts up the week's work, draws each site's uptime and takes a new form submission.
⌘1 to ⌘9 walk the rail, ⌘K finds any site, tab, agent or command, and the terminal and the Agents panel fold in and out with a key. Every key
⌘ Command · ⌃ Control · ⌥ Option · ⇧ ShiftOn Windows, ⌘ and ⌃ are both Ctrl
An app that holds your session, your folders and a terminal has to earn its place. What it may touch, and how it proves it’s ours, is written down. Security and storage
Mac builds are signed with a Developer ID and notarised by Apple, so Gatekeeper opens them like any app you download.
The Windows installers are not code-signed yet, so SmartScreen may ask the first time. The download page prints every installer’s SHA-256 to check it against.
A key pair made inside the app seals the handoff. The token lasts two minutes, and only the app that asked can open it.
Your session is encrypted on disk with a key your system keeps — on a Mac, in the Keychain. Signing out clears it entirely.
Stacklumen’s pages run sandboxed and isolated, and only its own addresses open inside the app. Everything else opens in your browser.
Files are read and written only inside folders you synced or opened in Code, every path checked after following links.
A Cloud app’s preview runs in its own session: no Stacklumen cookies, no permissions, only addresses on your own computer.
New versions download in the background and install when you press Restart to update, or the next time you quit.
Sign in on the download page and it offers the build for your computer first, then every installer with its size and fingerprint.
On 0.1.4 or older? Builds before 0.1.5 weren’t signed, so they can’t update themselves: download the current version once, and every update after it installs itself.
If Windows says “Windows protected your PC”, choose More info, then Run anyway. Check the installer’s fingerprint against the download page first.
It installs as “Stacklumen” for now, and takes the StackIDE name in an update. There is no Linux build, and StackIDE needs a connection: Stacklumen’s pages in its tabs are served live.
What every button does, every key, and every message you might meet, read off the app’s own source.
It is the same Stacklumen account and workspace, in one window. The designer, a site’s dashboard, a client’s full profile and chat threads are Stacklumen’s own pages in tabs, so what you do there is exactly what happens on the web, and they update when Stacklumen does. Pulse, Content, Brand, Clients, Inbox, Developer, Code and Cloud are StackIDE’s own screens over the same API. What a browser tab can’t do — a real terminal, folders kept in step with your sites, git, your coding agents and Cloud apps running on your computer — is what the app adds.
StackIDE is the app’s new name, and the installed app takes it in an update. For now it is called Stacklumen in Applications, the Dock and the Start menu, in its window and its menus, and Settings → About reads “Stacklumen Desktop”. It is the same app.
Nothing extra during the private alpha: StackIDE comes with your Stacklumen account. Downloads are for signed-in accounts, and what you can do in the app follows your workspace’s plan and your role, the same as on the web.
Claude Code, Codex, Gemini CLI, Cursor Agent, Copilot CLI, opencode, Amp, Aider and Goose. StackIDE finds the ones installed on your computer and starts the one you choose in a terminal, in the folder you choose, with your own sign-in, plan and settings. Agents you haven’t installed are a link away.
No. StackIDE never talks to an AI model and holds no AI key. It starts your own agent by its command name, from a fixed list, and reads the chats your agent keeps on your computer without changing them. An agent started in a synced site’s folder finds Stacklumen’s MCP server in the folder’s .mcp.json.
Not yet. Until it is, SmartScreen may say “Windows protected your PC” the first time: choose More info, then Run anyway. The download page prints each installer’s SHA-256, and checking it is how you tell our copy from any other. Mac builds are signed with a Developer ID and notarised by Apple.
Builds before 0.1.5 weren’t signed, and a Mac only installs updates into a signed app. Download the current version from the download page once; from then on, updates download in the background and Restart to update appears in the status bar.
Terminal Cloud deploys are by application while we set the company up: a workspace’s owner or admin asks, and Stacklumen approves. Until then, StackIDE’s Cloud shows where the request stands and holds New app, Deploy and Merge & deploy. Cloning an app and running it on your computer work either way.
On Stacklumen, as on the web: sites, content, clients, chat and your account. On your computer are the folders you chose, your session (encrypted) and the app’s own few settings, such as window size and theme.
There is no Linux build. StackIDE needs a connection, because Stacklumen’s pages in its tabs are served live. Folder sync waits and tries again while you are offline, and an edit made while the app was closed is still sent when it opens.
StackIDE for Mac, Apple silicon or Intel, and Windows. Sign in with your Stacklumen account to download.
Private alpha · Installs as “Stacklumen” for now · Mac builds signed with a Developer ID and notarised by Apple