@rizom/ops 0.2.0-alpha.27 → 0.2.0-alpha.29
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -21,6 +21,11 @@
|
|
|
21
21
|
- `https://<handle>.rizom.ai/health` returns `200`
|
|
22
22
|
- unauthenticated `POST https://<handle>.rizom.ai/mcp` returns `401`
|
|
23
23
|
14. For fleet upgrades, edit `pilot.yaml.brainVersion` and push once; CI rebuilds the shared image tag, refreshes generated user env files, and redeploys affected users.
|
|
24
|
-
15. Hand the Discord setup details to the user.
|
|
25
|
-
16.
|
|
26
|
-
|
|
24
|
+
15. Hand the Discord setup details to the user.
|
|
25
|
+
16. Hand over the browser defaults:
|
|
26
|
+
- Dashboard: `https://<handle>.rizom.ai/`
|
|
27
|
+
- CMS: `https://<handle>.rizom.ai/cms`
|
|
28
|
+
- GitHub token guidance for CMS access to the user's private content repo
|
|
29
|
+
17. If they need direct client access, also hand over the MCP connection details.
|
|
30
|
+
18. If you are also giving them a content repo workflow, describe it as optional and frame git/Obsidian as an advanced file-based path, not the default.
|
|
31
|
+
19. Send `docs/user-onboarding.md` to the user as the pilot handoff guide.
|
|
@@ -2,18 +2,23 @@
|
|
|
2
2
|
|
|
3
3
|
Welcome to the Rover pilot.
|
|
4
4
|
|
|
5
|
-
This
|
|
5
|
+
This guide is written for **first-time users**. You do **not** need prior experience with Rover, MCP, git, GitHub, or Obsidian to get started.
|
|
6
6
|
|
|
7
7
|
## What Rover is
|
|
8
8
|
|
|
9
9
|
Rover is your private AI assistant for working with your own notes, links, and ideas.
|
|
10
10
|
|
|
11
|
-
In this pilot,
|
|
11
|
+
In this pilot, the normal experience is:
|
|
12
12
|
|
|
13
|
-
-
|
|
14
|
-
- **
|
|
15
|
-
-
|
|
16
|
-
|
|
13
|
+
- **Discord** for chatting with Rover
|
|
14
|
+
- the **Dashboard** in your browser at `https://<handle>.rizom.ai/`
|
|
15
|
+
- the **CMS** in your browser at `https://<handle>.rizom.ai/cms`
|
|
16
|
+
|
|
17
|
+
Optional workflows exist too:
|
|
18
|
+
|
|
19
|
+
- **MCP** for direct client access from supported AI tools
|
|
20
|
+
- **git** if you want to work with the underlying files directly
|
|
21
|
+
- **Obsidian** if you want a nicer note-focused editor for those same files
|
|
17
22
|
|
|
18
23
|
You can think of Rover as a private knowledge companion that helps you:
|
|
19
24
|
|
|
@@ -23,6 +28,18 @@ You can think of Rover as a private knowledge companion that helps you:
|
|
|
23
28
|
- find patterns in what you have collected
|
|
24
29
|
- think through questions with AI
|
|
25
30
|
|
|
31
|
+
## The default mental model
|
|
32
|
+
|
|
33
|
+
If you remember only one thing, remember this:
|
|
34
|
+
|
|
35
|
+
- **Discord** = talk to Rover
|
|
36
|
+
- **Dashboard** = browser overview
|
|
37
|
+
- **CMS** = browser editing interface
|
|
38
|
+
- **MCP** = optional direct client integration
|
|
39
|
+
- **git / Obsidian** = optional file-based workflow
|
|
40
|
+
|
|
41
|
+
Most pilot users should start with the first three.
|
|
42
|
+
|
|
26
43
|
## What you will receive from us
|
|
27
44
|
|
|
28
45
|
We will send you the details you need to get started.
|
|
@@ -30,209 +47,222 @@ We will send you the details you need to get started.
|
|
|
30
47
|
That usually includes:
|
|
31
48
|
|
|
32
49
|
- confirmation that Discord is enabled for you, plus the invite/setup steps
|
|
50
|
+
- your **Dashboard URL**: `https://<handle>.rizom.ai/`
|
|
51
|
+
- your **CMS URL**: `https://<handle>.rizom.ai/cms`
|
|
52
|
+
- if you will use the CMS, an invite to your **private** Rover content repo plus instructions for creating a GitHub token
|
|
33
53
|
- if needed, your Rover MCP URL: `https://<handle>.rizom.ai/mcp`
|
|
34
54
|
- if needed, your **Bearer token**
|
|
35
|
-
- if needed, an invite to your **private** Rover content repo
|
|
36
55
|
- any extra instructions if we are testing a specific workflow with your cohort
|
|
37
56
|
|
|
38
57
|
If we give you a **Bearer token**, treat it like a password. Do not share it.
|
|
39
58
|
|
|
40
|
-
##
|
|
59
|
+
## Start here: your first 5 minutes
|
|
41
60
|
|
|
42
|
-
|
|
61
|
+
For most users, the best first setup is:
|
|
43
62
|
|
|
44
|
-
|
|
45
|
-
|
|
46
|
-
|
|
63
|
+
1. join the Discord server we send you
|
|
64
|
+
2. open your Dashboard at `https://<handle>.rizom.ai/`
|
|
65
|
+
3. open the CMS at `https://<handle>.rizom.ai/cms`
|
|
66
|
+
4. when the CMS asks for GitHub access, use a fine-grained GitHub token with access to your private Rover content repo
|
|
67
|
+
5. send a first message in Discord and make one small edit in the CMS
|
|
47
68
|
|
|
48
|
-
|
|
69
|
+
A simple first chat message is:
|
|
49
70
|
|
|
50
|
-
|
|
51
|
-
|
|
52
|
-
- join Discord
|
|
53
|
-
- message Rover there
|
|
54
|
-
- start using it
|
|
55
|
-
|
|
56
|
-
If your cohort is also testing MCP, we will send the URL, Bearer token, and setup help separately.
|
|
71
|
+
> What can you help me do, and what should I use you for?
|
|
57
72
|
|
|
58
|
-
|
|
73
|
+
Or:
|
|
59
74
|
|
|
60
|
-
|
|
75
|
+
> Help me save my first note.
|
|
61
76
|
|
|
62
|
-
|
|
63
|
-
- a normal **git repo of markdown/text files** only if you also want to work directly with your content later
|
|
64
|
-
- **Obsidian** only if you want a friendlier interface for those same files
|
|
65
|
-
- **Claude Desktop** or another MCP client only if we explicitly ask you to test a direct MCP workflow
|
|
77
|
+
A simple first CMS action is:
|
|
66
78
|
|
|
67
|
-
|
|
79
|
+
- open the **Notes** collection
|
|
80
|
+
- create a short note about why you want to use Rover
|
|
81
|
+
- save it
|
|
68
82
|
|
|
69
|
-
|
|
83
|
+
If Discord is not enabled for you yet, tell us and we will share the right next step.
|
|
70
84
|
|
|
71
|
-
|
|
72
|
-
- open the Rover channel or DM
|
|
73
|
-
- send a first message
|
|
85
|
+
## One important idea: Discord + Dashboard + CMS are the default, MCP is optional
|
|
74
86
|
|
|
75
|
-
|
|
87
|
+
If you are new to Rover, the shortest explanation is:
|
|
76
88
|
|
|
77
|
-
|
|
89
|
+
- **Rover** is the assistant
|
|
90
|
+
- **Discord** is the default chat interface
|
|
91
|
+
- the **Dashboard** is the default browser view
|
|
92
|
+
- the **CMS** is the default browser editing interface
|
|
93
|
+
- **MCP** is an optional direct connection method for supported AI clients
|
|
78
94
|
|
|
79
|
-
|
|
95
|
+
You do not need to understand the protocol details unless we specifically ask you to use MCP.
|
|
80
96
|
|
|
81
|
-
|
|
97
|
+
For most users, the practical meaning is simple:
|
|
82
98
|
|
|
83
|
-
|
|
99
|
+
- join Discord
|
|
100
|
+
- open your dashboard in the browser
|
|
101
|
+
- use the CMS when you want to edit structured content directly
|
|
102
|
+
- start using it
|
|
84
103
|
|
|
85
|
-
|
|
104
|
+
If your cohort is also testing MCP, we will send the URL, Bearer token, and setup help separately.
|
|
86
105
|
|
|
87
|
-
|
|
106
|
+
## Working in the CMS
|
|
88
107
|
|
|
89
|
-
|
|
90
|
-
- **Bearer token authentication**
|
|
108
|
+
The CMS is the easiest way to edit Rover content in the browser.
|
|
91
109
|
|
|
92
|
-
|
|
110
|
+
Use it when you want to:
|
|
93
111
|
|
|
94
|
-
-
|
|
95
|
-
-
|
|
96
|
-
-
|
|
112
|
+
- create notes without touching git directly
|
|
113
|
+
- edit existing content in a structured form
|
|
114
|
+
- browse your collections in one place
|
|
115
|
+
- make quick updates from the browser
|
|
97
116
|
|
|
98
|
-
|
|
117
|
+
### Why the CMS asks for GitHub access
|
|
99
118
|
|
|
100
|
-
|
|
119
|
+
Your Rover content lives in a **private GitHub repo**.
|
|
101
120
|
|
|
102
|
-
|
|
121
|
+
The CMS edits that repo for you.
|
|
103
122
|
|
|
104
|
-
|
|
123
|
+
That is why it asks for a **GitHub token**.
|
|
105
124
|
|
|
106
|
-
|
|
107
|
-
- **Authentication:** Bearer token
|
|
108
|
-
- **Token:** the token we sent you
|
|
125
|
+
In practice, that means:
|
|
109
126
|
|
|
110
|
-
|
|
127
|
+
- you can use the CMS without cloning the repo locally
|
|
128
|
+
- your changes still go into your private content repo
|
|
129
|
+
- if you later open that repo with git or Obsidian, you are looking at the same underlying content
|
|
111
130
|
|
|
112
|
-
|
|
131
|
+
### What to expect the first time you open it
|
|
113
132
|
|
|
114
|
-
|
|
133
|
+
When you open `https://<handle>.rizom.ai/cms`, you should expect something like this:
|
|
115
134
|
|
|
116
|
-
|
|
135
|
+
1. the CMS asks you to authenticate with GitHub
|
|
136
|
+
2. you enter the GitHub token we told you to create
|
|
137
|
+
3. the CMS loads your content collections
|
|
138
|
+
4. you can open an entry, edit it, and save your changes
|
|
117
139
|
|
|
118
|
-
If
|
|
140
|
+
If the CMS loads correctly, that is a good sign that:
|
|
119
141
|
|
|
120
|
-
|
|
142
|
+
- your browser access is working
|
|
143
|
+
- your repo access is working
|
|
144
|
+
- the token is working
|
|
121
145
|
|
|
122
|
-
|
|
146
|
+
### What you will see in the CMS
|
|
123
147
|
|
|
124
|
-
|
|
148
|
+
The exact collections may change over time, but a normal pilot setup includes collections for things like:
|
|
125
149
|
|
|
126
|
-
|
|
150
|
+
- **Notes**
|
|
151
|
+
- links or saved resources
|
|
152
|
+
- settings or other structured content
|
|
127
153
|
|
|
128
|
-
|
|
154
|
+
The important idea is not the exact list — it is that the CMS is the browser-based editor for your Rover content.
|
|
129
155
|
|
|
130
|
-
###
|
|
156
|
+
### A good first CMS task
|
|
131
157
|
|
|
132
|
-
|
|
158
|
+
A good first CMS task is to create a short note.
|
|
133
159
|
|
|
134
|
-
|
|
160
|
+
For example:
|
|
135
161
|
|
|
136
|
-
|
|
162
|
+
- open **Notes**
|
|
163
|
+
- create a new note
|
|
164
|
+
- title it something like `Why I’m using Rover`
|
|
165
|
+
- write 3 to 5 sentences
|
|
166
|
+
- save it
|
|
137
167
|
|
|
138
|
-
|
|
168
|
+
Then go back to Discord and ask Rover something like:
|
|
139
169
|
|
|
140
|
-
>
|
|
170
|
+
> What do you know about why I’m using Rover so far?
|
|
141
171
|
|
|
142
|
-
|
|
172
|
+
That connects the browser editing workflow with the chat workflow.
|
|
143
173
|
|
|
144
|
-
|
|
174
|
+
### When to use Discord vs CMS
|
|
145
175
|
|
|
146
|
-
|
|
176
|
+
A good rule of thumb is:
|
|
147
177
|
|
|
148
|
-
|
|
178
|
+
Use **Discord** when you want to:
|
|
149
179
|
|
|
150
|
-
|
|
180
|
+
- think out loud
|
|
181
|
+
- ask questions
|
|
182
|
+
- capture something quickly
|
|
183
|
+
- use Rover as a day-to-day assistant
|
|
151
184
|
|
|
152
|
-
|
|
185
|
+
Use the **CMS** when you want to:
|
|
153
186
|
|
|
154
|
-
|
|
187
|
+
- deliberately create or revise content
|
|
188
|
+
- browse existing entries
|
|
189
|
+
- make cleaner edits than you would in chat
|
|
190
|
+
- work in a more editor-like browser interface
|
|
155
191
|
|
|
156
|
-
|
|
192
|
+
Use both together. That is the default pilot workflow.
|
|
157
193
|
|
|
158
|
-
|
|
194
|
+
### If the CMS feels confusing
|
|
159
195
|
|
|
160
|
-
|
|
196
|
+
That is useful feedback.
|
|
161
197
|
|
|
162
|
-
|
|
198
|
+
Please tell us:
|
|
163
199
|
|
|
164
|
-
-
|
|
165
|
-
-
|
|
166
|
-
-
|
|
200
|
+
- what part was confusing
|
|
201
|
+
- whether the problem was authentication, navigation, editing, or saving
|
|
202
|
+
- what you expected to happen instead
|
|
167
203
|
|
|
168
|
-
|
|
204
|
+
We want to improve this workflow.
|
|
169
205
|
|
|
170
|
-
|
|
206
|
+
## Optional: direct MCP access
|
|
171
207
|
|
|
172
|
-
|
|
173
|
-
- perform an action it cannot perform yet
|
|
174
|
-
- add a workflow or feature that does not exist yet
|
|
208
|
+
If we have asked you to use an MCP client, use one that supports:
|
|
175
209
|
|
|
176
|
-
|
|
210
|
+
- **HTTP / Streamable HTTP MCP**
|
|
211
|
+
- **Bearer token authentication**
|
|
177
212
|
|
|
178
|
-
|
|
213
|
+
When your client asks for connection details, use:
|
|
179
214
|
|
|
180
|
-
|
|
215
|
+
- **Server URL:** `https://<handle>.rizom.ai/mcp`
|
|
216
|
+
- **Authentication type:** Bearer token
|
|
217
|
+
- **Bearer token:** the token we sent you
|
|
181
218
|
|
|
182
|
-
|
|
219
|
+
If the client asks for a name, use something simple like:
|
|
183
220
|
|
|
184
|
-
|
|
221
|
+
- `Rover (<handle>)`
|
|
185
222
|
|
|
186
|
-
|
|
223
|
+
## Optional: Claude Desktop setup
|
|
187
224
|
|
|
188
|
-
|
|
225
|
+
If we ask you to connect through Claude Desktop and your version supports a **remote HTTP / Streamable HTTP MCP server**, enter:
|
|
189
226
|
|
|
190
|
-
-
|
|
191
|
-
-
|
|
192
|
-
-
|
|
193
|
-
- repeated demand can increase the count of how many times that wish was requested
|
|
227
|
+
- **Server URL:** `https://<handle>.rizom.ai/mcp`
|
|
228
|
+
- **Authentication:** Bearer token
|
|
229
|
+
- **Token:** the token we sent you
|
|
194
230
|
|
|
195
|
-
|
|
231
|
+
Then try a first message like:
|
|
196
232
|
|
|
197
|
-
|
|
233
|
+
> What can you help me do, and what should I use you for?
|
|
198
234
|
|
|
199
|
-
|
|
235
|
+
Or:
|
|
200
236
|
|
|
201
|
-
|
|
237
|
+
> Help me save my first note.
|
|
202
238
|
|
|
203
|
-
If
|
|
239
|
+
If your Claude Desktop version only supports local MCP servers and not remote HTTP MCP cleanly, tell us what version you are using and we will help you.
|
|
204
240
|
|
|
205
|
-
|
|
206
|
-
- it says the request was added to the wishlist
|
|
241
|
+
## Optional: git, text files, and Obsidian
|
|
207
242
|
|
|
208
|
-
|
|
243
|
+
The underlying content workflow is still a normal **git repo** with normal **markdown/text files**.
|
|
209
244
|
|
|
210
|
-
|
|
245
|
+
But for this pilot, treat that as **optional**.
|
|
211
246
|
|
|
212
|
-
|
|
247
|
+
Use direct git or file-based workflows only if you want more control.
|
|
213
248
|
|
|
214
249
|
Obsidian is optional. It is just one possible editor for those files.
|
|
215
250
|
|
|
216
251
|
That means:
|
|
217
252
|
|
|
218
253
|
- use **Discord** as the main way to talk to Rover
|
|
219
|
-
- use
|
|
254
|
+
- use the **Dashboard** and **CMS** as the normal browser workflow
|
|
255
|
+
- use a normal editor plus **git** only if you want to browse, draft, and edit your files directly
|
|
220
256
|
- use **Obsidian** only if you want a more note-focused interface for the same files
|
|
221
257
|
- Rover can pick up those file changes through the normal git-sync / directory-sync flow
|
|
222
258
|
|
|
223
|
-
A simple mental model:
|
|
224
|
-
|
|
225
|
-
- **Discord** = talk to Rover
|
|
226
|
-
- **git repo + text files** = the underlying content
|
|
227
|
-
- **Obsidian** = an optional editor for that content
|
|
228
|
-
|
|
229
259
|
### Important: your content repo is private
|
|
230
260
|
|
|
231
261
|
If you use the git/text-file workflow, you will be working in your own **private** GitHub repo.
|
|
232
262
|
|
|
233
263
|
That means:
|
|
234
264
|
|
|
235
|
-
- you do **not** need repo access just to use Rover in Discord
|
|
265
|
+
- you do **not** need repo access just to use Rover in Discord
|
|
236
266
|
- you **do** need GitHub access if you want to clone, edit, and push to your content repo
|
|
237
267
|
- we will invite you only to **your own** content repo, not to the operator repo and not to other users' repos
|
|
238
268
|
|
|
@@ -245,28 +275,21 @@ If you want the git/text-file workflow, we will:
|
|
|
245
275
|
3. ask you to accept the GitHub invite
|
|
246
276
|
4. send you the repo URL
|
|
247
277
|
|
|
248
|
-
### Easiest setup for most users
|
|
249
|
-
|
|
250
|
-
The easiest path for most first-time users is:
|
|
251
|
-
|
|
252
|
-
1. install **GitHub Desktop**
|
|
253
|
-
2. accept the repo invite in GitHub
|
|
254
|
-
3. clone the private repo with GitHub Desktop
|
|
255
|
-
4. open the cloned folder in your normal editor and edit the markdown/text files directly
|
|
256
|
-
5. optionally open that same folder as an **Obsidian** vault if you prefer
|
|
257
|
-
6. commit and push your changes
|
|
258
|
-
|
|
259
278
|
### Authentication options
|
|
260
279
|
|
|
261
|
-
To work with a private repo, you need GitHub authentication.
|
|
280
|
+
To work with a private repo or the CMS, you need GitHub authentication.
|
|
262
281
|
|
|
263
282
|
Usually the easiest order is:
|
|
264
283
|
|
|
265
|
-
1. **GitHub
|
|
266
|
-
2. **
|
|
267
|
-
3.
|
|
284
|
+
1. **GitHub sign-in** to accept the private repo invite
|
|
285
|
+
2. a **fine-grained personal access token** for the CMS, with access to your private Rover content repo
|
|
286
|
+
3. **GitHub Desktop** or normal git auth if you also want to clone the repo locally
|
|
287
|
+
4. **SSH key** only if you already use git that way
|
|
288
|
+
|
|
289
|
+
You do **not** need a GitHub token just to use Rover in Discord.
|
|
290
|
+
You do **not** need an MCP Bearer token unless we explicitly ask you to use MCP.
|
|
268
291
|
|
|
269
|
-
|
|
292
|
+
### If you want the local file workflow
|
|
270
293
|
|
|
271
294
|
If we have already shared your content repo workflow with you, the normal setup is:
|
|
272
295
|
|
|
@@ -277,11 +300,11 @@ If we have already shared your content repo workflow with you, the normal setup
|
|
|
277
300
|
5. commit and push your changes through normal git, GitHub Desktop, or the Obsidian Git plugin
|
|
278
301
|
6. let the normal git-sync flow carry those changes into Rover
|
|
279
302
|
|
|
280
|
-
If we have **not** given you a direct content repo workflow yet, that is fine. You can ignore git, text files, and Obsidian for now and use Rover in Discord. If we have also asked you to test MCP, you can use that too.
|
|
303
|
+
If we have **not** given you a direct content repo workflow yet, that is fine. You can ignore git, text files, and Obsidian for now and use Rover in Discord and the CMS. If we have also asked you to test MCP, you can use that too.
|
|
281
304
|
|
|
282
|
-
## Discord (default)
|
|
305
|
+
## Discord (default chat interface)
|
|
283
306
|
|
|
284
|
-
Discord is the default interface for this pilot.
|
|
307
|
+
Discord is the default chat interface for this pilot.
|
|
285
308
|
|
|
286
309
|
Think of it as the main place to:
|
|
287
310
|
|
|
@@ -292,13 +315,82 @@ Think of it as the main place to:
|
|
|
292
315
|
|
|
293
316
|
Important:
|
|
294
317
|
|
|
295
|
-
- **Discord is the main pilot interface
|
|
318
|
+
- **Discord is the main pilot chat interface**
|
|
319
|
+
- the **Dashboard** and **CMS** are the main browser interfaces
|
|
296
320
|
- MCP is **optional**
|
|
297
321
|
- if Discord is enabled, we will send the exact invite/setup steps separately
|
|
298
322
|
- for some pilot setups, Discord-enabled users may need to supply their own bot token
|
|
299
323
|
|
|
300
324
|
If Discord is **not** enabled for you yet, ask us and we will tell you whether your cohort is on the Discord-first workflow.
|
|
301
325
|
|
|
326
|
+
## Dashboard basics
|
|
327
|
+
|
|
328
|
+
The Dashboard is the browser landing page for your Rover.
|
|
329
|
+
|
|
330
|
+
Use it when you want to:
|
|
331
|
+
|
|
332
|
+
- confirm the instance is up
|
|
333
|
+
- see the browser-side operator surface
|
|
334
|
+
- jump into the CMS quickly
|
|
335
|
+
|
|
336
|
+
This is not meant to be a public website. It is part of your Rover control surface.
|
|
337
|
+
|
|
338
|
+
## Wishlist: when Rover cannot do something yet
|
|
339
|
+
|
|
340
|
+
Rover has a built-in **wishlist**.
|
|
341
|
+
|
|
342
|
+
This matters because Rover will not be able to do everything yet.
|
|
343
|
+
|
|
344
|
+
If you ask for something Rover cannot do, it should add that request to the wishlist instead of just failing silently.
|
|
345
|
+
|
|
346
|
+
You can think of the wishlist as:
|
|
347
|
+
|
|
348
|
+
- a backlog of missing capabilities
|
|
349
|
+
- a record of things users want Rover to do
|
|
350
|
+
- a way for the pilot team to see which missing features matter most
|
|
351
|
+
|
|
352
|
+
### When the wishlist is useful
|
|
353
|
+
|
|
354
|
+
The wishlist is especially useful when you ask Rover to do something like:
|
|
355
|
+
|
|
356
|
+
- connect to a tool it does not support yet
|
|
357
|
+
- perform an action it cannot perform yet
|
|
358
|
+
- add a workflow or feature that does not exist yet
|
|
359
|
+
|
|
360
|
+
Examples:
|
|
361
|
+
|
|
362
|
+
> I want Rover to draft and send emails for me.
|
|
363
|
+
|
|
364
|
+
> I want Rover to connect to my calendar.
|
|
365
|
+
|
|
366
|
+
> I want Rover to summarize voice notes automatically.
|
|
367
|
+
|
|
368
|
+
If Rover cannot actually do those things yet, it should tell you that and add the request to the wishlist.
|
|
369
|
+
|
|
370
|
+
### What happens when something is added to the wishlist
|
|
371
|
+
|
|
372
|
+
When a request is added to the wishlist:
|
|
373
|
+
|
|
374
|
+
- it is saved as a **wish**
|
|
375
|
+
- it starts in a **new** state
|
|
376
|
+
- similar requests can be grouped together instead of creating endless duplicates
|
|
377
|
+
- repeated demand can increase the count of how many times that wish was requested
|
|
378
|
+
|
|
379
|
+
That helps us see which gaps are one-off ideas and which ones keep coming up across real usage.
|
|
380
|
+
|
|
381
|
+
### How you should use it
|
|
382
|
+
|
|
383
|
+
You do **not** need special commands.
|
|
384
|
+
|
|
385
|
+
Just ask naturally.
|
|
386
|
+
|
|
387
|
+
If Rover cannot do what you asked, a good response from Rover is something like:
|
|
388
|
+
|
|
389
|
+
- it explains the limitation clearly
|
|
390
|
+
- it says the request was added to the wishlist
|
|
391
|
+
|
|
392
|
+
If that does **not** happen, that is useful feedback for us too.
|
|
393
|
+
|
|
302
394
|
## What to expect in the pilot
|
|
303
395
|
|
|
304
396
|
This is a real working system, but it is still an early pilot.
|
|
@@ -319,15 +411,40 @@ For the pilot:
|
|
|
319
411
|
|
|
320
412
|
- your Rover is deployed specifically for you
|
|
321
413
|
- if you are using MCP, access to `/mcp` is protected by your Bearer token
|
|
414
|
+
- your content repo is private
|
|
322
415
|
- you should avoid putting highly sensitive material into the pilot unless we have explicitly agreed that it is in scope
|
|
323
416
|
|
|
324
417
|
If you are unsure whether something belongs in Rover, ask us first.
|
|
325
418
|
|
|
326
419
|
## Troubleshooting
|
|
327
420
|
|
|
328
|
-
### I opened the domain and it does not look like a normal site
|
|
421
|
+
### I opened the domain and it does not look like a normal public site
|
|
422
|
+
|
|
423
|
+
That is expected. The root URL is your **Dashboard**, not a public website. The CMS lives at `/cms`. Rover also runs through Discord and, optionally, a direct MCP endpoint.
|
|
424
|
+
|
|
425
|
+
### The CMS asks for GitHub auth and I am not sure what to do
|
|
426
|
+
|
|
427
|
+
That is expected.
|
|
428
|
+
|
|
429
|
+
Use the GitHub token we told you to create for your **private Rover content repo**.
|
|
430
|
+
|
|
431
|
+
If you are missing one of these pieces, tell us:
|
|
432
|
+
|
|
433
|
+
- you did not get the repo invite
|
|
434
|
+
- you did not accept the repo invite yet
|
|
435
|
+
- you are not sure how to create the token
|
|
436
|
+
- the token was accepted but the CMS still does not load
|
|
437
|
+
|
|
438
|
+
### The CMS loads, but I am not sure whether my change worked
|
|
439
|
+
|
|
440
|
+
A good quick test is:
|
|
441
|
+
|
|
442
|
+
1. edit a short note in the CMS
|
|
443
|
+
2. save it
|
|
444
|
+
3. refresh the CMS and confirm the change is still there
|
|
445
|
+
4. ask Rover in Discord about that note
|
|
329
446
|
|
|
330
|
-
|
|
447
|
+
If anything in that loop feels unclear, tell us exactly where it became confusing.
|
|
331
448
|
|
|
332
449
|
### I got an authentication error in MCP
|
|
333
450
|
|
|
@@ -359,6 +476,7 @@ If that happens, send us:
|
|
|
359
476
|
We especially want to hear:
|
|
360
477
|
|
|
361
478
|
- what was confusing during setup
|
|
479
|
+
- whether Discord, Dashboard, and CMS each made sense
|
|
362
480
|
- what felt useful immediately
|
|
363
481
|
- what felt weak, awkward, or unclear
|
|
364
482
|
- what you expected Rover to do but could not get it to do
|
|
@@ -373,6 +491,9 @@ When we onboard you, the message will look roughly like this:
|
|
|
373
491
|
```text
|
|
374
492
|
Discord enabled: yes/no
|
|
375
493
|
Discord setup: <invite link or setup steps>
|
|
494
|
+
Dashboard URL: https://<handle>.rizom.ai/
|
|
495
|
+
CMS URL: https://<handle>.rizom.ai/cms
|
|
496
|
+
CMS auth: GitHub token with access to your private Rover content repo
|
|
376
497
|
MCP access: optional / enabled / not enabled
|
|
377
498
|
|
|
378
499
|
If MCP is enabled:
|