What’s new | Spacefast

Everything that shipped, newest first.

Product, dashboard, CLI, API and hosting changes, dated as they landed. This page is a record, not a roadmap.

Changelog

August 28, 2026

tags are now revisions everywhere and duplicate routes are gone, old ones with no redirects. Update your clients in one pass.

Publishing a plain ZIP is faster and can no longer be failed by the build sandbox it doesn’t need.

Re-running the install script updates an existing sf. --dry-run previews the steps.

August 27, 2026

The required rationale on mutations is gone from the CLI, MCP, and the API.

Hosting companies can run Spacefast under their own brand, with their own customers, domains, and plans.

Deleting a space detaches its domains so they can be reused.

August 25, 2026

Doc pages moved to paths like /docs/start and /docs/publish, and old addresses redirect.

Agent setup guides moved to /setup/<agent>, replacing /start and /ai.

Reordering a team’s spaces saves as your personal preference, not a team-wide rearrangement.

Going back in the agent setup flow keeps your picks visible.

August 24, 2026

Email codes or a social account, multiple verified emails on one account, and sudo mode on a new Security page.

netlify.toml settings and Netlify build plugins run without a compatibility layer.

Promoted from Settings to space navigation, for every space.

Teams can add their own email domain for automatic enrollment, and a refusal says why.

Spaces with crons in sf.jsonc get a read-only schedule view, and git-push-to-publish gets an onboarding page with live build logs.

OAuth redirects now accept ephemeral loopback ports.

August 19, 2026

Declare cron jobs in sf.jsonc, then read them with sf crons ls or fire one now with sf crons run. The Vercel importer converts them too.

Prerendered pages, RSC payloads, and error pages ship in the publish instead of re-rendering live on every request.

Stranded webhook deliveries are re-driven, and an older build can no longer move production backward.

Every site build publishes llms.txt, setup and skill docs, and an API catalog.

curl -fsSL https://spacefast.com/install.sh | sh installs sf, with install.ps1 for Windows.

August 15, 2026

August 14, 2026

Down from the 15-to-40-second range, on unchanged wire contracts.

A version activation purges every production hostname, so a custom domain stops serving the old page after a publish.

Re-running sf login recovers cleanly from a device login that died mid-handshake.

Big connected builds fit again, failed builds clean up their drafts, and the logs page shows errors instead of spinning forever.

August 10, 2026

Spaces are the only name.

--can view is now --role viewer, with viewer, commenter, editor, and manager.

sf comments settings set controls where comments run and which sites may embed them.

August 7, 2026

Narrow scopes replace API-key setup, and the plugin picks a space only after you choose a team.

sf deployments get|promote|rollback, sf spaces export|import, and sf versions download are removed. sf promote and sf rollback are the one way.

August 6, 2026

The age-based sweep is gone. Free spaces still have a version-count limit: old version bytes that are no longer served can expire, while served versions stay protected.

The closing-tab race no longer loses a claim handoff.

August 5, 2026

Zero, the storage runtime for full-stack apps, is default-on. The only gate left is your plan entitlement.

No static-export compromise. Static, ISR, and SSR routes all execute.

sf publish and connected builds are the way.

Sessions reconstruct with the same transport and capabilities.

August 4, 2026

Percent-encoded and equivalent non-ASCII paths now behave as one.

Downloads respect protected-file rules, including exact-content downloads for agents and CI.

Malformed emails are caught in the form instead of failing after.

August 3, 2026

A complete JSON backup of every declared table, written atomically to the path you name. Also on the API.

sf storage ls and confirmed sf storage rm, with a dashboard tab and API methods to match.

One command installs bundled skills, configures local MCP, and reports auth health. Gemini CLI, Windsurf, Cline, Roo Code, and Continue get setup destinations.

Media files get real audio and video types instead of application/octet-stream.

August 2, 2026

Redirects and custom headers join the project config, and access=public makes the whole live space public.

