agentspaces is a Windows app for coordinated work across multiple agents. It helps a system claim work, recover after a crash, and keep tasks moving in a shared queue.
Use it when you want:
- one place to manage work claims
- safe recovery after a stop or crash
- a simple way to run multiple agents on the same task pool
- a Postgres-backed store for shared state
Before you install, make sure your PC has:
- Windows 10 or Windows 11
- Internet access for the first download
- Enough disk space for the app and its data
- A running Postgres database if you plan to use shared storage
- Permission to install or run apps on your PC
If you are only trying the app, start with the default setup and use the local settings first.
Go to the project page here and get the app:
If the page includes a release file, download that file and open it on Windows. If the page gives source files, download the project, unpack it, and run the setup steps listed in the repo.
- Open the download page in your browser.
- Download the Windows version or the full project files.
- If the file is zipped, right-click it and choose Extract All.
- Open the extracted folder.
- Look for a file named
agentspaces.exe,setup.exe, or a similar start file. - Double-click the file to run it.
- If Windows asks for permission, choose Yes.
- If the app asks for a database connection, enter your Postgres details.
When you open agentspaces for the first time, it may ask for:
- a database host
- a database name
- a user name
- a password
- a port number, often
5432
Use the values from your Postgres setup. If you do not have one yet, create a local Postgres instance first, then return to the app.
agentspaces uses a shared workspace model. Each agent can claim a task, work on it, and mark it done. If one agent stops, another can recover the task state and continue.
This helps with:
- task ownership
- work claiming
- crash recovery
- shared state across multiple agents
- queue-based task flow
- multi-agent orchestration
You can use agentspaces for:
- coordinating AI agents on a shared job list
- tracking work items that need retries
- keeping task state in Postgres
- running a simple task queue for agent work
- handling leased work so two agents do not take the same task
If the app needs a database, use a Postgres server with a clean database for agentspaces.
Typical setup details:
- host:
localhost - port:
5432 - database:
agentspaces - user: your Postgres user
- password: your Postgres password
If the app offers a config file, add these values there. If it offers a form, fill them in during launch.
Try these steps:
- Close the app.
- Open it again with the same file you used before.
- Check that Postgres is running.
- Make sure the database name is correct.
- Check your username and password.
- Look for a missing file in the app folder.
- Re-download the project if files look damaged.
A typical project folder may include:
README.mdfor project infosrcorappfor the program filesconfigfor settingsscriptsfor helper toolsdatabasefor schema or setup filesdocsfor more details
If you see a setup script, run it before opening the app.
Use a database account with only the access you need. Keep your Postgres password private. If you use the app on a shared PC, store the config in a folder only you can open.
The project topics point to the main parts of the system:
- agent: one worker that can take on a task
- agent-orchestration: control over many agents
- agents: more than one worker
- coordination: shared control and task flow
- distributed-systems: work across more than one process or machine
- inference: agent output or model use
- llm: large language model use
- multi-agent: many agents working together
- task-queue: ordered work list
- tuplespace: shared data space for task claims
- crash-recovery: restore work after a stop
- Use File Explorer to open folders
- Right-click and choose Run as administrator if the app needs it
- Keep the app folder in a place you can find again
- Do not move files after setup unless the app docs say it is safe
- If you use a zip file, extract it before opening the app
If you need the files again, use this link:
Use agentspaces when you want a shared place for agent work that can survive restarts and keep tasks in order. It fits jobs where several workers need to claim items without overlap and write state back to Postgres