Moduletrace/cobble
2
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases 11 Wiki Activity

Add bot schedules (routines), open Activity, add Help and a Desktop computer view

Browse Source 
Bots create, list, update and delete schedules (cron_jobs, Bun.cron in UTC);
a per-minute cron queues due runs as tasks. Routines, Activity (super admins)
and Help get their own rail aside. Help covers familiar problems, starting
with signing in to Google through Cookie-Editor over the new Desktop (noVNC)
view.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
tben
2026-10-19 10:52:32 +01:00
co-authored by Claude Opus 5.5
parent f24c0d7e82
commit c44048dbab
62 changed files with 1904 additions and 78 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/pages/admin/help/(data)/help-topics.ts
+103
View File
@@ -0,0 +1,103 @@
import { HelpSignInTopicId } from "@/src/dict/help-dict";
export type HelpTopic = {
/**
* The anchor: `/admin/help#<id>` opens the page at it.
*/
id: string;
title: string;
/**
* One line under the title: when this is the topic you need.
*/
summary: string;
/**
* The answer, in markdown.
*/
body: string;
};
/**
* The help page: familiar problems and how to get past them, the most
* common first.
*/
export const HelpTopics: HelpTopic[] = [
{
id: HelpSignInTopicId,
title: "Google won't let me sign in on a computer",
summary: `"This browser or app may not be secure", "Couldn't sign you in", or a sign-in that loops. Google and some other sites do this.`,
body: `Your bots drive the browser on their computers, and Google (like some banks and social sites) refuses sign-ins from browsers it can tell are automated. Typing the password yourself doesn't help: the browser itself is turned away.
The way around it is to sign in on your own browser, where Google trusts you, and carry that session over to the computer with the **Cookie-Editor** extension.
**Before you start:** the cookies you copy *are* your signed-in session. Anyone who has them is signed in as you, without a password. Never paste them into a chat with a bot, don't keep them in a file, and clear them when you're done (step 9).
### On your own browser
1. In Chrome (or Edge, Brave, any Chromium browser), install [Cookie-Editor](https://chromewebstore.google.com/detail/cookie-editor/hlkenndednhfkekhgcdicdfddnkalmdm) from the Chrome Web Store.
2. Sign in to the site with the account your bot should use. For Google, go to [myaccount.google.com](https://myaccount.google.com) and sign in.
3. Still on that site, click the extensions icon (the puzzle piece) in the toolbar, then **Cookie-Editor**. Click **Export**, then **JSON**. The cookies are now on your clipboard.
### On the bot's computer
4. Open the computer: in the bot's chat, click the computer icon in the header and open the computer, or click **Take over** if the bot asked you to. Switch to **Desktop**. This is the only view that shows the browser's toolbar, where extensions live.
5. The first time only: in the computer's Chrome, open the [Cookie-Editor page](https://chromewebstore.google.com/detail/cookie-editor/hlkenndednhfkekhgcdicdfddnkalmdm), click **Add to Chrome**, then **Add extension**. Pin it from the puzzle piece so it's always one click away. It stays installed: the computer keeps its browser between restarts.
6. In the computer's Chrome, go to the same site (for Google, [myaccount.google.com](https://myaccount.google.com)). It's fine that it shows the sign-in page.
7. Put the cookies on the computer's clipboard. Desktop has a small handle on the left edge: open it, click the **Clipboard** icon, and paste into the box (Ctrl+V, or Cmd+V on a Mac). What's in that box is the computer's clipboard.
8. Click **Cookie-Editor** in the computer's toolbar, then **Import**. Click into the box, paste (Ctrl+V), and click **Import**. Reload the page (F5): you're signed in.
9. Clean up: open the **Clipboard** panel again and clear it.
Then tell the bot you're signed in, or click **Hand back** if it asked you to take over, and it carries on.
### If it doesn't work
- **The paste in step 7 or 8 is empty.** Use the computer's code editor instead: switch to **Code**, create a file such as \`cookies.json\`, and paste into it (that paste always works). In the computer's Chrome, open \`file:///home/gem/cookies.json\`, press Ctrl+A then Ctrl+C, and import as in step 8. **Delete the file afterwards.**
- **You're signed in, then signed out again soon after.** Google sometimes ends a session it sees used from a new place. Sign out and back in on your own browser, export again, and import straight away. Using the same account and keeping the bot's work regular helps the session last.
- **Cookie-Editor's icon doesn't show.** You're in the **Browser** view, which shows pages only. Switch to **Desktop**.
- **Another site still says no.** Make sure you exported while on that site (Cookie-Editor exports the cookies of the site you're on), and that you opened the same site on the computer before importing.`,
},
{
id: "take-over",
title: "A bot asks me to take over",
summary: "A message with a Take over button, and the bot shows it needs you.",
body: `Some things only you can do on a computer: sign in, solve a captcha, type a code sent to your phone, approve a prompt. The bot stops there and asks you to take over.
1. Click **Take over** in its message. The computer opens in the view the bot picked (browser, terminal, code or desktop).
2. Do what it asked. You're using the same computer the bot works on.
3. Click **Hand back to** the bot. It gets a message that you're done and carries on.
A task that hit the wall stops and reports instead of waiting, so after you hand back the bot picks the work up again from the chat.`,
},
{
id: "computer-not-ready",
title: "A computer is stuck on Creating, or isn't ready",
summary: "Tasks fail with \"isn't ready\", or the computer never leaves Creating.",
body: `A new computer downloads its image and starts up, which can take a few minutes the first time. It stays **Creating** until its health check passes (its sandbox and browser both answer).
- **Still Creating after several minutes, or Failed:** open **Settings, Computers** and look at its state. A super admin can **Retry** it there; the error shows on the row.
- **Unhealthy or stopped:** the computer's container is down or struggling. Give it more memory or CPUs from **Edit** (it restarts, its files are kept), or retry it.
- **Everything fails at once:** the app needs Docker on the machine it runs on. Check that Docker is running.
A computer's home folder lives in the app's data folder on the machine, so restarting or recreating its container never loses its files.`,
},
{
id: "bot-asleep",
title: "A bot is asleep, or says no model is available",
summary: "Its face is asleep and replies wait, or tasks fail naming the models.",
body: `Bots think with AI models. By default they use free models, which are shared and rate limited: when every model a bot can use is resting, it falls asleep and its work waits until the first one comes back. Nothing is lost.
To make this rarer, a super admin can open **Settings, Models**:
- Add a provider with your own API key (OpenRouter, OpenAI, Anthropic, Gemini and others), so paid models are there when free ones rest.
- Pick a model for the text harness instead of automatic, and keep **fallback** on so the automatic picks still step in.
A bot's own models (the model icon in its chat header) win over the defaults, and a workspace's win over a bot's.`,
},
{
id: "routine-time",
title: "A routine runs at the wrong time",
summary: "It runs hours early or late.",
body: `Routines run on UTC, not your local time. A routine set for \`0 9 * * *\` runs at 09:00 UTC.
Tell the bot your time zone once ("I'm in Lagos", "I'm on New York time") and it remembers it and converts for you. To fix one yourself, open **Routines**, click **Edit**, and change the schedule to the UTC hour you want. Routines don't follow daylight saving changes, so ones near a clock change may need a nudge twice a year.`,
},
];
src/pages/admin/help/(partials)/help-topic-group.tsx
+23
View File
@@ -0,0 +1,23 @@
import Markdown from "react-markdown";
import remarkGfm from "remark-gfm";
import Stack from "@moduletrace/twui/layout/Stack";
import { MessageMarkdownComponents } from "@/src/pages/admin/bots/[bot_id]/(data)/message-markdown-components";
import SettingsGroup from "@/src/pages/admin/settings/(partials)/settings-group";
import type { HelpTopic } from "../(data)/help-topics";
/**
* One help topic: the problem and when you'd see it on the left, the
* answer (markdown, rendered like a bot message) on the right. Its id is
* the anchor bots and other pages link to.
*/
export default function HelpTopicGroup({ id, title, summary, body }: HelpTopic) {
return (
<SettingsGroup id={id} title={title} description={summary}>
<Stack className="gap-3! items-stretch min-w-0">
<Markdown remarkPlugins={[remarkGfm]} components={MessageMarkdownComponents}>
{body}
</Markdown>
</Stack>
</SettingsGroup>
);
}
src/pages/admin/help/(sections)/help-topics-section.tsx
+15
View File
@@ -0,0 +1,15 @@
import { HelpTopics } from "../(data)/help-topics";
import HelpTopicGroup from "../(partials)/help-topic-group";
/**
* Every help topic, one block each.
*/
export default function HelpTopicsSection() {
return (
<>
{HelpTopics.map((topic) => (
<HelpTopicGroup key={topic.id} {...topic} />
))}
</>
);
}
src/pages/admin/help/index.tsx
+19
View File
@@ -0,0 +1,19 @@
import type { BunextPageModuleMetaFn } from "@moduletrace/bunext/types";
import { SiteData } from "@/src/data/site-data";
import SettingsShell from "@/src/pages/admin/settings/(partials)/settings-shell";
import HelpTopicsSection from "./(sections)/help-topics-section";
export default function AdminHelpPage() {
return (
<SettingsShell title="Help" description="Familiar problems, and how to get past them.">
<HelpTopicsSection />
</SettingsShell>
);
}
export const meta: BunextPageModuleMetaFn = async () => {
return {
title: `Help | ${SiteData["SiteName"]}`,
description: `Familiar problems on ${SiteData["SiteName"]}, and how to get past them.`,
};
};