Visibility, access, and routing changes reach visitors in seconds instead of waiting for the next sweep.

The private-page screen now explains the claim instead of a bare 403.

Hosted connections survive token expiry instead of needing consent re-run.

August 1, 2026

The comment overlay takes your space’s accent and adds notifications, avatar profiles, and bubble threads.

Eleven on-device and fifteen hosted tools replace the 86-operation dump. Code mode still gets everything.

A storage runtime for full-stack apps: server-side code, a queryable database, and object storage.

July 31, 2026

sf publish can compile a Functions worker that runs behind your site. Assets still answer from disk.

Connect WordPress content and rebuilds run when it changes. Private beta for now.

sf publish waits until the new version actually answers at its public URL.

sf auth login joins sf login, and sf deployments ls is now an exact alias of sf versions ls.

An unknown --profile fails with a fix-it error instead of quietly using your default account.

Unknown paths return the standard error envelope, wrong methods get 405.

July 29, 2026

Every new space starts private, including anonymous publishes. Receipts keep bare live and version addresses separate from a repeatable, expiring open link for the author. Docs →

Add grants for the public, your team, specific people, named links, passwords, machines, or external identity, then review access requests in the same place.

The file share dialog switches between people and public audiences, so the link you send matches the access you meant to give.

Publishes that terminally failed show as Failed in Work instead of looking like they are still running.

The team and space switcher keeps the right scope active, request path search works again, /drop recovers from errors, OAuth consent shows a real error state, invitations stop spinning in retry loops, missing version routes no longer blank out, and upgrade buttons only appear on plans you can actually buy.

The same space authority controls page admission, private version previews, and comments. Turning comments on does not open a side door for anonymous access. Docs →

July 28, 2026

Content-addressed files skip the CDN purge, so a publish no longer evicts unchanged assets still serving from the edge.

July 27, 2026

Connect a Jekyll repo or run sf publish --remote with no build settings. Spacefast detects the config, installs gems, builds, and publishes _site. Gem themes and the github-pages gem work.

Change the slug from the dashboard, sf spaces update --slug, or MCP. The managed hostname follows, old addresses redirect, and version URLs are untouched.

Repeat publishes only process changed files, and first publishes go live sooner.

Once the files arrive, Spacefast finishes the publish on its own, so a dropped connection no longer means starting over.

A rejected publish fails immediately with the real error instead of stalling for an hour, and reserved x-spacefast-* headers in _headers are caught at publish time with a message naming the problem.

Publishing to a brand-new space waits while it warms up. The CLI retries for you instead of failing.

A domain that passes its health check completes DNS and SSL setup without another nudge.

Connected builds and API publishes past 2,000 files no longer stall.

Large files and browser assets come straight off the edge, resumable downloads included, and password-protected pages stop re-downloading their assets on every navigation.

Matches the API and the dashboard’s “Apply now”, and exits with the real error when an apply fails.

The docs split into Documentation, Setup, and Recipes, each with one job. Docs →

July 26, 2026

Version URLs stay attached for the life of the space. Free history limits can still expire bytes for older versions that are no longer served.

Publishing without an account had been failing since July 18. sf publish now creates the space, claim link, and version in one call.

CI and agents fetch protected files with Authorization: Bearer and a service token, no callback round trip.

POST /v1/docs/ask streams a documentation-grounded answer, public and rate-limited, while MCP capability discovery comes from Spacefast’s generated OpenAPI catalog.

July 25, 2026

Updating access rules on a public space no longer silently drops its stored password.

July 24, 2026

Not-found, access, directory, and file preview share one responsive light-and-dark design.

Writes are write-only unless you say otherwise, and sf env pull skips values you can’t read back.

July 23, 2026

Pinned and page-level threads, live replies, commenter access, and a triage inbox, in the dashboard, the API, and hosted MCP.

Pages and Appearance merged: theme, visitor pages, SEO and social metadata, and logo in one place.

