01 / ARRANGE
Give every agent its space.
Open your project. Split the terminal grid. Put each agent where you need it, with its own live shell and working folder.
SpaleSpace · Terminal workspaces
THE SPALE ECOSYSTEMMeet your working environment
Your agents.Your workspace.
Run your coding agents side by side. Keep terminals, tasks,
memory, and changes in one desktop environment.
Installed with SpaleHub · Windows 10+ · 64-bit
SpaleStudio / The working environment
Interactive product tourClaude Codefrontend · powershell
✳ Claude Code
C:\projects\orbital
› Build the workspace navigation.
✓ Read src/components/Sidebar.tsx
✓ Updated navigation and active states
›Checking keyboard navigation
Codexbackend · powershell
>_ Codex
C:\projects\orbital
› Add project persistence.
✓ Read src/lib/projects.ts
✓ Added save and restore handlers
✓6 tests passed
Gemini CLIreview · powershell
◇ Gemini CLI
C:\projects\orbital
› Review the workspace changes.
✓ Checked 3 modified files
Navigation and persistence look good.
›Reviewing error states
Browser previewlocalhost:3000
◒orbitalWorkspace / Overview
A little more
space to think.
Your projects, in a calmer orbit.
Open workspace ↗SHARED GOAL / ORBITAL
Ship the new workspace.
Claude · InterfaceCodex · BackendGemini · Review
Queued 01
Check empty and error states
Gemini · ReviewIn progress 02
Build workspace navigation
Claude · InterfaceVerify saved project state
Codex · BackendComplete 01
Define project data model
✓ Codex · Backend↳ Codex → Claude Project handlers are ready.
↳ Claude → Gemini Navigation is ready for review.
↳ Claude → Gemini Navigation is ready for review.
PROJECT MEMORY
▤ Architecture
▤ Design decisions
▤ Project conventions
▤ Release checklist
SPALEMEMORY / ARCHITECTURE.MD
A decision worth keeping.
Workspace layouts belong to the project. Restore the terminal arrangement when the project opens.
## Project conventions
→ Keep project paths explicit.
→ Save layout with project state.
→ Review changes before merging.
→ Keep project paths explicit.
→ Save layout with project state.
→ Review changes before merging.
[[design decisions]][[project conventions]]
Workspace connectedUTF-8Illustrative product tour
01 / Arrange your working space.Real terminals. Your folders. A browser right beside the code.
The agents you already use. The accounts you already have.
Bring your own CLI.
Claude CodeCodexGemini CLICursorCopilotKimi Code
Plus OpenCode, Grok, and other agents on your PATH.
01 / The workflow
From the first prompt.
To the final diff.
The work already has enough moving parts. Your environment should help you keep them together.
02 / COORDINATE
Keep the whole build in view.
Set a shared goal, assign the roles, and follow the handoffs. Agents can work in parallel with a board and messages between them.
SpaleSwarm · Agent coordination03 / CONTINUE
Pick up with context.
Keep the decisions that matter in linked Markdown notes. Your next session can start with the thinking you already did.
SpaleMemory · Persistent contextSpaleSwarm
One goal.
A few good agents.
Let one agent build the interface, another handle the backend, and another review the work. Give each a clear role in the same project.
Shared tasks, agent messages, and visible activity keep the handoffs close to the work.
Explore agent coordinationWORKSPACE / ORBITAL
SHARED GOAL
Ship the new workspace.
Interface
Claude Code
Building
Backend
Codex
Testing
Review
Gemini CLI
Reviewing
02 / The context
Good work builds
on what came before.
The architecture decision. The project convention. The approach that worked. Give your agents somewhere to keep it.
SpaleMemoryarchitecture.md
PROJECT / ORBITAL
Decisions, with a paper trail.
## Workspace architecture
Keep layout state with the project.
Restore the working environment on open.
## Why this matters
Returning to a project should feel like
returning to where you left off.
[[project conventions]][[layout decisions]][[release checklist]]
Linked Markdown · Shared across sessions
Memory that carries forward.
Agents can read and write linked notes, keeping decisions available beyond a single conversation.
A method you can reuse.
Drag a SpaleSkills card onto a terminal to give the agent a working methodology. Use built-in cards or your own.
Context you can read.
Plain Markdown keeps project knowledge understandable. Open a note, follow a link, see the reasoning.
A new session should never mean a blank slate.
Look inside SpaleMemory03 / The details
Stay close
to the actual work.
Check the diff. Open the preview. Track the next task. Keep the tools you need beside the agents doing the work.
src/lib/workspace.ts+ 4− 1
12
export async function openProject(id) {13
const project = await loadProject(id);14
− return createWorkspace(project);14
+ const layout = await loadLayout(id);15
+ return createWorkspace({16
+ ...project, layout17
+ });18
}◒ orbitalWorkspace / Overview
A little more
space to think.
Your projects, in a calmer orbit.
Pick up where you left off.
To do 1
Write the release notes
DocumentationIn progress 1
Review the saved layout
ReviewDone 1
Build the project sidebar
InterfaceProject tasks, updated by you or an agent.
Keep the handoff visible.
Example project · A docked Git panel, beside your terminals.
04 / The Spale ecosystem
A considered set of tools.
One place to start.
Studio is your working environment. Hub brings the Spale applications, licenses, and updates together.
SpaleStudio
THE WORKSPACETerminals, agents, shared tasks, and project memory. The desktop environment for the whole build.
Explore StudioSpaleHub
THE STARTING POINTInstall Studio and Voice. Manage your account, licenses, updates, add-ons, and release notes.
Get the HubSpaleVoice
PART OF THE ECOSYSTEMAvailable alongside Studio through SpaleHub, with installation and updates in the same place.
View in HubBefore you begin
A few useful
things to know.
The practical details about the workspace, your agents, and getting set up.
What exactly is SpaleStudio?
SpaleStudio is a Windows desktop development workspace. It brings real shell terminals, coding agents, a browser, an editor, Git tools, shared tasks, and project memory into one environment.
Can I use my existing coding agents?
Yes. Studio launches the command-line agents installed on your computer. Claude Code, Codex, Gemini, Cursor, Copilot, OpenCode, Kimi, and Grok are among the supported options. Your existing agent accounts handle model access and usage charges.
How are Space and Swarm different?
SpaleSpace arranges independent terminal sessions in a grid. SpaleSwarm gives multiple agents a shared goal, individual roles, a task board, and messages for coordination. Memory and other project panels can sit alongside your work.
How do I install it?
Download SpaleHub for Windows 10 or later, 64-bit. Hub installs SpaleStudio and manages your account, license, and updates. Keep Hub running while you use Studio; Studio pauses if Hub closes and reconnects when it returns.
What does a Spale license include?
Spale is organized around one plan for its applications. Pricing is still being finalized and licenses are currently issued manually. Check the current plan details before getting started. Coding-agent usage is billed separately by the providers you already use.
Make yourself at home.
Open your project.
Get to work.
Bring your agents, your tools, and your next idea.
Give the whole build a place to happen.