Notable changes to the Spikefrost platform. Improvements ship continuously; this is the list worth knowing about.
Apps can now declare private, named storage buckets that are provisioned and bound automatically on deploy. Prefix-based lifecycle rules can expire temporary files or move older objects to lower-cost storage, and each bucket appears in Data with its environment and retention policy.
App code can now ask focused choice, score and yes-or-no questions and receive typed answers with probabilities. This gives routing, classification, moderation and verification a faster, lower-cost path than prompting a general chat model.
The desktop App can now install and sign in to Codex in place, checks provider, model and reasoning support before sending, and reads model choices from your own account. A cleaner chat workspace makes settings, activity and operations easier to follow.
A new public pricing catalog shows current rates for AI models, tools, voice, search, browsers and App infrastructure. Metered usage now pairs readable service names with filters that make a specific charge easier to find and understand.
Connector checks now validate provider credentials when the provider supports it and distinguish an unavailable test from a successful connection. Expired GitHub access shows what happened and provides a direct path to replace the token.
Team chats now collapse into one row per teammate and open into a card that brings their current work, recent chats, deployments and source history together. Each shared chat also shows the client and model settings driving it.
A notification bell in the web console and desktop App now collects mentions, channel and Talk messages, and completed runs without making you open every App. Read and mute state stays in sync across devices.
A new Storage section in Settings finds rebuildable App artifacts and old job logs, shows how much space they use and removes them with one confirmed action.
Conversations completed by agents running on your own computers now appear alongside cloud-model conversations in the console, desktop App and CLI after the App is redeployed.
Deleting an App now takes its sites and endpoints offline within seconds while preserving the existing 30-day recovery window. Final cleanup retries safely until all resources due for removal have been handled.
Claude-powered managed-computer chats can now compact their context before it fills, reducing repeated token use during long-running work. A corrected context meter makes the remaining capacity easier to judge.
Free and legacy teams can now move to Pro or Business directly from Usage & plan. Limits are enforced consistently at the point of action, with clear messages when a plan cap is reached.
Connect an Atlassian site from the Connectors page and let agents work with Jira issues using the access level you choose. The integration covers the full issue lifecycle, from discovery and creation through assignment and transitions.
Every agent and computer chat now has a human-only Talk thread, plus an App-wide channel for team coordination. The conversation stays next to the work without becoming part of the agent's context.
Apps can now connect securely to services that require mutual TLS, including Apple Pay merchant validation, banking APIs and payment providers. Spikefrost manages the certificate binding while your App makes a normal request through it.
App decision logs now keep a compact index with each decision in its own file, so builders and agents can load only the rationale they need. Existing single-file logs migrate automatically without losing their history.
Connect your Grok or Kimi subscription and use it for App chats or agents running on a Spikefrost-managed computer. Provider, model and reasoning controls stay with each conversation.
Browse public assets and private environment files from the web console or desktop app, with folders, previews, uploads, downloads, moves and deliberate deletion. New CLI and agent tools bring the same asset library into automated workflows.
Apps now open directly into Chat and remember each provider's last-used model settings. New trace and deployment views make it easier to follow agent work and shipping progress without switching tools.
Run App chats and agents on a Spikefrost-managed computer using your own ChatGPT/Codex or Claude subscription. There is nothing to install, and the computer sleeps when it is idle.
Create, animate, edit, extend and compose Seedance 2.5 videos with synchronized dialogue, sound and music. Seedream 5.0 Pro creates trusted casting images, while the asset library keeps characters, voices and references reusable across productions.
The App view now brings source history, deployments and deployed agents into the web console, alongside schedules, data, logs and security. Environment-aware actions open the right site or mobile preview without leaving the App.
New Apps start with semantic design tokens and guidance matched to the surface being built. Builds now report advisory design warnings without blocking deployment, making common contrast, typography and generated-design problems visible early.
Team App chats can be shared live with teammates and read from a paired phone even when the owner's Mac is offline. Agent traces are grouped by conversation and can render every turn, child agent and tool call as one sequence diagram.
Declare an inbound receiver in app/email.json and every accepted email thread becomes its own agent conversation. Replies retain native threading, and a custom domain can provide one branded address for both sending and receiving.
Agents can opt into web search, page reading, screenshots, PDFs and interactive browser sessions that navigate, click, type and wait. Browser work is budget-gated and metered per action.
Voice agents are now ordinary SpikeAgent classes powered by OpenAI Realtime, with full-duplex speech, barge-in, server-side tools and durable transcripts. This replaces the former ElevenLabs voice-chat stack and retires custom team voices.
Routine scheduling no longer runs on AWS EventBridge. Schedules are now read and armed entirely on Cloudflare, which removes a cross-cloud hop from every scheduled run and means nothing can re-arm a stale AWS schedule behind your back.
A real machine you own can now be an agent. Declare it on an agent class and the machine becomes the thing that does the work, running your own Claude or Codex seat, with the result arriving back in the same conversation.
The largest change in this period. An agent is a TypeScript class in your app under app/agents/**, compiled into your own Worker on deploy. It holds your app's bindings, so it reads your data in-process rather than through a platform API — and deploying it is what registers it.
A Usage tab showing infrastructure usage and cost per app, so spend is attributable to the thing that caused it rather than arriving as one line at the end of the month.
Read the docs →The full store journey is now something an agent can walk you through: enrolling, creating the API keys, and submitting. Testing on a real device stays a single QR scan with no developer account needed.
Signup is now protected against automated abuse, which was arriving through address aliasing. Legitimate signups are unaffected.
Declare a sender in app/email.json and your Worker gets a binding plus an assigned From address. No API keys, no SMTP configuration — the binding is the whole integration.
Declare a queue in app/queues.json and deploy provisions it along with a dead-letter twin. Produce from app code, consume with a handler or an agent, with retries and backoff you configure.
A desktop app for building by conversation. Your teams and apps in a rail, a chat per app, and the project on disk — with no terminal required, though everything it does is still available from the CLI.
Ask for a mobile app and a real native companion is built alongside your web app. Scan the QR code once with Expo Go and reopen it after every deploy — no cables, no store account.
Read the docs →Opt a route in with one line and it is served from the edge without running your Worker at all. Every deploy invalidates the app's cache automatically, so a release can never leave stale HTML behind.
Reads can be served by regional replicas, multiplying read throughput. The scaffold wires a per-request session so every visitor still reads their own writes.
Design a voice, audition three takes, and keep the one you want as a team voice for voice-enabled chat. This ElevenLabs-based capability was retired on 4 August when voice agents moved to OpenAI Realtime.
Sonnet 5 becomes the default for new work, with Sonnet 4.6 and Opus 4.7 retired. GLM 5.2 and Kimi 2.7 Code join the registry, including a high-speed Kimi variant.
A Workers KV namespace is now bound to every app as env.KV, with no setup. Use it for caching, sessions, feature flags and counters — and as the fastest mitigation you have during an incident, since a flag flips in seconds without a deploy.
Read the docs →Author a write as an operation route and every caller — an agent, an HTTP route, a scheduled job — goes through the same invariant. The build fails if an operation route skips caller verification, because an unauthenticated write path is one anyone can invoke.
IP, country and ASN rules, a bot threshold, blocked paths and maintenance mode — enforced at the edge before your code runs, so filtered traffic costs you nothing.
Read the docs →A filter language for request logs with click-to-filter, so finding the failing request stops being a scroll. Available in the console and from sf logs.
Secrets can be updated without a redeploy dance. Values remain write-only — listing returns names, never values.
Read the docs →A scheduled agent can deliver its result straight to Slack, email or chat with no orchestration to write.
Read the docs →A thread rooted on the bot's own message continues naturally — no need to mention it again on every reply. In channels with several bots, messages are attributed so each one knows what is meant for it.
Read the docs →Grant specific people read access to an app's conversations, so the person answering for an agent's behaviour can actually see what it did.
The website chat widget gained a full-screen mode with new-chat and history, plus container and inline mounting and a documented theming contract.
Read the docs →Deep-copy an existing app, optionally into another team — useful for spinning a variant off something that already works. A clone is a separate app from then on; for a staging copy of the same app, use an environment instead.
Read the docs →Connect remote MCP servers that authenticate with a custom header, and edit those header values from the connector modal.
The console leads with a launcher across all your teams and apps rather than a left rail, with a click-to-copy app-id chip in the workspace header.
One app can start work in another, governed by an explicit invocation policy that says who may call in. Templates became team-wide and apps can be grouped.
A calendar-month cap alongside the existing daily one, so a slow leak is bounded and not just a single bad day.
See your database contents and the tasks currently running against an app, without leaving the console or reaching for the CLI.
Read the docs →Building on Spikefrost? The documentation covers everything here in depth.
Answers come from the documentation. Frost can be wrong — check the linked page.