Grants, named links, passwords, machine tokens, identity connections, requests, and firewall blocks live together across live and immutable versions.

July 22, 2026

Every publish reports whether it activated or was superseded, plus a machine-readable next step, so agents drive the whole lifecycle off one field.

July 20, 2026

Choose which emails you get. One-click unsubscribe actually stops those emails.

Proxy-mode domains can cache upstream responses at the edge.

July 19, 2026

Replace the not-found, password, login, directory, and file-preview pages with spacefast.jsonc or _layout.html, with full _pages takeovers on paid plans. Docs →

Pull a default page into your project, check templates before publishing.

Routes are /<team>/<space>, with Share close at hand.

Lists active grants; sf share check explains exactly which ones open one route.

sf versions ls pages through everything instead of stopping at page one.

July 18, 2026

Publishing and settings progress collects in one surface instead of floating cards.

Start from what you want to add, not a provider catalog.

July 16, 2026

Navigation stays on the team or space you’re in, with canonical Domains, Traffic, and Settings pages.

Versions, builds, and operations in one view, failed and superseded attempts included.

API keys, service tokens, environment variables, webhooks, agents, and approvals in one section.

Start an agent with a one-use link, revoke unused handoffs from the team ledger.

/terminal runs a persistent in-browser shell with the core sf commands.

July 15, 2026

Unclaimed anonymous spaces stay recoverable for seven days after they expire, up from one.

July 10, 2026

Follow a build live, read logs, retry or cancel, and create a space from a connected repository. Docs →

sf env pull, sf redeploy, and sf logs --follow.

sf login uses the device flow from remote shells and agent sessions.

sf setup agent writes a working VS Code MCP configuration.

July 9, 2026

Spaces published without an account get a visitor quota and a content-type policy.

July 7, 2026

Design your space’s theme and social images from settings.

See which agents and apps hold a grant on your account or team, and revoke them.

July 6, 2026

The first request never races domain setup.

A guided install-and-connect flow for GitHub repositories.

July 3, 2026

Validate and diff before applying, undo after, import or export BIND zones, use service presets. Docs →

Claiming is one focused flow, and you can keep the publishing agent connected. Its space key swaps for a scoped credential. Docs →

July 1, 2026

Published files support ETags, so browsers and CDNs revalidate instead of re-downloading.

The API honors Idempotency-Key, so a retried POST doesn’t publish twice.

June 30, 2026

The canonical project config. sf.jsonc and .json variants still resolve at lower precedence.

Extensionless URLs resolve, trailing slashes behave predictably, and a missing SPA asset is a real 404, not the fallback page.

Failures carry a resume envelope, fix hints, and retryable metadata. SF_AGENT turns it on automatically.

Tiered help, offline sf docs search, a JSONL event stream for --json, per-command examples, and aliases.

Create a team and accept an invite from the API, CLI, or MCP.

An MCP registry listing, a Cursor plugin, one-click installs, and an agent brief at spacefast.com/ai.

June 29, 2026

Roll live back to any ready version from the space overview.

A per-space feed of every publish and version event.

Pick events with wildcards, rotate signing secrets with a 24h overlap, and resend past callbacks.

Add analytics and other tags from space settings.

Missing assets return a real 404, and hashed filenames cache forever.

Whether an upload lands as a website or in Files mode is decided from its root HTML. No flag to set.

June 28, 2026

Browse a version by folder, preview images and PDFs inline, and download several at once. Sharing stays route-based at the space level.

Connect GitHub, GitLab, Bitbucket, or a plain repo and build from source with sf git connect, build, and sync.

June 27, 2026

sf mcp runs locally, sf setup agent connects Claude, Codex, Cursor, or ChatGPT in one step, and cloud clients use mcp.spacefast.com. Docs →

Agents write JavaScript in a sandbox, so many tool calls fit in one program.

Injected third-party scripts become versions: diff, approve, and roll back from sf tags or the dashboard.

