SPS is Redon's local-first Desktop workspace for people and teams who want to use AI on real projects while keeping control of their project folders, tools, and work records. It brings a team's chosen project folders, AI helpers, add-on workflows, and results together in a Workspace—a project-specific work area—on the computers the team chooses.
SPS is not one required task board or one required way to work. Start with a simple Workspace, then add the screens and tools that fit the project—such as game production, web or app development, research, or a team-specific workflow. AI is available when you want it; a Workspace does not have to use AI.
한국어 · SPS product page · Downloads · SPS Source
Create a Workspace for a game, app, website, research effort, or another project. SPS can keep the project's work records, AI activity, and results together. The Host—the main computer that manages the Workspace—chooses which existing project folders are available to it. SPS leaves those folders where they are; it does not make a second copy just to add them to SPS.
Each Workspace can use a different set of add-ons. A game team can use a task and room workflow while a research project uses a different set of screens—or no workflow add-on at all.
An Agent is an AI helper that you set up in SPS. Choose an available command-line helper or local model on a computer, then choose the model and working folder for the Agent. Depending on what is installed and signed in on that computer, SPS can discover tools such as Claude Code, Codex CLI, Agy CLI, Gemini CLI, OpenCode, Pi, Ollama, and LM Studio.
These tools and their accounts are not included with SPS. You provide any required installation, sign-in, plan, or API key. Optional Codex and Claude runtime packs are also published with some Desktop releases; a pack provides the program files, not an account or subscription. AI is optional, and you can keep a Workspace without an Agent.
One computer acts as the Host: it holds the SPS Workspace and chooses the project folders that can be shared. A teammate signs in as a Member (an invited teammate), joins with a Host invitation, and connects their computer as a Node (a computer that offers its approved tools to SPS). The Host approves that computer and chooses which project folders and tools it may use.
Each computer keeps its own AI sign-ins, API keys, and local models. SPS does not copy those credentials to teammates. For the current Windows candidate, computers connect through Tailscale 1.52 or later.
SPS uses Host-managed, internally reviewed add-on packages. The Host can inspect a package, check whether it fits the installed SPS version, and explicitly install or enable it in Settings. SPS does not currently offer an open public marketplace for community uploads or public recommendations. Developers can create packages with the public SPS Plugin SDK; the Host still reviews and manages their use.
The SPS product page describes choosing or building workflows with an Assistant. In the current SPS Source branch, the Plugin Builder code is kept for compatibility but is not started for a new Host, and new Builder work is deferred. The source support matrix lists the Builder package, but that does not mean the Builder is a ready-to-use feature in every current build.
SPS keeps records of supported work runs and their results so a team can see progress and return to the files or artifacts a workflow produced. Add-ons can add their own status pages, task history, reports, and review steps. The details depend on the tools and add-ons the Host has chosen.
The Host can export a server backup for restoring SPS-managed Workspace data on a new, empty Host. A Workspace package can also move supported SPS records into a new Workspace. Neither kind of export is a copy of the actual project folders, AI accounts, API keys, or computer connections. After moving, reconnect the folders and sign in to tools again. See the data and recovery guide before changing computers.
The latest SPS Source branch identifies Desktop 0.4.137 as a development candidate. Its support matrix lists these first-party add-on packages. The source branch starts a new Host without Builder, Workplane, or Memory enabled. A package listed in the support matrix is not a promise that its screens are available in a normal installation. The latest stable installer is an older, separate build and may behave differently.
| Add-on | What it adds | How it is used |
|---|---|---|
Plugin Builder (0.4.0) |
Source package for recording plugin work, collecting build evidence, opening an isolated Preview, and preparing a package. | Not enabled for a new Host in the current source branch; new Builder work is deferred. |
Team Workplane (0.3.92) |
Optional Agent work items, Team Rooms that keep an Agent's project context and decisions across tasks, Task Rooms for one piece of work, helper-Agent assignments, status summaries, and reports waiting for review. | Optional package; it is not started by default. |
SPS Default Memory (0.1.0) |
Optional recall of approved facts and decisions from the current team, project, conversation, or task, plus reviewable suggestions about decisions, lessons, limits, or preferences to remember. | Optional package; it is not started by default. A suggestion does not silently rewrite project files or approved notes. |
Add-ons can bring their own screens, tools, rules, and project data. The Host checks compatibility and chooses where an add-on is used. The Marketplace and its Assistant help people discover and understand add-ons; they do not make that choice for the Host.
A small game team creates a Workspace and the Host selects the existing game folder. The Host invites a teammate, approves that person's computer, and grants it access to the needed folder and tools. The team can connect an approved AI tool and keep execution records with the Workspace. If a compatible Team Workplane package is available and enabled, it can also track Agent work and preserve project decisions across tasks. The project folder stays in its original location, and each person keeps their own AI sign-in.
- Download SPS Desktop from the official release page. Official releases use the stable update channel. Use a Preview only to check installation and first launch.
- Install SPS on a Windows 10 or 11 x64 computer and sign in with a Google account.
- Choose Create Host to start a new Workspace, or join a Host using an invitation.
- Open or create a Workspace. The Host can then select the project folders it should use.
- Add an Agent if you want AI help. The Host can inspect and manage internally approved add-on packages in Settings; Plugin Builder availability depends on the installed build.
- To work with another computer, connect both computers to Tailscale, invite the teammate, and approve their Node and the access it needs.
The getting started guide has more setup detail.
“Local-first” means SPS manages the Workspace and its selected project folders from the Host computer. It does not mean that no information can ever leave your computer. If you send project text or files to a cloud AI or another online service, that service receives what you send. Check that service's terms and privacy settings.
The Host chooses which project folders are shared. A Member cannot pick or replace a Host folder. Choosing an Agent's working folder helps it start in the right place, but that setting by itself is not a separate operating-system lock on every file it can reach. Give each computer and tool only the access your team intends.
SPS is a private feedback build for a small group, not a general public launch. The current supported Desktop target is Windows 10/11 x64. The current source candidate uses Tailscale 1.52 or later for remote Host and Member connections; native LAN and browser-based Workspace access are not supported by this candidate. The current source policy keeps package review and installation Host-managed; public Marketplace search and recommendation features are not part of this candidate.
As of November 12, 2026, 0.4.85 is the latest non-withdrawn official release listed. 0.4.86 was withdrawn after a provenance and signing review. 0.4.90-preview.1 is the latest published installation Preview. The source candidate 0.4.137 is development work, not an installer. Check the official releases and Previews for the current files and notes. A stable installer may not yet include every feature described for the newer source candidate.
| Term | Meaning |
|---|---|
| Workspace | A project's SPS work area, with its chosen add-ons, records, and connections. |
| Host | The main computer that manages the Workspace and chooses which project folders to share. This is a technical role, not a company rank. |
| Member | A teammate invited to join a Host. |
| Node | A computer connected to SPS so it can offer its approved local tools to the Workspace. |
| Source | A project folder the Host has chosen to make available to an SPS Workspace. The folder stays in its original location. |
| Agent | An AI helper set up with a chosen tool or model on a computer. |
| Plugin / add-on | An optional package that adds screens, tools, or a way of working to a Workspace. |
- SPS — this product introduction.
- SPS Source — Desktop app, Host and Node software, and product documentation.
- SPS Core — shared services used by the Desktop app and add-ons.
- SPS Core Compat — a separate compatibility mirror; it is not the SPS Desktop runtime.
- SPS Plugin SDK — toolkit for developers who create add-ons.
- SPS Official Extensions — signed releases of SPS-published add-ons.
- SPS Desktop Releases — official Desktop installers and updates.
- SPS Desktop Preview — separate installation-test builds.
- SPS MY Plugin Builder — design archive for a specialized solution-building add-on; it is not the Plugin Builder implementation.
- Redon Games Website — source for Redon's public website, including the SPS product page.
This repository introduces SPS; it does not contain the Desktop application. Public visibility does not grant permission to reuse SPS software, names, or brand assets. See NOTICE.md.