In beta
Bots that work for you, on your computer.
Spade is ace's own assistant: a messenger where you talk to Spade and to bots you make, each with a face, a task, a model and a machine.
Bots you make
Each bot has a face, a task, a model and a computer it lives on. Spade is the main one, and always there.
Clubs
Put 2 to 8 bots in a group chat with a lead. The lead hands the parts out; @Name goes straight to one bot.
It works on its own
A bot writes down what done means, works through a plan, and calls it done only once a separate check agrees. No step count or clock cuts it off.
Its own computer
A browser, the screen, a terminal and files of its own, live beside the chat. Work alongside it, or take over and hand back.
Memory
Short notes you can read and change, with About you shared by every bot, and a record of what it learned on past jobs.
Routines and waking
Work on a schedule, on an ace event, from a webhook or on a heartbeat. In between, a bot sleeps until a time or until something happens.
Skills, plugins and apps
A bot proposes skills you can keep, uses the plugins you turn on for it, and reaches only the apps you hand it.
Files, voice and research
PDF, Word, Excel and CSV in, images out, dictation and read-aloud. Research runs in the background with helpers and comes back cited; bigger jobs can start other bots and ace agents.
Digests
What moved, what each bot decided and why, and what waits on you, built from its own record.
Your models, your machine
Any endpoint with your key in the OS keychain, or a coding CLI you're signed in to, and a model per job. Spade runs on your computer, never hosted.
Sandbox and review
Commands run in a sandbox: the bot's folder, none of your passwords, the network through Spade's proxy. What reaches outside is checked first.
Always yours
Paying, sending as you and changing access always come to you as a request. Questions come as a card you can answer later.
Make one.
Pick a face. In the app it works the same, then you give it a job.
Bolt
A toy: nothing is saved. New bot in Spade starts the same way.
Switch me on.
I'm in every copy of ace, off until you say so.
v0.0.24 for macOS on Apple silicon, 281 MB. v0.0.24 for Windows on x64, 242 MB. v0.0.24 for Linux on x64 (AppImage), 278 MB. Release notes
- 01Switch it onIn ace, open Settings › Beta and turn on Spade.
- 02Give it a modelAdd an endpoint with your key, or pick a coding CLI you are signed in to.
- 03Say helloTalk to Spade, or press + for a new bot with a task of its own.
Questions about Spade.
Does Spade cost anything?
Spade is part of ace, which is free and open source. The models are yours: you pay your own endpoint, or use a coding CLI subscription you already have. Spade shows what each bot spent, and has no limits of its own.
Does Spade run in the cloud?
No. Spade runs as its own service on your computer, beside ace, and listens only on that machine. Each bot lives on the computer you choose for it.
Where are my API keys kept?
In your operating system's keychain: Keychain on macOS, Credential Manager on Windows, the Secret Service on Linux. A key is never written to a file, a log or ace's relay, and no app can read it back.
What can a bot do without asking me?
Work in its own folder: run commands in its sandbox, read the web, keep notes. Publishing and commands outside the sandbox are reviewed first. Paying, sending anything as you and changing access always ask you.
What is a club?
A group chat of 2 to 8 of your own bots with a lead. The lead hands parts of the job to the others, and @Name sends a message straight to one of them.
How do I turn Spade on?
Spade is in beta. In ace, open Settings › Beta and turn on Spade, then give it a model in Settings › Spade.
Free, open source, and yours to run.
Install ace on your computer, point it at a project, and start a thread with any agent you have logged in.
v0.0.24 for macOS on Apple silicon, 281 MB. v0.0.24 for Windows on x64, 242 MB. v0.0.24 for Linux on x64 (AppImage), 278 MB. Release notes
Star on GitHub