bots-garden/sidekickspublic Fork
⑂ feature/1st-release
Commits
⬇ Clone ▾
git clone https://git.rickub.com/bots-garden/sidekicks.git
git clone ssh://git@rickub.com/bots-garden/sidekicks.git

Host key fingerprint (ed25519): SHA256:iycHnxEyq0Q7uyVpB7JlznP0G7JrTPXLYRcAU5CSLhc — verify it before your first connect.

Download ZIP
🛟 Updated. d580a32 · on feature/1st-release · k33g · 3d ago
reset-sidekicks.md · 38 lines · 1.8 KBmarkdown
Blame HistoryOpen raw

How to reset Sidekicks

This guide shows how to start again from a clean state: the configuration, the conversation history, or both. Quit Sidekicks first (⌘Q): it holds the history open while it runs.

What Sidekicks keeps, and where

Everything is in one folder: ~/Library/Application Support/sidekicks/ on macOS, ~/.config/sidekicks/ on Linux (or $XDG_CONFIG_HOME/sidekicks/).

File or folder Holds
config.yaml the default configuration: agents, channels to create, preferences
preferences.json the last configuration opened from the application, and the recent ones
data/ the history: one database per configuration file (channels, members, messages, agents' commands)

Steps

On macOS (on Linux, replace the folder as above):

cd ~/Library/Application\ Support/sidekicks
rm -rf data                 # every conversation and channel, of every configuration
rm -f preferences.json      # the last opened and recent files: the default configuration opens again
rm -f config.yaml           # the configuration: a commented default one is written at the next launch

Run only the lines you need. Then launch Sidekicks again.

Variants

  • Only one configuration's history: each folder in data/ belongs to one configuration file, but its name is a hash of the file's path; when you cannot tell which one, reset all of data/.
  • Get the test agents back after deleting config.yaml: make install-test-config at the root of the repository.
  • Keep a copy: rename instead of deleting, e.g. mv data data.old.
  • Panel sizes: they are kept by the window itself; Settings and the log start folded at every launch anyway.

See also

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
# How to reset Sidekicks

This guide shows how to start again from a clean state: the configuration, the conversation history, or both. Quit Sidekicks first (⌘Q): it holds the history open while it runs.

## What Sidekicks keeps, and where

Everything is in one folder: `~/Library/Application Support/sidekicks/` on macOS, `~/.config/sidekicks/` on Linux (or `$XDG_CONFIG_HOME/sidekicks/`).

| File or folder | Holds |
| --- | --- |
| `config.yaml` | the default configuration: agents, channels to create, preferences |
| `preferences.json` | the last configuration opened from the application, and the recent ones |
| `data/` | the history: one database per configuration file (channels, members, messages, agents' commands) |

## Steps

On macOS (on Linux, replace the folder as above):

```bash
cd ~/Library/Application\ Support/sidekicks
rm -rf data                 # every conversation and channel, of every configuration
rm -f preferences.json      # the last opened and recent files: the default configuration opens again
rm -f config.yaml           # the configuration: a commented default one is written at the next launch
```

Run only the lines you need. Then launch Sidekicks again.

## Variants

- **Only one configuration's history**: each folder in `data/` belongs to one configuration file, but its name is a hash of the file's path; when you cannot tell which one, reset all of `data/`.
- **Get the test agents back** after deleting `config.yaml`: `make install-test-config` at the root of the repository.
- **Keep a copy**: rename instead of deleting, e.g. `mv data data.old`.
- **Panel sizes**: they are kept by the window itself; Settings and the log start folded at every launch anyway.

## See also

- [How to edit or switch the configuration](edit-or-switch-the-configuration.md)
- [Reference: history](../reference/agents-and-events.md#history)