The site is spacefast.com and the CLI is sf; old domains redirect.

June 24, 2026

A ⌘K command palette, live publish indicator, inline validation, and a mobile sidebar.

One ordered policy with grants, a space-wide ban, and a guided generator, with raw rules behind Advanced.

A committed .spacefast/space.json makes git clone && sf publish find the right space; --config-only pushes config without reuploading files.

Published files serve brotli or gzip automatically.

Threaded comments on version previews, with screenshots and markdown export.

June 18, 2026

POST an HTML body to serve it as index.html, or send any file with ?path. No archive needed.

.wasm, .gz, and .tgz get the right type; gzip and fonts are detected without an extension.

Bind a custom domain in proxy mode to forward traffic to an outside server.

Cache-Control and the matching CDN headers apply exactly as you set them. Docs →

A one-off signed git remote anyone can push a site to. Nothing to install.

June 14, 2026

Connect Cloudflare, Route 53, or Vercel, or use Spacefast DNS, with OAuth, record import, and provider health.

sf publish detects supported project setups, builds locally or with --remote, and publishes the output, or skips straight to --prebuilt. sf deploy is the alias.

sf git origin installs a signed remote so a plain git push deploys your space.

Tags, commits, merges, branch diffs, search, and source archives for connected repos.

Builds cancel mid-run, recover from broken uploads, and log toolchain versions.

June 12, 2026

Write-only secrets: stored, never readable back.

_redirects, _headers, and templates all read {{ vars.NAME }} with a space/team/site cascade and per-channel values.

match: "exact" rules never actually fired in production before. They do now.

Root sf.jsonc and custom _headers work on free publishes; only Basic-Auth stays paid.

sf analytics for views, visitors, and bandwidth; sf logs access to tail recent requests. Both on the API too.

June 11, 2026

Get a live URL right away, plus a one-time link to claim the space before the countdown runs out.

Sign in with a browser-approved device code, then create and scope API keys with policy presets.

Move a space out as an archive, bring one back in, or download a retained version.

Hand a space to another team. It applies once they confirm, and either side can cancel first.

@spacefast/sdk is generated from the OpenAPI spec: types instead of hand-rolled fetches.

June 8, 2026

Domain ideas and availability from the terminal. Also public on the API, no account needed.

200! Agent=true rules beat published files and host redirects, so AI crawlers land where you point them.

May 22, 2026

One PowerShell command.

May 15, 2026

Spaces could run PHP and WordPress next to file-based sites, with sf sftp sync to match. Later removed: Spacefast became file-only.

Copy a space, versions included.

Domains go live only after DNS checks and wait for a live version before SSL.

Single-page apps serve their fallback route before a 404.

@spacefast/vite-plugin validates _redirects and _headers during builds; sf routing inspect prints the compiled rules.

Move a site from Netlify, Cloudflare Pages, GitHub Pages, Vercel, or here.now. Each guide maps that platform’s rules onto Spacefast.

May 13, 2026

DNS, TXT, and SSL state in one command, with the same answers on the API for setup screens and agents.

JSON, XML, text, manifests, images, and fonts ship free; anything still gated warns instead of failing the publish.

The space overview shows what’s live.

Open a retained version, browse its files, diff two retained versions.

Serve public images through a CDN with on-the-fly resize, crop, quality, and WebP. No build step. Docs →

May 12, 2026

Point live at any ready version, no rebuild, no redeploy. Also on the API, immediate or as a pollable job. Docs →

Sync settings, pull variables, and see how routing resolves with today’s values before you publish. The commands live on as sf apply, sf env pull, and sf routing compute.

Team and space variables live in one model, including the values routing files use.

May 11, 2026

Large publishes ride out brief hiccups instead of failing halfway.

The CLI doesn’t say “live” until it means it, especially in CI.

Invite people by email as an owner, admin, or member, from the dashboard or sf teams.