Product updates from Stacklumen, newest first: Terminal, the Hub, Stacklumen Base where it meets them, and
stacklumen.com itself. What comes next is on the roadmap.
The Agency plan covers the Hub, Terminal and StackIDE, now with five editor seats and three workspaces, and Baselumen is its own product, bought on the same account on any plan. Two add-ons arrive with it: Client payments, for invoices and retainers your clients pay by card, and Advanced analytics, for any site.
Invoices in the Hub: numbered invoices from scratch, a CRM quote or unbilled time, with reminders and receipts, retainers that charge a saved card each month, quarter or year, and an overview of what is owed
Clients pay an invoice or start a retainer by card inside their portal or from the emailed link, straight into your own Stripe account
Advanced analytics gives a site its own Analytics page: visitors, sources, campaigns, goals, funnels and the last 30 minutes, counted without cookies, and shared with the client when you choose
Every site keeps its free page counts, now with campaign tags and without crawlers or 404 probes
An agency on an earlier plan keeps its price and everything it has until a renewal at least 30 days after we write to it
Pricing, the docs and the terms (version 3.7) say all of this
A Design site’s GitHub panel now only imports. Import pages reads your repository into the designer, and from then on the pages are the site’s while your repository keeps its own history: Stacklumen reads it and never writes to it.
Re-import latest commit reads the branch again whenever you like, and replaces the pages it made
Push, Pull and sending visual edits back as a pull request are gone
Any repository you can read links to a Design site: it needs no write access
Download code gives the site as plain HTML, CSS and JavaScript, and StackIDE’s Sync to folder keeps its files in a folder on your computer
A Code site is changed on your own computer, in StackIDE or any editor, and pushed with your own git to wherever you choose. Stacklumen never commits, pushes, opens or merges a pull request, or makes a repository or a branch, and Cloud deploys what you push to the site’s branch.
A Code site’s overview opens it in StackIDE and shows its repository, its branch and where Cloud has it live
Link any repository you can read: a Code site needs no write access
Cloud deploys every push to the site’s branch, and Deploy latest commit builds the branch’s newest commit whenever you like
Agents connected to Terminal work on a Code site’s CMS, forms, settings and Cloud, and edit its code where it lives, on your computer
Every site can hold collections and items on any plan or none. A site plan now buys what the CMS is for: Content API keys come with the CMS or Premium site plan, and pages that show CMS content publish on Premium.
A site holds up to 10,000 items and 200 collections, whatever its plan
Publish item puts an item live at once on production Content API keys and, on Premium, on the published pages that show it
Deleting an item takes it off the Content API at once, and off a Premium site’s published pages too
Pricing, the FAQ and the docs say what each site plan buys
Notes on your site, in a client’s portal, opens their published site full size. They click a spot, say what should change, and it reaches you as a client request that names the page and what they clicked.
Each note shows as a numbered dot on the page, in the same place on a phone, a laptop and your screen, with its status beside it
What you asked them to approve about the site sits at the top, approved or sent back right there
Your Client requests inbox shows where each note was pinned
Send clients their week, and walk them through new work
Hub
Each client’s week, their visits, form entries, orders and updates against the week before, and what was finished for them, can be sent to their people from StackIDE. In their portal it opens as “Your site this week”.
Clients see their own sites and a count of the work done, never your task titles
The week also opens on its own once a week in the portal when there is something to show
Record a walkthrough of your screen and voice in StackIDE, and it plays at the top of the client’s portal
The first time you open Stacklumen each day, a short brief walks you through your wins since you last looked, what could use a hand, and what today holds.
Mondays add the week just gone, set against the week before
A site’s first publish, its own domain going live, a new member joining and an upgrade each get a moment of their own, once
A client sees their site’s launch day in their portal
Hand a finished site to your client, move one between your own workspaces, or pass it to another agency, from the Transfer card in its Settings. Nothing moves until the other side accepts.
The site moves whole: pages, CMS, files, forms and their submissions, History and its custom domain, and its published site stays live while it moves
The other side gets an email with a link, chooses which of their workspaces it goes into, and can make an account then if they need one
Ask to stay on as an editor, so you can keep working on a site you handed over
Store orders and client bills stay with you as a sales record you can download from Transfers
An agent connected over MCP can now store a file it made itself, such as an image it rendered or a chart, by asking for an upload link with create_upload_link and sending the file to it from its own shell.
A link takes one file for 15 minutes, for one site, with no other sign-in, and the file never passes through the conversation
Files are checked and stored by the same rules as upload_asset: images, video, audio and captions, reused when the site already holds the same file
Every Hub screen and every screen of Terminal's dashboard now opens on a phone or a tablet, laid out for the width it has. Only the designer still asks for a bigger screen.
Add Stacklumen to your home screen and it opens like an app: full screen, on your dashboard, with the same icon
stacklumen.com/mobile shows how to add it, step by step and animated, for Safari, Chrome, Firefox, Edge, DuckDuckGo, Brave and Samsung Internet on iPhone, iPad and Android
On a phone the top bar keeps search, the agent, what needs you, the bell and your account; help, the roadmap, the other apps, light and dark, and refresh move into the account menu
Figures pair up, tables scroll sideways inside their panels, and fields no longer zoom the page when you tap them
A site whose CMS is read from your own code through the Content API now carries a blue CMS badge, and no longer reads as a draft because its own pages were never published.
Such a site whose pages were never published shows CMS in place of Draft, and one whose pages are live shows Live beside CMS
These sites count as live in the Overview, the Sites list and its filters, the Hub and a client’s profile
The site’s own Overview says its CMS is read from code, with no publish step to take
Publishing a site’s pages is never needed to use its CMS through the Content API
Three site plans, and a CMS tag on sites read from code
Terminal Hub Website
Sites now have three plans: CMS for content only, Basic for a site on its own domain, and Premium for a site on its own domain that runs on its content.
The CMS site plan gives a site Content API keys, while its own pages stay on staging: for a site’s CMS read from your own code
Premium is the plan that was called CMS until now, so nothing changes for a site already on it
A site’s Settings offers Staging, CMS, Basic and Premium, and the Hub’s Billing sells and counts all three
A site whose CMS is read from code, with a live content key of its own or on the CMS site plan, carries a CMS tag beside its state on the Overview, Sites, the Hub and a client’s profile
Pricing, the FAQ and the docs describe the three plans
Code sites: a site built from its GitHub repository
Terminal Hub
A new site now starts by asking how it’s built. Design is the visual designer, as every site is today. Code makes your GitHub repository the site, and you edit it in StackIDE.
A Code site is made from one of your repositories, on the branch and folder you choose, and Terminal reads whether it is an Astro, React, Next or plain HTML project
Its overview shows the repository, the branch and its latest commits, with Open in StackIDE as its main action
The CMS, forms, domains and the Content API work for a Code site as for any other, and its pages stay in the repository: the designer never opens one
New Design copy imports a Code site’s repository into a new Design site. Nothing is converted in place
Agents connected to Terminal get the CMS, forms and settings tools for a Code site, and a plain answer from the design tools
Code sites carry a Code badge on the Overview, Sites and Hub screens
Importing a repository into a Design site still works, one way
stacklumen.com/cms shows everything Terminal’s CMS does, from its sixteen field kinds and staged publishing to the Content API, with live demos of the editor, a request and its JSON, translations and an agent setting it all up.
A demo of the CMS editor leads the page: an item added, written, published and edited again, its status moving with it
The Content API section switches between a production and a development key, so you can see what each one serves
The page reads this site’s own blog from the CMS as it renders, the way any front end would
Resources in the menu, the command palette and Terminal’s page link to it
The blog is redesigned, and runs on Terminal’s CMS
Website Terminal
stacklumen.com/blog now reads every post from Terminal’s CMS through the Content API, the way any headless front end would, and has a new design to read them in.
Every post, old and new, is an item in the Stacklumen site’s blog collection, with its cover in that site’s assets. A published edit shows on the blog within about five minutes, with no deploy
The front page leads with the newest featured post, then every other post in a grid you can narrow by topic or search. Press / to search from anywhere on the page
A post has a contents rail that follows your reading, a reading progress line, sharing, the posts either side of it and three more to read
Posts show their date and read time, and the blog has an Atom feed at stacklumen.com/blog.xml
The command palette finds every post
Ten new posts: five on what shipped this month, and five on the news in software and the web
Safer saves when two people edit, and faster editing on big sites
Terminal
When someone else saved a site while you were editing, Keep mine now merges page by page: your pages win, and their version of any page you both changed is kept in History.
Keep mine works on sites of any size, and a banner names the pages where both of you made changes
A designer tab left open from before an update asks you to reload rather than saving over newer work, and keeps what you typed for after the reload
History shows who wrote each version, including an agent by name, and keeps a copy before anything an agent removes
Typing in a navbar or footer shared across many pages stays instant, and the other pages catch up when you pause
A class edit on a large page redraws only the elements that wear it
A page published from a site your workspace does not edit pastes in as a look only, while your own published pages still come back whole
The designer on the web is now the visual editor. Open in StackIDE, at the foot of its rail, opens the site’s code in StackIDE, the desktop app, on the page you were on.
Open in StackIDE is also in the right-click menu and the command palette, for anyone who can edit the site
The first time, StackIDE asks for a folder to keep the site in; after that the site opens straight away
Code ↗ is gone from site cards and site pages, and GitHub stays in the designer under Developers
Navbars, mega menus and dropdowns behave exactly like their code
Terminal
Menus in Terminal now open, fold and respond the way their HTML and CSS say, on the canvas and on the published page alike. Code that arrives as a menu, a dialog, a switch, an accordion or a carousel becomes the native element, and the canvas and the Inspector read your CSS exactly.
A navbar folds at Laptop, Tablet, Phone or any width you choose, never makes the page zoom, and shows its logo, a 36px menu button and its call to action at the top of the open phone menu
The open phone menu holds the page still behind it, a tapped dropdown inside it opens without closing it, and Escape closes the innermost menu first
Mega menus stay open as the pointer travels to their far columns, line up with the bar at any width, and turn back into dropdowns
The Menu section builds sub-menus and sets each dropdown’s own open on, caret, delays and motion, its open and current-page looks, and how a link counts as the current page; O shows the selected menu open on the canvas
A menu added on one page’s copy of a shared navbar reaches every page that shares it
Imported menus keep how they opened: a click menu stays a click menu, and hover comes only from the page’s own hover rules. Dialogs, switches, accordions and scroll-snap carousels from code become the designer’s own widgets
Pasting or importing a whole page keeps the scripts around its markup, its inline drawings, media-scoped styles and its <html> and <body> attributes, and your own published pages import back almost exactly
Repository write-back carries edits to imported rules, breakpoints, states and images into the pull request, keeps one open pull request per site, and never proposes a file that would not build
On large pages a nudge, a zoom step or a selection change now takes a millisecond or two, and a held arrow key stops when you let go
The Inspector reads the rule that really decides each value, including rules written with :is() and :where(), selectors with escapes, and dark-mode colours on the Dark canvas
Contact forms with a search-style field send to your inbox, slider dots and controls are easier to tap, and an accordion or tab set opened inside a section grows the section to hold it
Agents can set every menu option through menu_edit, and their saves write only the pages they changed and leave a restore point first
An open menu rises above a sticky bar that follows it, unless your own CSS deliberately puts that bar on top
The desktop app is StackIDE, and its Mac builds are signed
Suite-wide Terminal Website
The Stacklumen desktop app for Mac and Windows is now called StackIDE, with its own page at stacklumen.com/ide. From version 0.1.5, Mac builds are signed with a Developer ID and notarised by Apple, and they update themselves.
StackIDE puts your sites, content, brand kits, clients, inbox and code in one window, with a terminal, two-way folder sync and an Agents panel that starts the coding agents you already use
On a Mac, an update now downloads quietly and Restart to update appears in the status bar. On 0.1.4 or older, download the current version once by hand
Windows keeps installing its updates itself. Its installers are not code-signed yet, so SmartScreen may warn the first time
The app still calls itself Stacklumen on your computer until an update renames it
Terminal’s code view is now called Code, and Code ↗ replaces IDE ↗ on site cards, so IDE only ever means StackIDE. Its addresses are unchanged
The account menu’s link to the desktop app, and the bell and email that announce a new version, say StackIDE
StackIDE comes with every account during the private alpha, and the download page, the docs, pricing, hosting, security, the FAQ and the about, ecosystem and Hub pages describe it
Custom domains and Terminal Cloud are by application for now
Terminal Website
While the company is set up, a workspace asks for custom domains and for Terminal Cloud, and staff approve the request. Staging addresses work for everyone as before.
Ask from a site’s Settings, under Custom domains & Cloud, or from Cloud’s page: the business, its website, how many, what will be hosted, and the acceptable use policy
Domains and Cloud show where the request stands, and hold their save and New app until it is approved
Reading, clearing a domain, pausing, rolling back and deleting are never held back
An approval, a decline or a switch-off is told to the workspace’s owners and admins by bell and email
Imported mega menus, frames and page icons come across intact
Terminal
The importer is now version 14. Mega menus that a page’s own script opened become native dropdowns, and frames, icons and share images keep working on the imported site.
A script-opened mega menu opens step for step as it did before, in Preview, on the published site and on the canvas: the bar holds it as focus moves along, and the pointer switches between open menus
On the canvas those menus rest closed and open when you press their button, in their own look
A script that did nothing but open the menus is switched off once they are native
An iframe, object or embed that loaded from the old site loads from where the site is now served
A page’s icons and share image are copied with its images, or pointed at where the old site serves them, and fill its head code and SEO fields
A page imported with an earlier importer is offered a refresh to pick these up, and a re-import mends a share image that came across as a bare path
Writing edits back to the repository never proposes these new addresses as changes
The preview on each site card in the dashboard is rendered once for each version of the site and then kept by your browser, so the dashboard and the projects list fill in quickly.
A card only renders again when the site has changed since its last preview
Images and video below the top of a preview load only when needed
You can now put a published site on your own domain. Add the domain in the site’s Domains settings, prove it with a TXT record, and it is served with its own certificate.
The domains screen, the Terminal docs, the learning paths and the hosting, web and pricing pages describe how it works now
A saved domain now shows as the domain itself with three steps to connect it. Each DNS record is checked on its own and the page says exactly what to change
Every record is marked found, missing, wrong, extra or under the wrong name, with the fix beside it
Copy sits on every name and value you need to paste at your DNS provider
A live line checks the domain every 15 seconds by itself, and says when the record is right but the domain is not serving yet
The www version of a domain is attached and redirected for you, and every record stays in view while you work
One CMS picker now binds everything an element can read from an item. Text, images and sources, links, alt text, backgrounds, attributes, colours, classes and visibility all bind the same way.
The picker offers the item’s fields, a referenced item’s own fields and page, and system values such as the item’s address and dates
A bound row shows as a chip, with what it shows when the field is empty and a date or number format
A bind with nothing in it shows nothing by default; When empty can keep the design or hide the element instead
A class can be added when a field is set, and an element shown only under a condition
Broken binds, a deleted collection, a list and its empty state are each listed with a way to fix them
Outside a collection the group offers the template page or a Collection list, inside a component it says a bind reaches every copy, and a bind lands on every selected element that can show it
The repeating-sections lesson and exam in Learning describe the new empty rule
Filter by a relative date, and format dates and numbers
A heading keeps its tag around a block of rich text
Each card in a list keeps its own tabs, answers and labels
The canvas draws a list’s cards where they will publish, with lists inside them filled in
The canvas preview holds back the items a publish would, such as drafts and items that break a field’s rules. The CMS editor still shows every item
Site cards on the dashboard and the Design screen on your phone show a site’s CMS content, including item pages
The Style tab reaches every state and edits imported rules in place
Terminal
The Style tab now writes every state at any breakpoint, and a value that comes from an imported stylesheet is edited in that rule by default.
Open a pseudo-element, a new rule or a new media query before the stylesheet has one
A Lists, tables & forms group styles list markers and the properties of tables, cells and form controls
Rules under @supports, @container, a second @media and :where() are listed and editable
A closed component’s placement can be styled, and the tab says the change applies to every placement
When an edit loses to another rule, the tab names that rule and offers Edit that rule
An imported rule shows its selector, widths and layer, and an in-place edit lasts until the stylesheet is imported again; overriding on the element is still offered
On the Focus tab a class’s :focus-visible rule is edited where it is written
Grid cells size by their CSS, an inset can take its axis from the frame, and an inherited Custom CSS line can be deleted where it is set
Styles can be set for ten states and four pseudo-elements, at the base and at every breakpoint, and layout reads whichever style actually wins
A class’s flex or grid places its children on the canvas as it will on the page
A class edit that a more specific rule outranks is still saved, and the Inspector names the rule that wins
Aligning an element that its own insets place moves it by those insets, as dragging does
The Settings tab handles media, attributes and dropdowns properly
Terminal
Replacing an image in Settings now takes its responsive sources, size and alt text with it in one step. Attributes, dropdown options and media sources each get controls of their own.
An alt text written for the old image is pointed out when the image changes
A picture’s and a player’s sources and captions are listed with ways to add more, and a video or poster can be picked from the library or uploaded
A dropdown’s values, chosen option, order and groups are editable
Attributes offers every valid name, shows on/off attributes as switches and gives spans, scopes, preloads, track kinds and referrer policies their own controls
An input lists only the attributes its type uses, and a label or cell can pick the ids it points at
Text beside child elements gets a Lead text field, and files that draw nothing no longer show Mode and Tag
Double-clicking a player or frame opens its own gear, and dragging an image over another outlines the one it will replace
The Components card picks an image prop from the library, edits rich text and link props, and says when a style edit reaches every placement
Scripts name the elements they reach, and interactions get fuller controls
Terminal
A script’s References are now picked on the canvas or from the page’s tree. Each one selects its element and warns when the element has been deleted.
A reference is named after its element, and an imported script’s lookups become references in one press
A script’s kind, imports and data blocks are editable
Widgets list their items with add, remove, move and show
Interaction cards reorder and duplicate, offer an undo value for every attribute they set, and take scroll stops, wrap, modal, prevent, an interval’s period and a selector’s scope
A reveal’s starting look can be drawn on the canvas, and Starts closed sits beside the interactions that open it
A details or dialog element can be previewed open and closed by name
The page’s code view now shows and reads back every part of a page as it is stored, so editing the code changes only what you edit.
Raw markup, element handles, inner sections and element scripts show as written, and widgets and interactions show as read-only code
Text can carry what rich text keeps, a link’s target and rel, a class or a title, and the view says only what it would drop
An attribute typed with an empty value is kept, and text in a textarea, pre or preformatted element stays as typed, leading blank line included
Table rows sit in the tbody the browser would give them, in the code view and on the canvas, so table selectors and row striping match the published page
Repository imports land more faithfully, keep how they behave and write more back
Terminal
The importer is now version 13. Repositories land closer to how they render, and writing edits back covers the CMS, tokens and pages served as built.
A repository with no dark theme of its own lands with dark mode off, and tokens moved into Variables keep their look in both modes
A token changed in Variables is written back where the source declared it, or listed
Every collection a repository configures lands, and one with no page of its own gets a blank template page named after it
A page’s title, description and share card fill its SEO fields, and the rest of its head metadata travels in its head code
A script between two sections keeps its place, even as sections are added, moved or removed
A stylesheet that a component’s script imports is read into the site’s styles, where the canvas sees it
Writing edits back lists CMS changes since the import as steps to take in the repository, and pairs a page served as built with its source so an edit there is written back
Every note the importer writes is filed under a section of the import report
Imported pages now keep their sliders, lightboxes, tabs, animations and media scripts working, converted to native parts where that is safe and left on their original code where it is not
A site-builder export’s sliders, lightboxes and tabs are rebuilt as native widgets on the export’s own markup
A page whose animations need the export’s own runtime keeps that runtime and the library it relies on, so they play as exported
A script loaded from its original host keeps the library it calls
An image’s, video’s or audio’s load and error handlers run as scripts bound to it, including when the media had already loaded or failed
Hand-written arrow-key tabs become native tabs when their keys match the native keyboard behaviour; anything else stays a script
A converted slider’s current dot is announced to screen readers and keeps the site’s own active class
A link that opens in a new tab or carries a title or class stays part of its sentence as rich text
A submit button that sent its form to an outside service keeps doing so, with a copy sent to your inbox
Smooth scrolling and view transitions ship exactly as the source gated them, including for visitors who asked for reduced motion
Dark mode keeps selectors with :is(), :not() or :has() whole, and SVG drawings keep their sprites and animations
The referral partner program now runs in a portal. Partners see their tier, milestones, earnings and payout statements, share a link that credits them, and talk to the team directly.
A partner link credits the partner for anyone who signs up through it
The portal includes a sales kit and a Partner Academy
Partners and the Stacklumen team can message each other from the portal
A partner who accepts an invitation gets the partner portal and nothing else, and an invitation sent to an address that already has an account joins that account
Our policies are rewritten for the whole suite, in a new layout
Suite-wide Website Baselumen
Every policy is rewritten to cover what the products actually do today, and each one is a single document that stacklumen.com and Baselumen show word for word.
Each policy page shows its version, effective date and scope, a short plain-language version and numbered sections you can link to
Pages show reading progress, print or save as PDF, and have a contents menu on phones
The legal index groups the documents and shows which one takes precedence
New documents cover the private alpha and the use of agents and API keys
The Acceptable Use Policy is shorter and states its rules directly
Sign-in and sign-up link straight to the current policies
Each site now stages at its own address, <slug>.stacklumen.live, instead of a path on stacklumen.com. Its links, 404 page, sitemap, redirects and files all live at that address.
The dashboard, the designer, site settings, reports, the showcase, Shared with you, agents and publish emails show the new address
Old staging links forward to the new address
Site settings show the address field as <slug>.stacklumen.live
Each site runs on its own address, so one site’s code can never reach another site or your account
Some names, such as www, api and admin, are reserved and can’t be used as a site’s address
Once a site’s custom domain is live, forms sent from its stacklumen.live address count as staging submissions
The docs, the learning paths, the live demos and Dev Program sites use the new addresses
A rebuilt Forms screen, with settings for each form
Terminal
The Forms tab lists every form the site ships and gives each one its own settings. Submissions open in a drawer, can be filed and deleted in bulk, and show as cards on a phone.
Filter submissions by inbox, spam or all, and by live or staging
A submission opens in a drawer, with its files as secure links
Editors can change a form’s settings, file or delete many submissions at once, and erase everything one person sent by their email address. Viewers don’t see these controls
A form can keep its submissions for a set number of days instead of for good. Older submissions and their files are deleted every day
A form that sends to an outside service keeps a copy in your inbox, marked as a copy. Copies are never filed as spam, never send the automatic reply, and only notify people when the form’s settings ask for it
Copies fire the form.submitted webhook with copy: true
A form’s built-in messages follow the page’s language in French, German, Spanish, Italian, Portuguese and Dutch, and your own words always win
Every new form gets an inbox name no other form on the site uses, and a pasted form keeps its name unless its page already has a form with that name
Agents can list a site’s forms with their fields and settings, read a form’s settings, page through submissions by form, text, folder and environment, change settings and file submissions
The Terminal docs describe forms as they work now, including the inbox, copies, files, spam, settings, notifications, the webhook and the agent tools
A selected form now has a Form group in Settings. It covers the form’s inbox name, its success and failure messages and where it goes after a send
Pick the page a form goes to after a send
Choose whether it sends to this inbox, runs its script first, or sends to its own service with a copy here
The success or failure message can be held open on the canvas to style it
A link opens the form’s submissions, and an imported form shows the address it still names
Every collection can give its items their own pages
Terminal
Making a collection can now make its template page in the same step, so each item gets a page of its own. Lists, collections and Pages all open or make that page.
A new collection gets item pages by default when it is blank, a Blog or a Portfolio, and not when it is a Team. Each preset says which on its button
Every list and collection heading opens its template page, or makes one, and Pages marks template pages and makes one for any collection
Page settings moves a template under its address and picks each item’s search description, share title and share image from the item’s fields
Make repeating turns the cards you drew into the list’s cards in one step, so the published cards stand exactly where your drawn ones did
Deleting a collection with a template page asks whether to keep the page as an ordinary page or delete it
Renaming or deleting a collection says what it will change on the site before it does
Content API items say where their page is on the site
A client you share a site with now previews the site as published, at any page or item it publishes. A site that has never been published says so in plain words.
The Insert panel adds Accordion, Modal, Pricing toggle and Disclosure, and a Form now works the moment it lands, with a field, spam protection, a submit button and a status message.
Tabs, Carousel and Lightbox arrive with their look in the same step
New form parts: Email, Phone, Date, Fieldset group, Hidden field and Submit button
Table, Description list and Audio are offered
Collection list asks which collection to show
An insert aimed at a hidden container lands where you can see it, and says so
Button labels, textarea text and placeholders are typed straight on the canvas, and text editing keeps exactly what you type.
Enter starts the next paragraph or list item, and no-break spaces and preformatted text stay as typed
A format bar offers what rich text keeps, and the link field sets a new tab and rel or edits the link already there
Files dropped from your desktop are uploaded and placed, or replace the image they land on
The image gear replaces an image with its srcset, size and alt text, and opens on a double-click
Dialogs, details, sliders and script-driven tabs open on the canvas while you work in them, and form controls no longer toggle when clicked
Text edits on the canvas no longer disturb what is around them. Clicking into text and away again changes nothing, and links, icons and spacing inside the text survive an edit
Wrap, unwrap and grouping refuse markup a parent cannot hold, with a sentence that says why
Copies are real copies, with their own names, links and script targets
An edit inside a component instance selects the instance, and a pasted instance is rebuilt from the live component
Tabs, slides, accordion items and toggle options can be added, removed and moved in one step
A paste aimed at a collection list lands in its card
A link on the canvas now wears its own orange frame and tab. Its gear edits the address and the new-tab setting in place
Links read orange in the Layers tree too, tag and name, while a linked block keeps its violet
The gear’s popover opens below the link, or above its tab, instead of covering the words it edits
The component card is more compact and keeps clear of the link popover, and the rail’s icons use a lighter line
The right-click menu, keys and Layers act on the whole selection
Terminal
Copy, cut, paste, duplicate, delete, wrap and group now work on everything you have selected, and an action that can’t be done is greyed out with the reason.
Paste styles applies a copied look at the width you paste it at: everything at the base, only that layer’s own look at a breakpoint
Layers drags a multi-selection, never offers a nesting that won’t hold, and marks bound, referenced and hidden-at-this-width rows
A paste selects what it made, and pasting again places the next copy after it
A component pasted from another site is saved to this site’s components under a free name, with a notice naming it
List items hold their words and a sub-list, and Nest in a list moves an item under the one above it
Every way of placing an element checks the nesting rules and explains a refusal in plain words
A cut pastes back as a move, undo history keeps a multi-selection, and folds and page switches keep Redo
Deleting never leaves a reference to a missing element, and a custom element keeps its attributes through a tag change
A template page can be previewed with a chosen item, in the bar and in Preview
Cut and paste moves an element instead of copying it, and Copy styles takes the look on the clipboard
A list item can be moved out of its list from the right-click menu
A dragged widget brings its look, and a dragged form its own name
The CMS editor can make template pages, and previews show exactly what a publish would
In an artboard zoomed to a visitor’s screen, viewport widths measure what they do on the published page
A list’s template stays visible while designing when its first item’s value is empty
Published pages ship exactly as designed, with more publish checks
Terminal
A round of fixes makes the published page match the canvas, and the publish checks now catch many more problems before they ship.
A section hidden at a width hides all of it, and styles written for a section’s children still reach them
Page scripts run in the order their place on the page says
CSS imported for one page ships only on that page, and shared CSS ships once
A video ships only the controls you gave it, and preformatted text keeps its first line break
Rich text keeps no-break spaces, and changing an element’s tag drops attributes the new tag can’t carry
The publish checks now flag frames with no title, autoplaying video with sound or without captions, form fields with no name, forms with no send button, broken item links, bindings with nothing to read and scripts that name a missing element, each with the fix
Imported pages land exactly as their source wrote them
Terminal
A page imported from a repository now lands one to one. Every element keeps its true tag, its attributes, its spacing and its inline styles, and the published page is written the way the source wrote it.
Whitespace and preformatted text are kept byte for byte, raw markup stays whole, and inline handlers stay bound to their elements
Popovers, framework directives and the hooks a site’s scripts use to find their elements keep working
The published page no longer adds wrappers around a site’s own sections, and its base styles never outrank the site’s own CSS
Scoped styles, CSS modules and preprocessed stylesheets are worked out as the project builds them, and external, relative and package stylesheets load with their imports and assets
Content collections land as the CMS holds them: drafts, schemas, references, nested entries, body images, filters and sorts included, and importing again updates them in place
An untouched import proposes no changes back to the repository, and every edit is written where the source can hold it or listed where it cannot
The designer checks nesting the way a browser does, so markup it accepts is markup that renders
A repository import now keeps the CSS shared by every page apart from the CSS each page brings. A page publishes and draws with its own styles and no other page’s
The canvas, the inspector and the published site agree that another page’s layout rules do nothing on this one
Renaming a page, making it the home page or moving it to a new path takes its styles with it
A duplicated page keeps its page CSS, and a deleted page takes its CSS with it, with undo bringing it back
A page that no longer brings any CSS of its own drops its block on the next import
Tabs, sliders, accordions and modals work fully from the keyboard
Terminal
Every interactive widget now has one structure and one behaviour. Tabs, sliders, accordions, modals, toggles and disclosures carry full keyboard and screen reader support on the canvas, in Preview and when published.
Tabs take the arrow keys, Home and End
Modals trap focus, lock the page behind them, close on the backdrop and return focus where it was
A slider’s dots scroll its own track, never the page, and autoplay pauses on hover, focus and reduced motion
Enter and Space work on any element that opens or closes something
Scripts can name the elements they act on, and those names follow the elements when they are copied
An imported form that posts to an outside service keeps doing so, and a copy of each entry reaches the forms inbox
An open Dev Program screen now updates itself. Applications, decisions, credit and tier changes show within a minute, or as soon as you return to the tab.
Notices link back to the app the workspace applied from, and a notice about a piece of work opens that piece
A draft application keeps its place when it first saves, so the page no longer jumps
Forms gain spam filtering, recipients, auto-replies, webhooks and file uploads
Terminal
A site’s forms do much more with each entry. Entries are checked against the form you published, spam is sorted out, and each form decides who hears about it.
Required fields, email addresses and lengths are checked, and unknown fields are kept and flagged rather than dropped
Spam is stored apart with its reasons and sends no notices
By default the workspace’s owners and admins are told; a form can notify no one, use the bell only, or add up to five outside addresses, each confirmed first
An auto-reply sends the subject and message you write to the visitor’s email field
Each entry can go out to your webhooks
Forms can take files, up to five of 4MB each, stored privately behind links that expire
Every form’s success message, error message and redirect can be set
An imported form whose own script sent it elsewhere now reaches the inbox, and an imported search form becomes a search of the site itself
The inbox and its export show every field a form has ever sent
Make any page the home page from the Pages list’s right-click menu or the Home control in Page settings. The old home page moves to an address of its own, and links follow it.
Pages built on the CMS now publish exactly what each item holds. An empty field ships blank rather than the design’s placeholder, and a bound image shows the item’s picture at every size.
A list with no matching items shows its empty state
A template page’s pagination no longer links to pages that do not exist
A collection can get a blank template page, ready to design, in one step
Binds made over component cards survive the next edit
Rich text that shows an HTML tag as code stays rich text
An item’s address keeps up to 100 characters, cut at a word, and the designer says when it shortens one
The designer and its design library now live in Baselumen. The suite is two products under one sign-in, Stacklumen and Baselumen, and every menu, page and link says so.
The product switcher, the Hub’s Suite panel, the footer, the products, pricing and about pages and the marketplace filters show the designer as part of Baselumen
A client’s Designs section, its design approvals and Terminal’s Designs panel open Baselumen’s design library and designer
Baselumen’s docs gain ten sections on the designer: starting a design, drawing on the artboard, shortcuts, saving and version history, the library, exporting, pushing to Terminal and designs over MCP
Design events now come from Baselumen’s developer center and reach the webhooks subscribed there
Learning teaches the designer again as Baselumen’s fourth path, with four lessons, and the Baselumen certificate now covers it. Certificates and badges already issued still stand
Agents that connected to the designer before the move are listed under Baselumen in Agents & API
An agent connected over MCP can now rebuild a page’s real structure and behaviour, not only its markup. Tables, media, rich text, semantic tags, dropdowns and the site’s theme are all within reach.
Interactions such as tabs, reveals and slider controls, closed panels, scripts, breakpoint and hover styles, inline SVG and layer settings can all be written
Linked components with their props, related-items lists and full-width bands can be built
An agent can write to a large imported stylesheet, into its layers and without losing any of it, and read it in parts
Agents can upload images and videos
apply_edits refuses a field an operation does not take instead of quietly ignoring it
The server’s notes for agents describe all of this, so an agent knows what it can build
Agents can make every edit you make on the canvas, from a node’s real tag to widgets, forms, states, motion, components and CMS bindings
Agents can change a page’s own code, embed markup, edit a table’s rows and columns and a widget’s items, and style pseudo-elements and states
Agents can edit one interaction at a time, the site’s motion and keyframes, and a component’s props, variants and empty states
get_page_html and preview_page render a page exactly as it publishes, item pages included
update_site_css edits one rule in place
import_html imports a section of HTML onto a page, or a new page, exactly as pasting it into the designer’s Code panel does
create_collection can make the collection’s template page, at /<collection>/[slug] unless you name another address
Agents build forms, bindings and tables the way the designer does
Forms an agent builds get fresh inbox names, and binds are checked against what each element can show
Table edits use the designer’s own table actions, and set_style takes a state at a breakpoint
import_html lands a snippet as the designer would
The publish checks read the site’s collections and every field a bind names
The docs describe the new Insert elements, audio, captions and picture sources in Assets, every CMS binding place and its empty rule, the new MCP tools and how long a form keeps its submissions
Integrations is now Agents & API. Every key the workspace holds, and every agent that has signed in, is on one screen that every key page shares.
Make an agent key from a preset or by choosing each permission, or a content key for published items or drafts too
Keys can reach the whole workspace or one site, and the list filters by kind and reach
A key is shown once with what its client needs, and the screen asks before hiding one that was never copied
The Content API page is rebuilt on the same screen, with each key’s environment, standing and last use, and the collections, quick start and reference beside a connection card
A content key can now read every site in the workspace, naming the site in each request
Old Integrations links redirect, and the Hub and Terminal menus name Agents & API
Primary buttons on settings screens stay blue on hover in every app
A large site now saves and publishes reliably. A publish does its site-wide work once and copies unchanged pages instead of rendering them again, so a sixty-page site publishes in seconds.
A very large stylesheet ships once as its own file instead of inside every page
A publish that fails says where and why, and the panel counts how many pages were unchanged
A publish keeps going when its panel closes; reopening shows where it stands, and the Publish button shows progress while it runs
The staging link shows every time the panel opens
A save too large for one write goes in parts, and the stylesheet is sent only when it changed
An old tab that tries to save a whole large site at once is stopped with one instruction: reload the designer
Agency and personal pages live at stacklumen.com/your-address
Hub Website
Agency and personal pages now live at the root of stacklumen.com. Agencies and people share one set of addresses, so two pages can never collide.
The showcase builder’s Page tab opens on the address, says while you type whether it is free, taken or reserved, and moves a live page at once when saved
A first publish takes the agency’s name when it is free, and asks for another when it is taken
The profile screen shows your address and counts agency addresses when checking a handle
Old page links redirect to the new addresses
An agency has one page, on its home workspace, and it can show the work of every workspace the agency runs
The agency’s other workspaces lead to that page, and their Workspace screen says where it is
Imported sites keep their own light and dark theme, and every rule stays editable
Terminal
A site imported from a repository now brings its light and dark theme with it as the site’s own. Visitors with a dark system setting see the site’s real dark theme, not an inverted copy.
A repository’s root variables become the site’s variables
A dark-first site gets a Start dark scheme and ships dark without a script
Every colour stays as the repository decides, and form controls keep their scheme
Turning a site’s own theme script back on restores the theme whole
A page keeps its own attributes on the html and body elements, and Page settings edits them
Changes you make to imported styles survive the next import, and an unchanged import changes nothing
The Style panel can now edit every rule an imported stylesheet holds. That includes media queries no breakpoint tab names, and rules that reach an element without being one of its classes
A stylesheet built with cascade layers is edited in its own layers, so utility classes still win where they won
The variables rail writes where the Style panel does
A media query previews at its own width
A class with a dot in its name reads, writes and keeps its icon tint when renamed
What an imported page is made of now becomes the designer’s own parts. Its tables, media, forms, shared header and footer, menus and scripted effects all arrive as things you can edit.
A table is a table, a video keeps its sources, a responsive image keeps its sizes, and a form keeps working as it did
The header, banner and footer a site’s pages share land as one component, so one edit changes every page, including a header that marks the current page
Scroll reveals, menu scripts, tab sets and monthly/yearly price switches become native interactions and tabs. The original script is kept, switched off, one click from coming back
Every dropdown and mega menu, imported or built in the designer, is one native dropdown that opens on the canvas, in Preview and when published, keeping the site’s own look
Tables, pictures and players from earlier imports are brought to their proper tags when the site loads, without importing again
A collection list inside a table draws as rows, and a table’s cells and rows paste where they belong
Importing a repository is quicker and handles large sites
Terminal
A large repository now imports in one go. Saves travel compressed, so a site of seventy marketing pages that once took many rounds lands in one.
An import lands only the CSS its pages use, so stylesheets and font files are far smaller with no visible difference
A site of very large pages comes ten pages an import, and the import panel offers the next batch, counted in pages, or a prompt for an agent to build the rest
An import runs to its end whichever panel started it, finds each page by its route and keeps links between pages imported in different rounds
A site built under a base path imports and is classified correctly
A page that cannot be imported stays out on its own while the rest land
Videos play, SVG logos draw in light and dark, hidden icon labels stay hidden, and a site imported a page at a time keeps one copy of its stylesheet
A site’s motion, hero and menu scripts run in Preview and when published, while its sign-in and analytics scripts stay behind
Responsive elements show at their own widths, and importing again can refresh pages that have not changed
The canvas shows content a site’s script would reveal on load, without forcing menus, tabs or dialogs open
An import never takes a workspace past its storage
Edits proposed back to the repository keep the site’s base path, the attributes and text the importer kept, text a shared header takes as a prop, and forms added in the designer
A client you invite now has a portal of their own. It carries your agency’s logo and name, and gives each thing you share with them its own section: Overview, Messages, Website, Designs, Files, Brand and Approvals.
Overview shows what is waiting on the client, their website at a glance, the latest messages, recent files in both directions and their brand
Messages is the real chat, inside the portal, and a client of two agencies switches between them from the side panel
The first time a client opens it, a short animated welcome shows who set the space up and what is already there, then asks for their name and role
A client can send their company logo as a PNG, JPG or WebP
On a phone the side panel becomes a drawer, and older links to an approval, a file or a design open the right section
Someone who accepts a client invitation always lands in the client’s space, never in an agency workspace, even if their address already had an account
New accounts are asked first whether they run an agency, freelance or own a business. A business owner’s Hub and Terminal leave out Clients, the CRM and Reports, and Settings offers the switch to an agency account
Notices reach only the people on the team, or the guests of the client a notice is about, and turning a chat message into an approval request never quotes the message
The docs and the Hub’s learning path describe the client portal
Agency showcases, built and published from the Hub
Hub Website
Every agency can now publish a showcase on Stacklumen. Owners and admins choose which Terminal sites and components to show, write the story behind each piece and publish it from the Hub’s new Showcase builder.
Star up to three pieces to lead with, and give each one a summary, the problem, what was built, what changed, three numbers, a client quote and the people who worked on it
Edits save to a draft as you work. Publish puts the page live and Discard goes back to what is published
The builder’s preview shows the page a visitor sees, at desktop or phone width
The agency page opens on its mark, its name and its work in a live deck of site windows that turns to face the pointer, followed by selected work, services, the team, client words and a contact form
Each piece of work has its own page with the live site at desktop and phone width, or a component at three widths, and person pages list the work someone is credited on
Enquiries from the contact form go to the agency’s address and are listed in the builder to mark read or archive
A shared agency page, piece of work or person page shows its own share card with the agency’s logo or the person’s picture, its name and its line
Live site windows load again in an agency’s showcase, the builder’s preview and the Dev Program’s work cards
Only stacklumen.com can show a site’s Stacklumen address in a frame; other sites still cannot, and custom domains keep their own protection
Learning: lessons, paths and certificates for every product
Suite-wide Terminal Hub Baselumen
Learning is here. 40 lessons in 17 paths cover every product, from a first site to importing a repository and rebuilding its motion natively, with live examples, search and progress that follows you between apps.
Learning opens at /learning and as a Learning screen in Terminal, the Hub and Baselumen, with that product chosen first
Filter paths and lessons by product, level, topic and time, and press / to search
Live examples run in a safe frame, and Open in Terminal creates a practice site to try a lesson on
Learning is for signed-in accounts, so your progress is always kept on your account
Finishing lessons earns badges, and paths, advanced lessons and products earn certificates. Advanced lessons and products have a knowledge check or an exam, with a review of every question once you pass
Certificates download as PDFs on US Letter or A4, and print names correctly in almost every script
Every badge and certificate has a public page that verifies it and an embeddable badge image. You choose which ones to share, and can turn on a learning profile that lists them
A repository import that could not bring a script or an animation across now says so and links to the lesson on rebuilding it natively
Workspace, Profile, Settings and Account screens rebuilt
Suite-wide
The four screens every app shares have been rebuilt on one design. Each has an “On this page” guide that follows the scroll, and one save bar that appears when something has changed, saves on ⌘S or Ctrl+S, and asks before you leave with unsaved changes.
Profile shows a live public card beside the form, a completeness meter that jumps to what is missing, a handle checked as you type and a searchable time zone list
Workspace adds stats, logos that upload as you drop them, colour and type with a live specimen and contrast ratios, services and places you can reorder, and a link to Showcase
Making a workspace an agency is now an action with its own confirmation, never part of a save
Settings offers theme and density as picture cards, and email switches save as they change
Renaming a workspace on the Workspace screen renames it everywhere, the workspace switcher and the rail included
A display name chosen on Profile stays chosen, and a new picture reaches every app as soon as it is changed
The agency’s team size is asked with the same choices everywhere
Interactions, animations and scripts are native to the designer
Terminal
Motion and scripts are now part of a Terminal site itself. A site’s own scripts are kept on the element or page they belong to, keyframe animations are edited stop by stop, and interactions can do far more.
The inspector’s new Scripts view lists and edits a site’s scripts, with when they run and the elements they drive. Scripts never run on the canvas; they run in Preview and on the published site
Interactions can target elements by selector or relation, stagger, play named animations, set attributes and react when an element is scrolled past
Menus and panels can close on Escape, a click outside or a link, take turns in a group, and start closed
The new Animations view edits a site’s keyframe animations stop by stop, beside the site’s motion settings: view transitions, smooth scroll and a reduced-motion guard, on for new sites
The docs describe interactions, animations and scripts, and what runs where
Select a navbar, a dropdown or a mega menu and Settings opens a Menu section listing its items. Rename, link, reorder, nest or delete them in place.
An item links to a page of the site or another address, can open in a new tab, and turns from a link into a dropdown and back
Dropdowns unfold to their links and mega menus to their columns, with Add link, Add column and Remove column. New links and dropdowns look like their neighbours
Open on chooses Click or Hover, and Collapse chooses where the links fold behind the menu button: Tablet and below, Phone only, At every width or Never
A switch previews the open menu on the canvas
On the published site, hover dropdowns open after a short rest and close after a grace period, and arrow keys, Home and End move through their links
The link to the current page is marked and drawn semibold, on the canvas and the published site
A navbar’s links wrap onto a second row instead of running off the bar, and panels never outgrow the window
A dropdown or mega menu dragged onto a navbar joins its links and looks like them
Freely placed elements stay on the page at every width
Terminal
An element you placed freely on one breakpoint now stays inside the page, and shrinks to fit, at widths nobody laid it out at. A deliberate bleed is left as it is.
The inspector marks an element that has been kept inside the canvas, and moving it there saves that breakpoint’s own position
A breakpoint with no layout of its own shows the design your visitors get at that width, and says which one it is showing
The first edit at such a breakpoint starts its own layout without moving anything, in one undo step
Imported pages look and behave as they do on their own site
Terminal
A page imported from a repository now matches its live site on the canvas and when published. Backgrounds, icons, sticky headers, menus and page heights all come across as the site serves them.
Imported sections no longer paint a white background over the site’s own
Icons sized by the site’s own styles draw at their real size instead of disappearing
A sticky header sticks for the whole page
A page’s own menus and phone drawer open on the canvas as they do on the live site, and selecting a link inside a closed panel opens it
Every element keeps its original tag’s styling, so small text, bold text, figures and tables look as the site wrote them
An imported page is as tall on the canvas as on its site, with no empty space under the footer
Sections and scripts are named for what they are, such as Header, Footer, Drawer or Menu script
The repository’s 404 page becomes the site’s not-found page, and its structured data comes across for search engines
“Refresh pages that haven’t changed” brings pages imported by an earlier version of the importer up to date
Escape that closes a menu in Preview no longer closes Preview too
The page picker now sorts a repository’s routes into pages, templates, app screens behind a sign-in, and redirects and files. Pages and templates are ticked; app screens are left out
Groups fold, search covers every group, All and None act per group, and the button says what it brings, such as “Import 70 pages and 8 templates”
A large repository lands in rounds, shown as “Placing pages — round 2 of 3”, with Stop after this round, so you never have to import again to finish
The report counts only what needs a look, and folds everything else under What happened
Connecting an agent takes the same three steps, whichever agent you use
Suite-wide Terminal Website
The Connect panel, the docs and stacklumen.com now give the steps every MCP agent shares: copy the server URL, add it to your agent as a remote MCP server or connector, and sign in with your Stacklumen account.
An agent that cannot sign in uses a token sent as a bearer header
The AI guide on stacklumen.com describes what to look for in each kind of tool, and its fourth chapter is now “Connect your agent”
The Community screen and the outside community links are gone. The docs say where to ask for help instead
If you are signed in, the app’s front doors now take you straight to your dashboard. The sign-in and sign-up pages send you on to where you were going.
A typed or bookmarked /terminal opens Terminal’s dashboard, while the marketing site’s links still show Terminal’s product page
The Hub’s logo goes to the marketing homepage, as Terminal’s already did
Signing out never lands you on your dashboard
When you’re signed in, typing stacklumen.com or arriving from a search result now takes you to your dashboard. The Hub’s logo and links from our own pages still open the homepage
The workspace chip names your workspace the moment a page opens, instead of showing “Workspace” while it loads
Each client now has a space the agency and the client keep together. Files holds anything kept for them, and Brand holds their colours, typefaces, notes, logos and guidelines.
A file stays the team’s until it is shared. A shared file can be sent for approval, taken back or moved to Brand
The client’s guests download what is shared, send files of their own, read the brand and approve files
The agency is told when a guest uploads, and guests are told when the agency shares files
Files can be kept in folders. New folder names one, uploads go into the open folder, and More moves or renames
The Files and Brand tabs show how many files each holds, and the client’s Overview says when the client sent files this week
Uploads are checked before they are kept, and programs and scripts are refused
Clients are managed on one screen, with sharing and approvals
Hub Terminal
Clients now work the same way in the Hub and Terminal. You choose what each client’s guests see, ask them to approve work, and every client screen follows the same rules.
Every site and design in a client’s Sites tab has a Share with client switch, and guests see work in progress only when it is shared
Shared with you shows each client a Waiting for you block to approve work or ask for changes with a note, and the approval email links straight to it
Each client has an Approvals tab with pending and past requests, and Terminal’s Clients screen gains Messages
Archiving a client revokes pending guest invitations and withdraws pending approvals, and restoring brings back the status it had
Deleting a client says what goes and what stays, and offers Archive instead
Members can open a client’s Access tab to see its guests and open invitations; only owners and admins can change them
A client’s health score now counts a message waiting a day for your reply, and approvals left unanswered for over three days
Follow-ups are due at the end of your local day everywhere, and removes, revokes and deletes ask first
Chat only reaches the people who still belong in it
Hub
Someone who leaves the team, or whose guest access ends, now leaves every channel and direct message in that workspace. Every notice is checked against who is in the workspace now.
Archiving a client archives its channels, and restoring brings them back. Renaming a client renames its channels
Notices name the client instead of a channel
A team member limited to some clients sees only those clients, their guests and their channels
Guests see the team as “Team”, and are told when the team writes in their channel, at most once every ten minutes
Anyone in more than one workspace has a workspace switcher in Chat
The client pane opens the client’s company in the CRM and its projects
A new page explains how Terminal’s designer works: the canvas, the code view, repository imports and agents all edit the same site, and everything that ships is built from it.
It walks through how the designer works, where motion runs, what ships, how a repository comes in and how edits go back as pull requests
It lists what is still being built
It now lives at stacklumen.com/design-system, rewritten as a page about the Stacklumen design system, and links to its first address land there
The marketing nav’s Resources panel and the search palette link it as Design system, on desktop and phone
Repository imports bring in every page as its site serves it
Terminal
Importing a repository now reads each page from the repository’s live website, so the page that lands is the one visitors see, with its built styles and images.
Repositories that keep their pages as HTML documents import every page, styled
Importing again brings changed pages up to date where they stand, instead of skipping them
A site larger than one save lands across imports, and pages already placed are left as they are
An imported page’s own fonts and backgrounds point at where the site serves them
Importing, pushing and pulling work from any tab of a site, not only the one that saves for everyone
The empty page’s Import from GitHub and the new-site wizard’s Import open Developers → GitHub
The Developers popup’s GitHub section is redesigned, with your account in a chip, a search and repositories as rows
Chat comes to the Hub, with a channel for every client
Hub
The Hub has chat. It is where your team talks and where you manage each client, with a channel the client can read and a team-only channel beside it.
Every client has a pair of channels: one their guests join with their invitation, and a team-only one guests can never enter
The sidebar lists each client once, with a Client channel and Team only switch, a band that says when the client can see a conversation, and a message box that says who will read what you write
A client pane shows the client’s people, contacts, projects and active sprint, follow-ups, approvals and sites
Turn any message into a task, a follow-up or an approval request; the note saying so stays on the team-only side
Client messages nobody has answered are marked Awaiting reply, with No reply needed to clear them, in the sidebar, on a new Overview panel and on a Messages tab in the client’s profile
Channels, direct and group messages, threads, reactions, formatting, images and files, with search, pins, saved items and notification levels per channel
Presence, statuses and do not disturb, plus Activity, Threads, All unreads and Drafts views
Scheduled messages, reminders, slash commands, @here and @channel, and cards for links to your own records
Mentions reach the bell and, by your settings, email; typing indicators and live updates keep every open tab current
A client’s guest opens chat without the agency’s rail and sees only what they may, including whether the team is around but never anyone’s status text
The Overview no longer goes blank when its Awaiting reply panel loads or is hidden
The CRM becomes a full sales system, and Projects plans in sprints
Hub
The Hub’s CRM now keeps people, companies, activities, email, quotes, reports and automations in one place. Projects gains sprints, a backlog and the charts to run them.
People and companies are records of their own, linked to their leads, each with a table of saved views, filters, a column chooser, inline and bulk editing, CSV import with column mapping and a merge screen for duplicates
Calls, meetings, emails and notes share one timeline on every lead, person and company, and an Activities tab searches them
Send email from the CRM to one person at a time with workspace templates, merge fields and a live preview; replies come back to the sender and every send is logged
Custom fields of eight kinds, and your own names and odds for each stage
Quotes with line items, discount and tax, sent by email
Reports: forecast against monthly quotas, win and loss by reason, source and owner, the sales cycle and stage conversion
Automations book follow-ups, assign owners in turn, send notices and tag leads when a lead arrives, reaches a stage, goes quiet or has a follow-up overdue, with a run log
A CRM palette on Cmd+K and keyboard shortcuts with a help sheet
Projects gains sprints, epics, story points and task types, with every status change kept as history
A backlog to drag work between the active sprint, planned sprints and the backlog against velocity and capacity, with start and complete dialogs that carry unfinished work forward
A sprint board with swimlanes and work-in-progress limits, and burndown, burnup, velocity, cumulative flow and cycle time charts
Quick add reads @person #type 3pt !priority as you type
A project’s views, the sprint playhead and a strip of the sprint’s days sit in a floating dock at the foot of the screen
Selecting work in the List view brings up the same floating bar as the backlog, with Move to, Assign, Priority, Due, Done and Delete
The suite responds to the pointer, and the homepage has a new headline
Suite-wide Website Hub Terminal Baselumen
Brand marks and cards across the apps and the website now respond to the pointer and the keyboard. The homepage headline says what Stacklumen is building.
The homepage reads “Building the agentic future of agency management.”
A brand mark inside anything clickable rises, turns slightly and grows a touch under the pointer or on keyboard focus, in the app bars, product switchers, docs, marketplace tiles and the Made in Terminal badge
On the website, product, pricing, roadmap and showcase cards light up where the pointer is, in the colour of the product they describe
Icon-only controls on the website show their label after a short pause, or at once on keyboard focus
One easing throughout, no overshoot, and nothing moves when reduced motion is on
Terminal tells you when a published site goes down
Terminal
Every published site is checked every five minutes at the address its visitors use. If it stops answering, the workspace’s owners and admins hear about it.
A site is reported down after two failed checks in a row, and back up on the next good one
A certificate within 14 days of expiring is flagged once a day
Alerts arrive in the bell and by email
A new form submission’s notice names the sender, the form and the site, and the owners’ email still carries the whole submission
Several submissions to one site in the same minute arrive as one notice with a count
The CRM, Projects and client records are rebuilt as one system
Hub Terminal Baselumen
The Hub’s CRM, Project Management and client records now work as one system. A lead becomes a client and then work, and every client opens into the same profile in every app.
The CRM is a pipeline board, a leads table, follow-ups and insights: columns show count, value and the weighted forecast, cards drag within and across stages, and Won opens a convert dialog while Lost asks for a reason
The leads table sorts every column, filters by stage, owner, source and tag, edits in bulk and imports and exports CSV
The lead drawer has a stage stepper, every field editable in place, an explained lead score and one timeline of notes, stage history and follow-ups
Follow-ups are grouped overdue, today, this week and later, and completing one can be undone
Insights cover the funnel, win rate, days to close and in each stage, a six-month weighted forecast, sources, owners, activity and lost reasons
Winning a lead suggests matching clients, carries the person across as the client’s contact and can start a project from a template
Projects open on a portfolio with health, progress, budget burn, due date, next milestone and team, and start from six templates
A project has a board, a grouped list, a timeline with dependencies and drag to reschedule, a month calendar and a time tab with budget burn, logging, invoicing and CSV
My work, a weekly timesheet and an eight-week workload view sit beside the portfolio, and a running timer follows you across screens
The Overview gains a Pipeline panel with open value, the forecast, recent wins, follow-ups due and what should close in thirty days
A client opens into one profile in the Hub, Terminal and Baselumen: health score, contacts and guest invitations, sites, projects, tasks, won leads, activity, who can see it and settings
Archiving a client stops new guest invitations and can end guest access
Every link to a client opens it, from the CRM, follow-ups, projects and Terminal site settings, and an archived client keeps its name, marked as archived
Winning a lead offers the client its company is already linked to first, and an archived match offers Restore and file under it
The Portfolio’s client filter lives in the address, so a filtered view can be shared
The Overview’s client register counts every client, leaves archived ones out and offers Add client when there are none
Deleting a client a lead was once won into no longer fails
Agencies and independents who build on Terminal and Baselumen can join the Dev Program. Submit client work for review, get credited for it and move up through the tiers.
Join from Join Dev in the Hub or Terminal; a member is a workspace, so the agency is credited and the people on each piece are named by role
Tiers are Member, Verified (three credited pieces, listed in the public directory) and Partner, with a specialist distinction per product
Work is picked from your workspace, not pasted: Terminal sites and templates, Baselumen components, portals and designs, marketplace listings and apps
Every piece is scored on a published rubric, every decision carries its reason, and work can come back for changes twice
Submit to Dev appears on a published site’s overview in Terminal
The public side is /dev, with a showcase, a member directory with an introduction form, an optional Built by credit for published sites and a Dev badge on agency pages
Every application gets a reference, an automatic first screening and a status page with the review clock, four dated stages and what happens next
An application sent back for more opens with the reviewer’s note and a way to answer and resend it
New members get a Get started checklist on their Overview that ticks itself off
Members can credit another member on a piece of work; once accepted it shows on their directory page
Points age out of the twelve-month window on their own, and a tier only moves down after notice at a twice-yearly review
Receipts, decisions, tier changes and review notices are always emailed, whatever your activity email settings
The program’s terms are published at /legal/dev-program; members can sell their templates in the Baselumen marketplace, and points are recognition only
Agents can read the workspace’s standing, work and review notes with get_dev_program
Terminal has a Marketplace for templates and premium components
Terminal Baselumen Hub Website
The Baselumen marketplace now lives inside Terminal. Browse templates with live previews, buy one for your workspace and create a site from it.
Marketplace sits on Terminal’s dashboard rail beside Templates and in the Hub’s Build group
A template bought for a workspace is unlocked there in Baselumen and in the Terminal designer, and an owned template’s button is Create a site
A creator lists one of the workspace’s Terminal sites, built in the designer or by an agent, and a buyer’s new site is an exact copy; every listing is reviewed before it goes on sale
Creators’ reviewed templates appear in the designer’s template list beside Stacklumen’s, each naming its seller
Premium Baselumen components show in the designer as locked, with Buy, until the workspace owns them
A creator component the workspace bought joins the designer’s component shelf
Terminal’s older template shelf is retired; the Templates screen points to the Marketplace to sell
The public /marketplace shows each template as a live preview, with its own page of page tabs, what it holds and Open in Terminal
stacklumen.com/marketplace now opens on an overview of templates, components, apps, connections and programs, each with a page of its own. Terminal’s Marketplace carries the same sections, with Apps inside it
Each section shows live counts, and templates can be sorted
Inside the products, the Marketplace runs from Overview through Templates, Components, Apps, Connections and Programs to Your library, Sell, Build and Review
Apps left the Workspace rail and moved into the Marketplace. Old app links still land in the right place
An imported template’s sections reach the edges of the window on the published page and in Preview, so its page colour and hero backgrounds no longer stop short of a wide screen
A site with a collection template page, such as /blog/[slug], saves again, and an address that can’t be used says why
The dashboard Overview no longer fails on a site viewed at the start of its 30-day window
Viewers and members limited to certain clients are no longer offered buttons that can only fail
Editing a client’s business details in their portal no longer changes your own
Contact, support and sign-up forms answer bad input clearly and respond faster
The CRM, notes and support screens tell you when something was refused instead of hiding it
Safer accounts, cleaner deletes and access limited to your clients
Suite-wide Hub Terminal
Accounts, workspaces and client access are tightened across the Hub and Terminal. Deleting things now works and cleans up after itself, and members limited to certain clients see only those clients’ work everywhere.
A workspace that has clients can now be deleted, and deleting a workspace also removes its connections, its custom domain and its files
When a member’s account is deleted, the agency keeps their bills, hours, messages and marketplace items
Invitations stop working once the person who sent them is removed or loses their role
A member limited to named clients sees and changes only those clients’ projects, tasks, time, reports, members and folders, in the Hub as in Terminal
Deleting a client is for owners and admins, needs the client’s name typed to confirm, and the guests who lose access are told
A custom domain is connected only after you add the TXT record shown on the Domains screen, proving the domain is yours
Deleting an image or file that a published page still uses names those pages and asks first
An upload into a workspace that has run out of space says so in plain words
When your account’s email address changes, the old address is told
A sign-out link that didn’t come from Stacklumen asks before signing you out
Newsletter sign-ups are confirmed by email, and other forms add you only when you tick the box
Declining analytics cookies stops measurement at once and removes what was stored
The designer, the Hub and published sites load faster
Terminal Hub
Everything opens sooner. The designer’s first download is a fraction of its old size, and published sites are served from the edge until you publish again.
The designer loads its editor in one parallel step, and the code editor and search load only when you first use them
Large sites open noticeably faster, with the page data sent alongside the page rather than inside it
Published pages stay cached at the edge until you publish, unpublish or restore, so visitors to a quiet site no longer wait on a fresh render
Published text no longer jumps when a webfont arrives: each font has a matched fallback in the meantime
The Terminal dashboard prepares the page under a link you hover, and the Hub’s first section arrives with the page
Signed-in pages no longer wait for sign-in to finish loading before they respond to clicks
Agents can now set a site’s custom head and body code through update_site_settings
Terminal’s Apps screen is now a full app marketplace. Discover apps Stacklumen has approved, see exactly what each one may do before you install it, and connect the services you already use.
Discover lists approved apps with their permissions, panels and links
Installed shows what each app may do, asks for your consent when a new version wants more, and Remove cuts off its access at once
Connections link your workspace to the chat, automation, email, CRM, database and file storage services you already use, with each key checked before it is saved
Owners and admins can build their own apps under Build, with a listing, permissions, redirect addresses, a webhook and panels, and submit versions for review
Nothing installs until Stacklumen approves a version, private apps included, and every install runs the approved version
Apps install through a standard OAuth 2.0 consent flow, and an installed app’s panel opens safely inside Terminal
Apps complete sign-in with any standard OAuth 2.0 client, and an installed app acts in Terminal with only the permissions the workspace granted it
Exchanging a code and refreshing or revoking a token no longer fail for apps that follow the OAuth 2.0 standard
An installed app’s access token is accepted by Terminal’s MCP server, limited to the permissions the workspace granted and named for the app in the activity it leaves
A suspended or removed app, or a revoked or expired token, is refused with the reason
The designer’s Apps tab lists the workspace’s installed apps, with Open, Manage and a link to review a newer version’s extra permissions
A site’s Apps tab lists the same installs beside the built-in capabilities
Imported repositories keep their styles, and pull requests propose only your changes
Terminal
Sites imported from a repository now arrive with their stylesheets, layouts and components. A pull request back to the repository contains only what someone actually changed.
Imports follow the folder aliases a project names in its tsconfig or jsconfig, so its styles, layouts and components are found
More of a project’s own code is read during the import, including its functions, dates, addresses and everyday string handling, and a navigation marks the current page
Anything the import couldn’t read is listed once, however many pages use it
Each copy of a repeated element is compared with its own original, so an untouched import proposes nothing
Changing a heading that a component receives as a prop edits the prop where the component is used
Choosing a repository to link scrolls its branch, folder and Link controls into view
Comment on a site and tag the people who need to see it
Terminal Suite-wide
You can now leave comments on a site in the designer. Pin one to an element or leave it on the page, tag people with @, and they’re told.
Open Comments from the bottom rail, or press Shift+C
@ suggests the people who can open the site, and each person tagged gets a notification and, unless they’ve turned activity emails off, an email linking straight to the comment
Threads take replies, can be resolved and reopened, and jump to their element. Open threads show as pins on the canvas
Everyone already in a thread hears about new replies, and nobody is told about their own comment
Anyone who can open the site can comment, viewers and client guests included
The rail shows how many threads are open and a dot when you’ve been mentioned
Agents can read, answer and resolve comments over MCP
Terminal’s designer has a sturdier look. Fields and buttons are filled rather than outlined, rows and controls are taller, and icons are drawn with a softer, rounder stroke.
Menus, popovers and dialogs set their text a step larger, while the docked panels and the bar keep their compact type
The side panels are wider, and an invalid field still turns red
The Publish popover is redrawn in the new style, with switches for its options and a header and footer that stay put as it scrolls
The New site dialog matches the new sizes
Preview’s loading spinner turns again and pages fade in as they load
Publishing shows each step as it happens, and ships lighter pages
Terminal
The Publish panel is rebuilt. As you publish it lists each step live, from reading the site to rendering every page to going live, and five optimisations make the published pages smaller and faster.
The panel shows the site’s status, its addresses with a live indicator for each, the publish checks, History and Unpublish in one place
Optimisations, all on unless you turn them off: minified CSS, scripts and HTML, images below the fold loaded lazily, the first image loaded first, and webfonts shipped inside the page so a hero never paints in a fallback font first
Your pasted custom code and embeds are published exactly as written
Preview shows a spinner while a page renders and fades between pages
The canvas holds animations and transitions still at their resting state. They play in Preview and on the published page
Publish checks offer “Copy a prompt for AI to fix these”, ready to paste into any assistant connected to the site
Agents can list what would ship wrong with the call that fixes each item, read and change a site’s name, share image, favicon, language and optimisations, and set each page’s search and sharing titles and images
Agents can wire a site’s CMS into your own code, and build collection lists on the site
Terminal
An agent connected over MCP can now take a site’s collections into a codebase as a headless CMS, key, types and rebuild hook included, and can place a working Collection List and the pages it links to on the site itself.
get_content_api describes the Content API for a site and returns generated TypeScript: a type for every collection and a small client with no dependencies. The same module is served at /terminal/api/content/v1/types for a build step
create_content_key, list_content_keys and revoke_content_key manage a site’s content keys. A key is shown once, expires after 90 days unless asked otherwise, and the workspace owners are emailed when one is made or revoked
create_webhook, list_webhooks and delete_webhook register signed webhooks, so a site built elsewhere refreshes when items or the site are published
Key and webhook tools need the new Content keys and webhooks permission (integrations:write), ticked on the token. Full access does not include it, and the assistant inside the designer never gets these tools
An agent that signs in over MCP is asked for that permission, so it can manage keys and webhooks without a token from the dashboard. An agent that connected before signs in again to get it
A full-access token’s description now says it holds every permission except content keys and webhooks
The Content API takes ?expand= to return the items a reference points at, one level deep and under the key’s own rules, so a production key never sees an unpublished item through a reference
apply_edits gains add_collection_list, which places the same Collection List the Add panel does, bound to a collection with its card fields, sort, filter, limit or pagination, and add_template_page, which makes a collection’s item page with its fields bound
Item links follow a template page’s address as published: a /blog/[slug] template’s items link to /blog/<slug>, in cards, agent answers and the publish checks
The Add panel’s Collection List no longer titles a card with an image’s alt text field
CMS edits wait for a publish, and fields gain lists, times, settings and languages
Terminal
Edits to CMS items now wait for a publish, so a live item can change without changing what visitors and your own front ends see until you are ready. New field kinds, field settings, fuller rich text and content languages round out the CMS for headless sites.
Every item says where it stands: Draft, New, Published or Changed. Publishing the site publishes every new and changed item, and Publish item, Publish items now and the dashboard’s row Publish put items live on their own
Production Content API keys serve items as last published; development keys show every item as it is being edited, with its status
Discard changes puts a changed item back to its published values, and Unpublish takes a live item off at once. Deleting an item, moving its address and reordering still take effect at once
New field kinds: Date & time, entered and shown in the site’s time zone, Multi-option and Multi-reference
Fields can be Required or Unique, start with a Default, carry a line of Help and be Translated. An item that leaves a required field empty or repeats a unique value is saved, and held back at publish until it is fixed
Rich text takes headings, lists, quotes, rules, images and code as well as bold, italic and links. A value with a line that starts with "- ", "1. ", "## " or "> " now shows as a list, heading or quote; put \ in front to keep the characters
Settings → SEO & sharing adds Content languages and a Time zone. Translated fields hold a value per language, edited in the designer and served by the Content API with locale
Dates on the published site are written in the site language; sites in English keep the form they have always shown
The CSV import reads list and date-and-time cells, imports translations, can publish what it imports, and its preview counts empty required fields and repeated unique values
Agents get publish_items, unpublish_items, discard_item_changes and update_cms_settings, and a publish flag on every write. An agent that relied on its writes going live at once should send publish: true
The designer keeps what you build exactly as you built it
Terminal
Terminal’s designer is faithful from end to end. The canvas lays a page out the way the published site does, imported Baselumen components and templates keep their text and styles, and the inspector shows the values that actually render.
Forms, tables, accordions and video settings such as muted and loop now look and behave on the canvas as they do on the published page
The inspector reads imported styles properly: responsive and nested rules, shorthands, hover states and grids show their real values, and empty fields no longer show sample values
Your style edits to an imported component or template survive when the library ships a new version, and importing a page again no longer replaces a copy you have edited
A whole template imports as one undo step and opens on its home page, with its links between pages pointing at the pages you imported
Forms from the Baselumen library send their entries to your forms inbox
Text you are typing on the canvas is kept if the tab closes or reloads, and a site that fails to load is never saved over
Saving sends only the pages you changed, so a large site saves as quickly as a small one and keeps saving as it grows
Pasting, inverting and styling inside a component keep every copy in step
F6 moves between the canvas, the panels and the inspector
Components and templates imported before this update may carry extra spaces in their text. The designer can’t tell those apart from the original, so import them again to get the library’s exact text
Claude and Codex connect to Terminal and Baselumen over MCP, on your own plan. Nobody adds an AI provider key anywhere: the agent panels became Connect via MCP, and Claude connects by signing in with your Stacklumen account.
In Claude, add a custom connector with the app's server URL and sign in: Terminal at www.stacklumen.com/terminal/api/mcp, Baselumen at www.baselumen.com/app/api/mcp
Only the workspace owner can connect, and a connection acts in the workspace it first connected in
Terminal → Integrations lists every signed-in agent across the apps, with Disconnect and Allow again
Baselumen's server adds the Component Studio, pinning components to a Terminal site and account management, and the designer's tools, which read, draw, edit and push designs
The designer's Chat tab shows when Claude is connected, opens Claude and copies a prompt that names the open page
Claude Code, Codex and the CLI can still use an API token from Integrations
Plans now belong to the agency rather than to each app. One plan, Free, Pro or Agency, covers the Hub, Terminal and Baselumen in every workspace the agency holds, on one subscription and one invoice.
Every site stages free on its Stacklumen address, and a site on its own domain takes a site plan, billed one site at a time
Seats are counted across the agency: each editor counts once however many workspaces they work in, and viewers and client guests are always free
Each agency can take one Agency trial with no card, in place of a trial for every new workspace
Billing is still off during the public alpha, so everything stays free until it is switched on, with notice first
The pricing page, the docs and the terms describe the new plans
The designer gets one bar, inspector groups and variables
Terminal
Terminal’s designer now works from a single top bar. The inspector is organised into groups for layout, spacing, size, position, typography, background, borders and effects, and each group folds away when you are not using it.
Variables: named colours, sizes, fonts, radii and shadows, with light, dark and custom modes and a contrast check
Smart snapping to neighbouring edges and centres, the parent’s padding and an 8px grid as you move or resize
A history panel for restoring an earlier saved version of the page
Menus, class renaming, colour inversion and the right-click menu behave the same everywhere, and new elements land inside the container you chose
Each Terminal site can now serve its published CMS content to your own code. The read-only Content API answers with typed JSON, one page of items at a time, using keys you create for that site in the dashboard.
Fill a collection from a CSV file instead of adding items one at a time
The site dashboard gives each section one clear name and keeps a steady rhythm from screen to screen
Browse complete, multi-page website templates from Stacklumen and independent creators. Each one opens in Terminal, where it becomes the starting point of your own site.
The homepage hero is rebuilt, with a field of traces that routes around the headline and buttons instead of running behind them. Deep purple joins brand blue as a secondary accent at the ends of gradients and edges across the site, the apps and the Stacklumen mark.
The site opens in light mode by default, the apps keep their dark default, and a theme you chose always wins
Buttons are flat everywhere, on the site, in the Hub and in Terminal: one blue, a step darker on hover
Contact, support and enquiry forms line up with the rest of their pages
The product screens on the homepage show on phones again
An agent panel in the Hub and Terminal, on your own AI key
Hub Terminal Suite-wide
A star in the toolbar of the Hub and the Terminal dashboard opens an agent panel beside the screen you are working on. It runs on your workspace’s own key from a supported AI provider, and in Terminal it works with the same tools an external agent uses.
Add a provider key once and every product in your workspace can use it
The panel works on phones, with larger touch targets and a message box that does not zoom the page
Agents reading your CMS see draft items too, the same as you do in the designer
Selected tabs, filters and toggles are now a raised neutral chip in a grey tray instead of a solid blue fill. Blue is kept for primary actions, links and focus, pages run wider, and loading screens show the shape of the page instead of a spinner.
The sidebar marks the section you are on in every frame style, including when you arrive without one named in the address
Focus outlines are visible again on raised buttons
Empty Terminal screens show the icon for what belongs there, so a new list reads as a starting point rather than an error
Every page on stacklumen.com speaks one visual language
Website
Pricing, contact, support, the FAQ, enterprise, security, ethics, the blog, the portfolio, legal and the rest of the site move onto one shared kit built from the homepage. The same hero, type scale, spacing and flat buttons now run through every page, with 2px corners throughout.
Overview now opens on your sites, shown as previews. Below them sit a client roster with status, sites, open work and last contact, then delivery and time, this week, your team, recently copied Baselumen components, site health and your products.
Recently copied components render as the components themselves, not placeholders
The site list reads as a proper list, with previews that load as you scroll to them
A single palette button in the top bar sets the canvas (light or dark) and the frame around it (graphite, light or brand). Terminal adds its green-on-black skin to the same menu, and each choice is remembered.
The canvas keeps its own setting instead of following the frame
Updated components reach sites that already use them
Terminal Baselumen
When a Baselumen component is improved after you imported it, importing it again brings the newer version into your site. Before, a site that already held a copy kept the old one, with nothing on screen to say why.
Baselumen templates and marketplace pieces can be re-imported to a newer copy the same way
A sharper canvas, and inversion that stays on one element
Terminal
Hover and selection outlines are now drawn crisply at every zoom level and no longer cover the edges of text and images. Inverting a component’s colours changes only that instance, and flipping it back restores exactly what was there.
Components stay closed until you open them, on the canvas and in the layer tree alike
A background control, and sections can be dropped above an existing section
Effects fold into six rows, each opening onto its own editor
A site menu beside the page selector reaches site settings, domains, the site list and the dashboard
A component placed from the command palette is the same linked component you get from the panel
Every link into the designer opens a site from the Terminal dashboard rather than a blank setup screen
A Frameworks panel replaces the old project importer. Pick Astro, React, Vite, Vue, Svelte or plain HTML and Terminal writes a brief for the coding agent you already use, with this site’s connection filled in; the agent reads your real project and builds the pages in Terminal, and every change it makes is checked against the same rules as the canvas.
The Apps tab shows whether the agent connection is live and how many agent edits have landed
Every publish keeps a text snapshot of the site, so you can compare two publishes and see exactly what changed
Paste plain HTML and CSS into the Code components panel; framework source is refused with every reason listed, instead of being converted by guesswork
The designer’s sidebar goes from thirteen unlabelled icons to eight named destinations. Blocks, Baselumen components, marketplace libraries and your own designs now sit together as shelves in one Library panel.
Copy a component in the Baselumen library and paste it straight onto the canvas
Designs from your design tool arrive on their own Library shelf, ready to drag onto the page
The Pages panel shows one line per page, groups pages under headings and adds search once a site has a few pages
The preview can switch to any page of the site, and says so plainly when a page cannot be rendered
Navbars and dropdowns can no longer be taken apart into a menu that never opens, and a mega menu joins the Add panel
The ethics page sets out our commitments about the data we hold. It is written to be read straight through, with nothing hidden behind accordions, and it is linked from the site footer.
While Stacklumen is in alpha, the Hub and Terminal are open to every signed-in account without a paid plan. The alpha terms in the legal center explain what alpha means for your work and your data.
The homepage’s product window now draws four real Hub screens: Overview, the project board, the pipeline and the client roster. Drawn screens follow the page’s theme, weigh a fraction of a screenshot, and their text can be read by screen readers.
Page sections arrive in sequence as you scroll, and nothing stays hidden when motion is reduced or a script fails
The site no longer counts retired products in its banner and product strips
The navigation bar’s two icon slots go to Discord and X
The Hub gains Projects, boards of columns and cards you can move by dragging or from the keyboard. Start a timer from the card you are about to work on, and two people reordering at once no longer land a card where neither meant.
Scrolling on the site and in the apps follows the wheel more closely
Below 1024px wide, the Hub and Terminal say they need a larger screen instead of rendering a broken layout; the public site and legal pages stay fully responsive
stacklumen.com/terminal explains what Terminal does and how to use it, for people who have not signed up yet. The homepage’s Terminal button now leads there instead of to a dashboard a visitor cannot open.
Stacklumen is now the Hub and Terminal, with Baselumen beside it for components, client portals and web tools. Older product names are gone from every screen, email, form and document.
The welcome tour is shorter and covers the current line-up
Menus list only products that exist today, and client portals are reached through Baselumen
Plan screens, billing rows, support forms and the roadmap filter all use the current names
Baselumen templates and an apps marketplace in Terminal
Terminal Baselumen
Terminal’s Libraries panel imports Baselumen templates, section by section. The dashboard gains an apps marketplace where built-in and creator apps are installed across your workspace or pinned to one site, each showing the access it asks for.
Components sent from Baselumen appear on their own Imported shelf
Sidebar groups in the Hub and Terminal fold away and can be rearranged
Terminal’s green-on-black skin joins the colour menu
Pasting lands a copy beside the original, and inserting with the page selected starts a new section
Links handed out at publish, and payment links sent to clients, point at their current addresses
The visual site builder moves into Stacklumen as Terminal, on the same account, workspace and client list as the Hub. Design pages on a real canvas across four breakpoints, fill them from CMS collections, collect form submissions, add interactions, publish to a staging link, and let an external agent build through the agent connection (MCP).
Terminal has its own sidebar and carries the Stacklumen mark
Clients and team members are shared with the Hub, so a client added in one appears in both
A first-visit dialog asks which optional cookies you allow, and a Preferences control in the corner of every page reopens it whenever you like. Analytics stay off unless you allow them.
The public site is rebuilt page by page and served alongside the products. A new navigation shows every product and company page in its Products and Company panels, and the site and the apps now share one footer.
Every page the navigation and footer link to is rebuilt, from pricing and enterprise to the FAQ, the portfolio and the legal documents
Pages are much lighter: the menu’s background video no longer downloads until you open the menu
The navigation appears immediately instead of waiting on an intro animation
Signing in no longer loops between the site and the app
The documentation keeps its three columns of contents, article and on-this-page. Callouts now stand out from the text, code blocks carry a language label and a copy button, numbered steps are joined by a rule, tables are bordered, and the on-this-page list marks where you are.
stacklumen.com/legal indexes our policies, each on its own address: terms, privacy, cookies, acceptable use, data processing, subprocessors, billing and refunds, and copyright and takedowns. One set of policies covers the site and every product, and sign-up links to them directly.
Profiles for you and your agency, with public pages
Suite-wide Hub
Your profile grows from a name to a headline, bio, pronouns, location, links and skills, and your agency profile gains a tagline, about text, services, locations and links. Either can be published as a public page that shows only the fields you choose.
One profile is shared by every product, so an edit in one appears everywhere
Account and Profile are reachable from the sidebar
The logo upload shows the logo you already have instead of “No file chosen”
Public profile pages and the Agency tab’s colour swatches display correctly
Invitations that can be accepted, and a front door that is not a login wall
Suite-wide Hub
People you invite can now accept and join your workspace; the invitation link previously led nowhere. Signed-out visitors to the Hub’s address see a public landing page instead of a sign-in form.
Adding a client no longer requires creating a client portal first
Headings render at their intended weight
Links in the menu footer open their pages instead of the sign-in screen
A documentation shortcut sits in the top bar of every product, beside the roadmap. The docs gain proper inline code, labelled code panels, numbered steps, labelled notes and warnings, bordered tables and card grids.
Rewritten against the product itself, with plan limits, tool lists and screen names taken from the current software
A new section explains the two toolbars: the top bar that belongs to your account, and the canvas toolbar that belongs to the screen
Each client in the Hub opens into a card for every product, showing what that product has done for them and a button for the next step there. Empty cards still show, because a product with nothing for a client is often the next thing to do.
Last contact is recorded, so you can see who you have not spoken to in a while
The Hub’s panels are redrawn with clearer trend lines, room to breathe and quieter headers
Leads move across a board by stage, with a weighted forecast and counts of what needs attention above it. Each client also has a merged timeline of everything that has happened with them.
The frame (the top bar and sidebar) and the canvas you work on now take their themes independently, so a dark frame can surround a light working surface. The frame can also take a brand tint.
A theme chosen on stacklumen.com carries into the apps, and back
Dark mode sits on one consistent off-black, with no visible edges between surfaces
The Send button in the help panel is visible again
Shared documentation explains accounts, workspaces, clients, trials, roles and billing once for every product, and each product adds what is its own. Two diagrams show how products, workspaces and client portals fit together.
Roadmap, feature requests and community in every product
Suite-wide
Every product’s sidebar now reaches the roadmap, a feature-request board and the Discord community. The roadmap shows each integration’s own mark, and the top bar has a one-tap Discord shortcut.
New accounts get one short tour that explains the products and asks a few questions about your business. It is answered once for your account, so finishing it in one product means the others will not ask again, and each answer saves as you go.
The support form no longer needs a working session, a workspace or a plan. The email address you type is enough, because it is the one thing someone locked out of their account can still give.
The notched-frame mark replaces the old bar mark across the site, the apps, browser tabs and share cards. Each product in the switcher is redrawn in the same family.
Invite people to your workspace or to a single client’s portal, and remove them when they leave. Everyone holds one of four roles, owner, admin, member or viewer, named the same way in every product.
The canvas toolbar in each product shows recommended actions you can act on, in that product’s colour. When there is nothing to do it says “Nothing recommended at this time”, so a clean result never looks like a broken one.
Agency, Profile and Billing, the same in every product
Suite-wide Hub
Agency, Profile, Billing, settings and the roadmap are now one shared set of screens in every product, backed by the same records. Plans belong to the workspace rather than to whoever subscribed, so a team needs one plan, not one each.
A canvas toolbar with Refresh and a note of how fresh the data is
The product switcher shows each product’s own mark on a darker frame
The Hub gains a CRM on one dense screen, with key figures, filters and search, and leads sorted with the most neglected first. Clients get a section of their own and can be set up in the other products straight from the Hub.
Each product has its own report in the Hub: usage against the previous period and a full activity feed
The Baselumen report shows the components your workspace copied, rendered, and lets you copy them again
A Plan screen lists every product’s plan in one place
Signing in from one product returns you to the product you came from, and your session carries across all of them. Signing out ends the session everywhere.
The account menu opens on the first tap on iPhone and iPad
The Hub now opens on an Overview of your workspace’s activity across the products: what was worked on, the domains you work with, the components you reach for, and what happened recently. Setting up your workspace moves to your first sign-in.
Signed-in screens now live inside one workspace, with a sidebar and top bar that stay put while you move between sections. Links between products open each product’s workspace directly instead of its home page.
The product switcher and command palette are easy to read in both themes
The Hub is rebuilt in the same visual language as stacklumen.com: bold, tightly set display type, a brand-blue accent phrase, atmospheric hero fields and one pair of buttons.
The Hub home gains a search box that finds any screen, product or resource
A new page explains what moving an existing site onto a modern framework involves and when it is worth doing. A capabilities page sets out what clients can expect from us, and the app menu is reorganised around products, services, workspace, resources and company.
Two reference pages join the site: one on copyright and our design framework, and the terms that apply to promotional offers. Both have a contents rail that follows you down the page.
Press ⌘K, or Ctrl-K on Windows, anywhere in the app to search pages, tools and documentation. Recent places, quick actions such as switching theme, and matching blog posts and case studies appear as you type.
A partner program page explains how referral partners work with us, with the terms summarised in plain language, and the contact form gains a referral-partner option.
Referral partners get their own area in the Hub: their referrals and where each stands, a commission summary, a form to refer a client and a code to share
The mobile menu clears the banner and navigation bar when open
The first Baselumen components, and the framework behind them
Baselumen Website
The first Baselumen components ship: a pricing tier, a section intro, a call to action, an FAQ and a contact modal. They are built on the Stacklumen Development Framework, which gets its own reference page and a support route for component questions.
A plain-spoken guide to which AI tools are worth using for everyday business work, from writing to marketing and implementation, and where we choose not to use AI at all.
Web tools, an ecosystem page and a resources library
Website Baselumen
Our first web tools launch: an SEO audit that grades a page for search, accessibility and performance, and a link-preview tool that shows how a URL unfurls across platforms. An ecosystem page lists every product, and a resources library holds downloads. The web tools are part of Baselumen today.
More tools followed within the week: a contrast checker, an embed size checker, and a photo converter that runs entirely in your browser
The public site moves to one visual language: Inter throughout, gradient display headings, soft hero blooms that fade into the navigation, and smooth scrolling. The homepage and about page led, and the podcast, legal, roadmap, how-we-work, mission, navigation and footer followed over the next few days.
Newsletter sign-up in the footer, on the blog and in resources subscribes you for real
Every “Start a project” button leads to the same contact form
Every public page gets a proper title and description, structured data and a sitemap. The navigation is rendered on the server, so it works for screen readers and before scripts load.
A contact form asks the questions that shape a project, its type, budget and timeline, and sends a confirmation as soon as it arrives. Buttons about starting a project lead to it, and support questions keep their own form.
A page for our managed advertising programs covers the platforms we run, how a program goes from audit to reporting, and who it suits. The site footer is redesigned at the same time.
A light and dark switch in the navigation now themes every screen in the app, from the Hub home to onboarding and the merch store, and remembers your choice. The Hub home is rebuilt with a search box and a browsable row of every app.
Entrance animations render reliably on phones and switch off when your device asks for reduced motion
Invited clients get a portal in the Hub with an overview of their engagements and proposals and their business details to keep current. Onboarding now lands clients there.
In June the portal gained a My tasks tab and a card introducing your Stacklumen team
Upgrades and stack pages, and a new navigation bar
Website Hub
Two new pages cover the upgrade paths we offer for existing sites and the tools we build with, with a diagram of how they fit together. The app’s navigation bar is rebuilt to match the public site.
A step-by-step setup creates your company workspace and collects your company basics, contacts and project interests, saving as you go so a refresh loses nothing. A review step shows everything before you finish, with a shortcut to edit each part.
Your name and role appear beside your avatar in the navigation
Sign-in and sign-up are rebuilt on a dedicated identity service, with password resets and account management handled in one place. Signing in returns you to the page you started from.
The first version of the Hub: a home for every Stacklumen app and resource, with navigation and a footer on every page, dark mode, and a layout that works on phones.
Sign-up handles email confirmation cleanly and sets up your profile automatically
A guided, multi-step project brief for prospective clients
That is everything since April 2026. What comes next is on the roadmap.