# Spade: 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.

- Spade is in beta: it ships in every copy of ace and is off until switched on in ace's Settings › Beta.
- Spade runs as its own service on your computer, beside ace, and is never hosted.
- Spade uses your own models: any endpoint with your key, kept in your operating system's keychain, or a coding CLI you are signed in to.
- Spade is part of ace, which is free and open source (Apache-2.0).

## Spade's features

Spade has 12 features, shown one at a time on the page:

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.
7. 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.
8. 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.
9. Digests: What moved, what each bot decided and why, and what waits on you, built from its own record.
10. 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.
11. 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.
12. 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.

## How to turn Spade on

1. Switch it on: In ace, open Settings › Beta and turn on Spade.
2. Give it a model: Add an endpoint with your key, or pick a coding CLI you are signed in to.
3. Say hello: Talk to Spade, or press + for a new bot with a task of its own.

## Questions

### 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.

Web page: https://acehq.dev/spade/
