paseo-aydo 0.3.0 → 0.4.1

package/LICENSE

@@ -1,7 +1,7 @@
 MIT License
 
-Copyright (c) 2026 Ondrej Rehacek
 Copyright (c) 2026 Qiang Wei
+Copyright (c) 2026 Ondrej Rehacek
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

package/NOTICE

@@ -1,16 +1,30 @@
-Aydo (offline edition)
+Aydo
 
-Based on oliexe/paseo-bots, Copyright (c) 2026 Ondrej Rehacek, MIT License (see LICENSE).
+Copyright (c) 2026 Qiang Wei. Based on oliexe/paseo-bots, Copyright (c) 2026 Ondrej Rehacek, MIT License (see LICENSE).
 
-The design of the bots (teams with a Chief of Staff, memory and its journal, playbooks,
-routines and webhooks, saved commands, presets, skill review, the way one bot asks another)
-follows OpenMausBot, https://github.com/milind-soni/OpenMausBot, licensed under the
-Apache License 2.0. Where this code is derived from it, the Apache License 2.0 applies to
-that part: https://www.apache.org/licenses/LICENSE-2.0
+Parts adapted from OpenMausBot
+------------------------------
+https://github.com/milind-soni/OpenMausBot
+Copyright 2026 Milind Soni and OpenMausBot contributors
+Licensed under the Apache License, Version 2.0. The licence text is in licenses/Apache-2.0.txt
+(https://www.apache.org/licenses/LICENSE-2.0). The Apache License 2.0 applies to the parts below, which were
+changed from the original:
 
-The names OpenMausBot and MausBot and its mascot are trademarks of Supamaus Software Private
-Limited. This project is not affiliated with or endorsed by them and does not use their
-names for itself; they appear in comments only to say which design a piece of code follows.
+  - shared/playbooks.ts: choosing playbooks by trigger words (adapted from server/installed-playbooks.ts).
+  - shared/skills.ts, scanSkillText: the checks run on a skill before a bot gets it (adapted from shared/skill-md.ts).
 
-This edition changes the original: it removes everything that connects to the network, and
-adds memory upkeep, Devin support and bot tools as files, and follow-up questions between bots.
+The design of the bots (teams with a Chief of Staff, memory and its journal, playbooks, routines and webhooks,
+saved commands, presets, skill review, the way one bot asks another) also follows OpenMausBot; those parts were
+written independently, and comments in the code say which design a piece follows. A few short constants and
+sentences (memory size limits, webhook limits, one sentence of the prompt about past notes) match it as well.
+
+The names OpenMausBot and MausBot and its mascot are trademarks of Supamaus Software Private Limited. This project
+is not affiliated with or endorsed by them and does not use their names for itself; they appear in comments only to
+say which design a piece of code follows.
+
+Changes in this edition
+-----------------------
+This edition changes the original: it removes everything that connects to the network, and adds memory upkeep,
+Devin support and bot tools as files, follow-up questions between bots, approvals, project workspaces, and
+Chinese (zh-CN) support. These changes suit deployments with restricted environments, such as no outbound network access
+or limits on which tools a provider may use.

package/README.md

@@ -2,21 +2,21 @@
   <img src="docs/bots.svg" width="512" alt="Six pixel-art assistants">
 </p>
 
-# Aydo, offline edition
+# Aydo
 
-Aydo: personal assistants for [Paseo](https://paseo.sh) and Irix: give each assistant instructions, a model, memory, skills and tools, then chat with it in its own workspace or let it run routines.
+Aydo: personal assistants for [Paseo](https://paseo.sh): give each assistant instructions, a model, memory, skills and tools, then chat with it in its own workspace or let it run routines.
 
 Aydo is based on [oliexe/paseo-bots](https://github.com/oliexe/paseo-bots) 0.2.0 (MIT, by Ondrej Rehacek) for machines that must not send data to cloud services. **The plugin makes no network connections of its own.** Everything that needed one is gone, and a test keeps it that way.
 
 ## What is different
 
-| Upstream feature | Offline edition |
+| Upstream feature | Aydo |
 | --- | --- |
 | Connected apps through Composio (Gmail, Slack, Notion, 1,000+ more) | Removed, with its relay proxy, API key, sign-in cards and the roles built on it (Inbox, Watch, Ops) |
 | Avatar pictures drawn by OpenAI | Removed; pixel-art faces, and pictures you upload |
 | Pictures from an image address | Removed; a picture is kept only as an uploaded `data:` image |
 | Importing skills from GitHub or a link | Imports from **a folder on this computer** instead |
-| Testing MCP servers at a remote address (HTTP, SSE) | The plugin only tests programs and `http://localhost` addresses. A remote server (for example one inside your company) is imported and can be turned on without a test; the assistant's agent is the one that connects to it |
+| Testing MCP servers at a remote address (HTTP, SSE) | The plugin only tests programs and `http://localhost` addresses. A remote server (for example one on a private network) is imported and can be turned on without a test; the assistant's agent is the one that connects to it |
 | GitHub link on the start screen | Removed |
 
 Everything else is unchanged: assistants, memory, routines and webhooks, teams, the skill and MCP library, `/learn`, Paseo's own tools for assistants, and sharing assistants and teams as files.
@@ -41,21 +41,20 @@ Everything else is unchanged: assistants, memory, routines and webhooks, teams,
 
 ## Install
 
-Get the plugin folder onto the machine (the offline package unzips into one), then install it from that folder.
+Get the plugin folder onto the machine (the package unzips into one), then install it from that folder.
 
 ``bash
-irix plugin install /path/to/aydo          # Irix
-paseo plugin install /path/to/aydo         # Paseo
+paseo plugin install /path/to/aydo
 ``
 
-Turn on **Settings → Plugins → Enable plugins** first. Requires Paseo 0.13 or later. Aydo shows in English and Chinese (zh-CN), following the Paseo/Irix language setting. Irix installs plugins from a local folder only, which is what this edition is for.
+Turn on **Settings → Plugins → Enable plugins** first. Requires Paseo 0.13 or later. Aydo shows in English and Chinese (zh-CN), following the Paseo language setting. Plugins install from a local folder, which is what this edition is for.
 
 ## Usage
 
 ### Assistants
 
 1. Open **Aydo** in Paseo's sidebar and press **New assistant**. Start blank, from a role, from one of your presets, or paste an assistant or team file under **Import**.
-2. Chat with it. Every chat is a thread in the assistant's workspace; **Open in Paseo** in a chat's menu shows it in Paseo's own view. On Irix builds that offer the embedded chat (`ui.AgentView`), an open chat is Irix's own chat view inside the Assistants page, so the model, mode and thinking pickers, slash commands and other plugins' cards work there too; the first message of a new chat is still typed in the plugin's own box, because it builds the assistant's system prompt. On Paseo without it, the plugin's own chat window is used.
+2. Chat with it. Every chat is a thread in the assistant's workspace; **Open in Paseo** in a chat's menu shows it in Paseo's own view. On hosts that offer an embedded chat (`ui.AgentView`), an open chat is the host's own chat view inside the Assistants page, so the model, mode and thinking pickers, slash commands and other plugins' cards work there too; the first message of a new chat is still typed in the plugin's own box, because it builds the assistant's system prompt. On Paseo without it, the plugin's own chat window is used.
 3. Open its settings with the panel button at the top right of a chat, or **Open assistant settings** in the assistant's menu. **Identity** holds the name, avatar and voice, **Soul** its standing instructions, **Model** the provider and model, and **Permissions** the approval mode.
 
 Assistants can do the setting up too. Ask one in a chat, for example "Create a research team of three assistants with Scout as Chief of Staff", and it shows every change on one card; **Apply changes** makes them. An assistant can create, edit and delete assistants, teams, routines, library skills and MCP servers, and change what new assistants start with. Each assistant's earlier settings stay under **History** in its settings.
@@ -122,22 +121,22 @@ After a task, send `/learn` in the chat, or `/learn <what to focus on>`. The ass
 
 Assistants get Paseo's own tools, so you can ask one in a chat to start other agents, open workspaces and terminals, set up schedules or use the browser. An assistant's **Access** settings show whether they're on, and **Turn on** there switches them on for every agent on the host.
 
-## Building the offline package
+## Building the package
 
 ``bash
 npm ci --ignore-scripts
 npm run typecheck && npm test
-node scripts/pack-offline.mjs --out ../aydo-offline
+node scripts/pack.mjs --out ../aydo-dist
 ``
 
 The package is a zip of the plugin's source files only (the daemon compiles them when the plugin starts). It has no runtime dependencies, so installing it needs no npm and no internet.
 
-`tests/offline.test.ts` scans the whole source for network code (`fetch`, sockets, WebSocket, a remote address in code, an image loaded from an address) and fails if it finds any outside the one MCP probe, which refuses everything but this computer (remote MCP servers are the agent's to connect to). Run it after every change.
+`tests/no-network.test.ts` scans the whole source for network code (`fetch`, sockets, WebSocket, a remote address in code, an image loaded from an address) and fails if it finds any outside the one MCP probe, which refuses everything but this computer (remote MCP servers are the agent's to connect to). Run it after every change.
 
 ## Staying close to upstream
 
-`upstream` is the original repository. Merge it into the `offline` branch from time to time; the removed features will conflict, and the test above will tell you if a merge brings network code back.
+`upstream` is the original repository. Merge it from time to time; the removed features will conflict, and the test above will tell you if a merge brings network code back.
 
 ## License
 
-MIT, as upstream. See `LICENSE`. The design follows OpenMausBot (Apache-2.0); see `NOTICE`.
+MIT, as upstream. See `LICENSE`. Parts are adapted from OpenMausBot (Apache-2.0) and the design follows it; see `NOTICE` and `licenses/`.

package/client/native-agent-view.ts

@@ -2,7 +2,7 @@ import * as hostUi from "@getpaseo/plugin/client/ui";
 import type { ComponentType } from "react";
 
 /**
- * Paseo's own chat view for one agent. Irix adds it to `@getpaseo/plugin/client/ui`; stock Paseo
+ * Paseo's own chat view for one agent. A host may add it to `@getpaseo/plugin/client/ui`; stock Paseo
  * does not have it, so the plugin looks for it at run time and keeps its own chat window otherwise.
  */
 export interface NativeAgentViewProps {

package/client/panel/ApprovalsList.tsx

@@ -20,7 +20,7 @@ interface ApprovalsListProps {
 
 /**
  * Every approval a bot asked for: what waits for the user first (decided here, on the same card as in the chat),
- * then the history with who decided and when. The audit file behind it keeps more (docs/superpowers/specs/2026-10-21-approvals-design.md).
+ * then the history with who decided and when. The audit file behind it keeps more (docs/specs/2026-10-21-approvals-design.md).
  */
 export function ApprovalsList({ colors, compact, onBack, onOpenChat }: ApprovalsListProps) {
   const { t } = useT();

package/index.client.tsx

@@ -24,7 +24,7 @@ export default function contribute(client: PluginClientContext) {
   else client.addSurface("bots", BotsSurface);
   // The row is ours on every host (Paseo 0.13 and later have addSidebarHeaderItem): one status dot for all assistants. The host shows
   // one row per plugin and keeps the host in its own picker on the screen, so neither names a host.
-  client.addSidebarHeaderItem({ id: "bots", title: "Aydo", Component: BotsNav });
+  client.addSidebarHeaderItem({ id: "bots", title: messages.message("host.sidebarTitle"), Component: BotsNav });
   client.addSettingsScreen({ id: "bots", title: "Aydo", icon: "Bot", Component: BotsSettings });
   client.addCommandCenterItem({
     id: "open-bots",

package/licenses/Apache-2.0.txt

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "{}"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright {yyyy} {name of copyright owner}
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/package.json

@@ -1,12 +1,13 @@
 {
   "name": "paseo-aydo",
-  "version": "0.3.0",
+  "version": "0.4.1",
   "publishConfig": {
     "access": "public"
   },
   "files": [
     "paseo-plugin.json",
     "NOTICE",
+    "licenses/",
     "tsconfig.json",
     "index.client.ts",
     "index.client.tsx",
@@ -19,7 +20,7 @@
   "scripts": {
     "typecheck": "tsc --noEmit",
     "test": "vitest run",
-    "pack:offline": "node scripts/pack-offline.mjs"
+    "pack": "node scripts/pack.mjs"
   },
   "devDependencies": {
     "@getpaseo/client": "^0.14.0",
@@ -33,7 +34,7 @@
     "vitest": "^4.1.11",
     "zod": "^4.4.3"
   },
-  "description": "Personal bots for Paseo and Irix: instructions, a model, memory, routines, teams, skills and local MCP tools. Offline edition: makes no network connections of its own.",
+  "description": "Personal assistants for Paseo: instructions, a model, memory, routines, teams, skills and local MCP tools. Makes no network connections of its own.",
   "license": "MIT",
   "author": "Qiang Wei",
   "keywords": [
@@ -41,7 +42,6 @@
     "paseo-plugin",
     "bots",
     "agents",
-    "mcp",
-    "offline"
+    "mcp"
   ]
 }

package/paseo-plugin.json

@@ -1,6 +1,6 @@
 {
   "id": "aydo",
-  "description": "Aydo: personal assistants with their own instructions, agent, memory, routines, skills and local tools. Offline edition: no network connections of its own.",
+  "description": "Aydo: personal assistants with their own instructions, agent, memory, routines, skills and local tools. No network connections of its own.",
   "requirements": {
     "paseo": ">=0.13.0"
   }

package/server/approvals.ts

@@ -13,7 +13,7 @@ import { workspaceOfChat } from "./workspaces";
 
 // A bot puts a matter to the user and waits. The card is decided by the user only (the RPCs in index.server.ts); the
 // plugin stops the asking chat as far as it can, holds what it would send into it (server/chat-send.ts), checks an
-// approval a bot cites, and records everything in the audit (docs/superpowers/specs/2026-10-21-approvals-design.md).
+// approval a bot cites, and records everything in the audit (docs/specs/2026-10-21-approvals-design.md).
 
 const INTERRUPT_TEXT = "[Aydo] STOP: your request for the user's approval is waiting. Do not run anything else; reply only with the word WAITING. The user's answer will arrive here as a message.";
 

package/server/bot-home.ts

@@ -16,14 +16,14 @@ export function pluginDataPath(): string {
 /**
  * One folder for every bot that uses the managed folder. Paseo files each agent
  * under the workspace of its folder, so sharing it keeps all bot chats in a
- * single workspace; Paseo names the project after the folder, hence "Aydo" (it was "Bots" until offline.65).
+ * single workspace; Paseo names the project after the folder, hence "Aydo" (it was "Bots" until build 65).
  */
 export function botsHomePath(): string {
   // Nested because macOS folders are case-insensitive and "bots" held per-bot folders in v0.1.
   return join(pluginDataPath(), "shared", "Aydo");
 }
 
-/** The folder of versions before offline.65. Kept as a link to botsHomePath so chats and workspaces made there still work. */
+/** The folder of versions before build 65. Kept as a link to botsHomePath so chats and workspaces made there still work. */
 function previousHomePath(): string {
   return join(pluginDataPath(), "shared", "Bots");
 }

package/server/host-caps.ts

@@ -1,7 +1,7 @@
 import { hostCaps, type HostCaps } from "../shared/host-caps";
 
 /**
- * What the host announces about itself in the IRIX_HOST_CAPS environment variable (a JSON object, set by Irix
+ * What the host announces about itself in the IRIX_HOST_CAPS environment variable (a JSON object, set by the host
  * when it starts). Stock Paseo sets nothing, so every capability is false there.
  */
 export function readHostCaps(env: Record<string, string | undefined> = process.env): HostCaps {

package/server/workspaces.ts

@@ -1,4 +1,5 @@
 import { lstat, mkdir } from "node:fs/promises";
+import { join } from "node:path";
 import { isBotsProjectRoot } from "../shared/chat";
 import { allPages } from "../shared/pages";
 import { grantScope, workspaceInputProblem, folderNameFor, type CreateWorkspaceInput } from "../shared/workspaces";
@@ -109,7 +110,7 @@ export async function createWorkspace(paseo: PaseoApi, project: ProjectRef, inpu
     const handle = await paseo.workspaces.create({ title: input.title, source: { kind: "worktree", projectId: project.id, ...(input.base ? { baseBranch: input.base } : {}), branchName } });
     return `${created(input.title, handle.id, handle.directory ?? "unknown")} Paseo adds a number to the branch name when it was taken; run git branch in the folder to see the real one.`;
   }
-  const path = `${project.root.replace(/[\\/]+$/, "")}/${folderNameFor(input.title)}`;
+  const path = join(project.root, folderNameFor(input.title));
   const entries = await workspaceEntries(paseo);
   const have = entries.find((entry) => !isArchiving(entry) && entry.projectId === project.id && samePath(directoryOf(entry), path));
   if (have) return `Workspace "${input.title}" already exists: id ${have.id}, folder ${directoryOf(have)}.`;

package/shared/approvals.ts

@@ -3,7 +3,7 @@ import { botToolName } from "./bot-tools";
 import { englishTranslate, type Translate } from "./translate";
 
 // An approval is a matter a bot puts to the user and then waits for. Unlike a proposal card it blocks the asking
-// chat until the user decides, and every one is recorded for audit (docs/superpowers/specs/2026-10-21-approvals-design.md).
+// chat until the user decides, and every one is recorded for audit (docs/specs/2026-10-21-approvals-design.md).
 
 export const ApprovalStatusSchema = z.enum(["pending", "approved", "rejected", "withdrawn"]);
 

package/shared/host-caps.ts

@@ -1,5 +1,5 @@
 /**
- * What the host (Paseo or Irix) does for providers that the plugin cannot see for itself. Everything is
+ * What the host (Paseo or another host) does for providers that the plugin cannot see for itself. Everything is
  * false until the host says otherwise, which is how stock Paseo behaves.
  */
 export interface HostCaps {

package/shared/identity.ts

@@ -2,7 +2,7 @@ import type { PromptSection } from "./bot";
 import { NO_HOST_CAPS, type HostCaps } from "./host-caps";
 
 // A bot's identity (persona, standing instructions, memory, skills) reaches Devin as an always-on
-// rule file in the bot's folder: stock Paseo gives Devin no system prompt channel over ACP (Irix injects one into
+// rule file in the bot's folder: stock Paseo gives Devin no system prompt channel over ACP (a host may inject one into
 // the first message), but Devin reads `.devin/rules/*.md` that say `trigger: always_on`, and takes a snapshot
 // when a chat is created.
 

package/shared/locales/en.json

@@ -8,6 +8,7 @@
     "settingsUnreadable": "Settings can't be read."
   },
   "host": {
+    "sidebarTitle": "Aydo",
     "openBots": "Open Assistants",
     "newBot": "New assistant",
     "learn": "Save what the assistant just did as a skill",
@@ -208,7 +209,7 @@
     },
     "folders": {
       "attached": "In a project folder this assistant's own folder is attached, so writes to it ask exactly what edits in the project ask in the assistant's approval mode (Always ask asks every time).",
-      "devinNotAttached": "In a project folder this assistant keeps its identity only if the host injects the system prompt (Irix does, stock Paseo drops it), and its writes to its own folder ask once per session (the host does not attach it yet).",
+      "devinNotAttached": "In a project folder this assistant keeps its identity only if the host injects the system prompt (stock Paseo drops it), and its writes to its own folder ask once per session (the host does not attach it yet).",
       "antigravity": "It never asks for approval. Its tools are files, since it cannot take the plugin's MCP server."
     },
     "tool": {
@@ -1328,13 +1329,13 @@
     "copyName": "{{name}} copy",
     "assistant": {
       "name": "Assistant",
-      "title": "General assistant",
-      "description": "Answers questions, drafts text, and takes on whatever you hand it."
+      "title": "Everyday helper",
+      "description": "Handles questions, writing and small jobs you pass along."
     },
     "research": {
       "name": "Scout",
-      "title": "Researcher",
-      "description": "Digs through the web and your files, and comes back with a sourced brief."
+      "title": "Research assistant",
+      "description": "Searches the web and your files and returns a short, sourced summary."
     }
   }
 }

package/shared/locales/zh-CN.json

@@ -8,6 +8,7 @@
     "settingsUnreadable": "无法读取设置。"
   },
   "host": {
+    "sidebarTitle": "Aydo 个人助理",
     "openBots": "打开助理",
     "newBot": "新建助理",
     "learn": "把助理刚做的事存成技能",
@@ -205,7 +206,7 @@
     },
     "folders": {
       "attached": "在项目文件夹中，此助理自己的文件夹会被附加进来，因此写入它时的询问方式与在项目中编辑相同，取决于助理的批准模式（“总是询问”时每次都问）。",
-      "devinNotAttached": "在项目文件夹中，只有当宿主注入系统提示时此助理才保留它的身份（Irix 会注入，原版 Paseo 会丢弃），并且它对自己文件夹的写入每个会话询问一次（宿主尚未附加该文件夹）。",
+      "devinNotAttached": "在项目文件夹中，只有当宿主注入系统提示时此助理才保留它的身份（原版 Paseo 会丢弃），并且它对自己文件夹的写入每个会话询问一次（宿主尚未附加该文件夹）。",
       "antigravity": "它从不请求批准。它的工具是文件，因为它无法使用插件的 MCP 服务器。"
     },
     "tool": {
@@ -1300,13 +1301,13 @@
     "copyName": "{{name}} 副本",
     "assistant": {
       "name": "助理",
-      "title": "通用助理",
-      "description": "回答问题、起草文本，并处理你交给它的任何事情。"
+      "title": "日常助理",
+      "description": "处理提问、写作和你随手交给它的小事。"
     },
     "research": {
       "name": "探路者",
-      "title": "研究员",
-      "description": "搜索网络和你的文件，带回一份附有来源的简报。"
+      "title": "调研助理",
+      "description": "检索网络和你的文件，给出一份带来源的简要结论。"
     }
   }
 }

package/shared/playbooks.ts

@@ -1,8 +1,11 @@
 import type { Playbook } from "./bot";
 
-// OpenMausBot's playbooks: process guidance with trigger words. A chat gets a
-// playbook only when one of its triggers appears in the job (the chat's first
-// message), so unrelated guidance stays out of the prompt.
+// Playbooks: process guidance with trigger words. A chat gets a playbook only when one of its triggers appears in the job (the
+// chat's first message), so unrelated guidance stays out of the prompt.
+//
+// Adapted from OpenMausBot's server/installed-playbooks.ts (Apache License 2.0, Copyright 2026 Milind Soni and OpenMausBot
+// contributors; see NOTICE and licenses/Apache-2.0.txt). Changed here: renamed and reorganised, a different matching
+// framing text and language handling.
 
 const MAX_SELECTED = 3;
 const MAX_CHARS = 24_000;

package/shared/rpc.ts

@@ -351,7 +351,7 @@ export const commandRemoveRpc = defineRpc({
   output: z.object({ ok: z.boolean() }),
 });
 
-// ---------------------------------------------------------------- approvals (docs/superpowers/specs/2026-10-21-approvals-design.md)
+// ---------------------------------------------------------------- approvals (docs/specs/2026-10-21-approvals-design.md)
 
 const ApprovalId = z.string().regex(/^a-[a-f0-9]{10}$/);
 const AuditEventSchema = z.object({

package/shared/skills.ts

@@ -3,7 +3,7 @@ import { englishTranslate, type Translate } from "./translate";
 /** An absolute path on this computer: `/…`, `~`, a Windows drive (`C:\…`) or a UNC path (`\\server\…`). */
 const LOCAL_FOLDER = /^(\/|~([\\/]|$)|[A-Za-z]:[\\/]|\\\\)/;
 
-/** Whether a skill's source is a folder on this computer, which an update can read again offline. */
+/** Whether a skill's source is a folder on this computer, which an update can read again without a network. */
 export function isLocalFolder(source: string): boolean {
   return LOCAL_FOLDER.test(source.trim());
 }
@@ -61,8 +61,10 @@ export function expandLearn(text: string): string | null {
 }
 
 /**
- * Things worth a second look before a skill reaches a bot, as OpenMausBot's
- * scanSkillText flags them. They warn; the user decides.
+ * Things worth a second look before a skill reaches a bot. They warn; the user decides.
+ *
+ * Adapted from OpenMausBot's scanSkillText (shared/skill-md.ts; Apache License 2.0, Copyright 2026 Milind Soni and OpenMausBot
+ * contributors; see NOTICE and licenses/Apache-2.0.txt). Changed here: different thresholds and wording, two more checks.
  */
 export function scanSkillText(text: string, t: Translate = englishTranslate): string[] {
   const warnings: string[] = [];

package/shared/templates.ts

@@ -4,8 +4,8 @@ import { withToolModeFor } from "./tools-mode";
 import { englishTranslate, type Translate } from "./translate";
 import { newBotId, type Bot, type Preset } from "./bot";
 
-// Starting points for a new bot, from OpenMausBot's New bot roles
-// (src/lib/bot-roles.ts): a name, a job and standing instructions.
+// Starting points for a new bot: a name, a job and standing instructions. The idea of ready-made roles follows OpenMausBot's
+// (src/lib/ready-bots.ts); the texts here were rewritten for Aydo (see NOTICE).
 
 export interface BotTemplate {
   id: string;
@@ -26,24 +26,24 @@ export const BOT_TEMPLATES: readonly BotTemplate[] = [
   {
     id: "assistant",
     name: "Assistant",
-    title: "General assistant",
-    description: "Answers questions, drafts text, and takes on whatever you hand it.",
+    title: "Everyday helper",
+    description: "Handles questions, writing and small jobs you pass along.",
     nameKey: "templates.assistant.name",
     titleKey: "templates.assistant.title",
     descriptionKey: "templates.assistant.description",
     avatarSeed: "assistant-7",
-    soul: "You are a capable, plain-spoken assistant. Ask one clarifying question when a request is ambiguous; otherwise do the work and show the result. Keep replies short and concrete.",
+    soul: "You are a practical assistant who speaks plainly. If a request could mean two different things, check with the user first; if it is clear, just do it and report what you did. Be brief and specific.",
   },
   {
     id: "research",
     name: "Scout",
-    title: "Researcher",
-    description: "Digs through the web and your files, and comes back with a sourced brief.",
+    title: "Research assistant",
+    description: "Searches the web and your files and returns a short, sourced summary.",
     nameKey: "templates.research.name",
     titleKey: "templates.research.title",
     descriptionKey: "templates.research.description",
     avatarSeed: "research-5",
-    soul: "You research questions and return a brief: the answer first, then the evidence with links, then what you could not verify. Prefer primary sources. Say clearly when sources disagree. Never present a guess as a finding.",
+    soul: "You investigate questions and write up what you find. Lead with the conclusion, then the supporting evidence with links, then anything still uncertain. Favor original sources, point out where they conflict, and never state a guess as a fact.",
   },
 ];
 

package/shared/version.ts

@@ -1,5 +1,5 @@
 /** The plugin's version, shown on the splash. Kept in step with package.json by a test. */
-export const PLUGIN_VERSION = "0.3.0";
+export const PLUGIN_VERSION = "0.4.1";
 
 /** The plugin's id (paseo-plugin.json); timeline items it appends carry it as their pluginId. */
 export const PLUGIN_ID = "aydo";