@orlan-maker/cli 0.1.0 → 0.2.0

package/dist/http.js

@@ -25,13 +25,13 @@ const explained = {
     org_suspended: "This organisation is suspended.",
     topic_missing: "The agent has several topics and used none yet. Add --topic <topic id>: `orlan topics list` shows them.",
     file_too_large: "The file is larger than Orlan takes.",
-    plan_limit_agents: "The organisation uses all the agents of the Free plan. Disconnect an agent with `orlan mcp disconnect`, or ask an admin to move the organisation to Team (organisation menu, Billing).",
-    guest_account_agent_limit: "A guest account connects one agent. Disconnect it with `orlan mcp disconnect`, or add your email in Orlan (the bar at the top) to connect more.",
+    plan_limit_agents: "The organisation uses all the agents of the Free plan. Disconnect an agent with `orlan disconnect`, or ask an admin to move the organisation to Team (organisation menu, Billing).",
+    guest_account_agent_limit: "A guest account connects one agent. Disconnect it with `orlan disconnect`, or add your email in Orlan (the bar at the top) to connect more.",
     guest_account_file_limit: "A guest account holds 3 files, 25 MB in total. Add your email in Orlan (the bar at the top) to upload more.",
 };
 /** What to do after a named API error (F038): every error ends with a next_step line. */
 const nextSteps = {
-    not_signed_in: "orlan auth login, then orlan mcp connect --agent <id>",
+    not_signed_in: "orlan auth login, then orlan connect --agent <id>",
     forbidden: "ask an admin of the organisation, or tell your person what you wanted to do",
     not_found: "orlan brief (the topics, files and requests your token can reach)",
     ref_ambiguous: "give the id from the list above, or add --topic <topic>",
@@ -56,8 +56,11 @@ const nextSteps = {
     upload_invalid: "run the command again: it sends the file again",
     upload_expired: "run the command again: it sends the file again",
     mention_invalid: "write the comment without that mention",
-    plan_limit_agents: "orlan mcp disconnect --agent <id>, or ask an admin to move the organisation to Team",
-    guest_account_agent_limit: "orlan mcp disconnect --agent <id>, or add your email in Orlan",
+    compare_not_ready: "run the command again in a few seconds",
+    task_invalid: "check the text, the topic, --thread and --assignee: `orlan tasks add --help`",
+    decision_invalid: "check the title, the topic and --thread: `orlan decisions add --help`",
+    plan_limit_agents: "orlan disconnect --agent <id>, or ask an admin to move the organisation to Team",
+    guest_account_agent_limit: "orlan disconnect --agent <id>, or add your email in Orlan",
     guest_account_file_limit: "add your email in Orlan (the bar at the top)",
     internal_error: "run the command again; when it fails again, tell your person",
 };
@@ -90,10 +93,21 @@ export function apiError(status, code) {
     return new OrlanError((code && explained[code]) ?? `Orlan answered ${status}${code ? ` (${code})` : ""}.`, code);
 }
 /** The error of an agent token that Orlan did not accept: revoked or replaced. */
-export const agentTokenRefused = () => new OrlanError("Orlan did not accept the agent token. It was revoked or replaced.", "not_signed_in", "orlan mcp connect --agent <id>");
+export const agentTokenRefused = () => new OrlanError("Orlan did not accept the agent token. It was revoked or replaced.", "not_signed_in", "orlan connect --agent <id>");
+/**
+ * The id of the harness session the CLI runs in (F085), as the harness's hooks report it: ORLAN_SESSION
+ * (the Orlan OpenCode plugin sets it), else the id that Claude Code, Codex or OpenCode puts in the
+ * shell. Cursor puts none there: Orlan then takes the newest open hook session of the token.
+ */
+export function harnessSession(env = process.env) {
+    return [env.ORLAN_SESSION, env.CLAUDE_CODE_SESSION_ID, env.CODEX_THREAD_ID, env.OPENCODE_SESSION_ID]
+        .map((value) => value?.trim())
+        .find((value) => value)
+        ?.slice(0, 200);
+}
 /**
  * The stateless calls of the daily commands (F038): each is one plain HTTP request with the agent
- * token. No MCP session: no initialize, no DELETE, no session row. Orlan writes each call in the
+ * token. No session to open or close, and no session row. Orlan writes each call in the
  * audit log like any agent call. Human ids (#12, v5, a file or topic name) work as input.
  */
 export class AgentApi {
@@ -127,9 +141,17 @@ export class AgentApi {
         }
         return json;
     }
-    /** Calls an agent tool with its input and returns its JSON answer. A refusal throws with its code. */
+    /**
+     * Calls an agent tool with its input and returns its JSON answer. A refusal throws with its code. The
+     * call names the harness session it runs in, so the board shows it on that agent (F085).
+     */
     call(tool, input = {}) {
-        return this.send(new URL(`/api/agent/tools/${encodeURIComponent(tool)}`, this.server), { method: "POST", headers: { "content-type": "application/json" }, body: JSON.stringify(input) }, tool);
+        const session = harnessSession();
+        return this.send(new URL(`/api/agent/tools/${encodeURIComponent(tool)}`, this.server), {
+            method: "POST",
+            headers: { "content-type": "application/json", ...(session ? { "x-orlan-session": session } : {}) },
+            body: JSON.stringify(input),
+        }, tool);
     }
     /** GET an agent route, with its query. */
     get(pathname, query, what) {

package/dist/main.js

@@ -8,17 +8,16 @@ import { fileURLToPath } from "node:url";
 import { parseArgs } from "node:util";
 import { commands } from "./commands.js";
 import { OrlanError } from "./http.js";
-const { version } = JSON.parse(readFileSync(new URL("../package.json", import.meta.url), "utf8"));
+const { name, version } = JSON.parse(readFileSync(new URL("../package.json", import.meta.url), "utf8"));
 function overview() {
     const width = Math.max(...Object.keys(commands).map((name) => name.length));
     return [
         "orlan - connect an agent to Orlan, and work with its topics, files and comments.",
         "",
         "Set up:",
-        "  npm i -g @orlan-maker/cli",
+        `  npm i -g ${name}`,
         "  orlan auth login",
-        "  orlan skills add --agent <id>",
-        "  orlan mcp connect --agent <id>",
+        "  orlan connect --agent <id>",
         "",
         "Commands:",
         ...Object.entries(commands).map(([name, command]) => `  ${name.padEnd(width)}  ${command.summary}`),

package/dist/skills.js

@@ -5,7 +5,7 @@
 import { mkdir, readFile, writeFile } from "node:fs/promises";
 import path from "node:path";
 import { skillsDir } from "./agents.js";
-export const skillNames = ["orlan-review", "orlan-versions"];
+export const skillNames = ["orlan", "orlan-review", "orlan-versions"];
 /** Writes every Orlan skill for the agent. Returns the folders it wrote. */
 export async function writeSkills(agent, cwd = process.cwd()) {
     const root = skillsDir(agent, cwd);

package/hooks/orlan-intro.txt

@@ -0,0 +1 @@
+This session is connected to Orlan, the shared board of the team. "The canvas", "the board" and "the topic" mean the Orlan topic that orlan brief names. When the person asks for a diagram, a page, a deck, a mock or another file for people to see, or names the canvas or the board, load the orlan skill first and do what it says.

package/hooks/session-start

@@ -5,7 +5,10 @@
 orlan="$CLAUDE_PLUGIN_ROOT/bin/orlan"
 "$orlan" hook working --agent claude-code
 if "$orlan" brief --agent claude-code 2>&1; then
-  echo "The Orlan plugin's monitor runs orlan wait --follow for this session: each request comes as a notification. Do not run orlan wait yourself."
+  # This line tells the session what Orlan is and when to load the orlan skill (D088, F086). Codex,
+  # Cursor and OpenCode read the same file (F090).
+  cat "$CLAUDE_PLUGIN_ROOT/hooks/orlan-intro.txt"
+  echo "orlan inbox lists the open requests. orlan wait waits for the next request and blocks the turn: run it only when the person asks for that."
   echo "Answer a request with the orlan command in few steps: orlan files pull <file id> --out <path> && cat <path>; edit the file; orlan respond <request id> --file <path> [--to <file id>] --message \"<what changed>\"."
 fi
 exit 0

package/opencode/orlan.js

@@ -1,5 +1,5 @@
-// The Orlan plugin for OpenCode (F045). `orlan mcp connect --agent opencode` writes it to OpenCode's
-// plugins folder, and `orlan mcp disconnect --agent opencode` takes it out.
+// The Orlan plugin for OpenCode (F045). `orlan connect --agent opencode` writes it to OpenCode's
+// plugins folder, and `orlan disconnect --agent opencode` takes it out.
 //
 // OpenCode has no stop hook and no monitor: a turn that ends raises `session.idle`, and a plugin may
 // answer it with a new prompt. So when a session goes idle, this plugin runs `orlan hook wait`. When a
@@ -7,12 +7,16 @@
 // session with prompt_async: a new turn starts. When the session works again before a request
 // comes, the plugin ends the wait, and an untaken request stays in the inbox.
 // The board shows the session's state from OpenCode's events through `orlan hook <state>`.
+// OpenCode has no session start hook that adds context: the plugin adds the Orlan intro line (what
+// Orlan is, F090) to the system prompt of each session's model call, with experimental.chat.system.transform.
 import { spawn } from "node:child_process";
 
-// The orlan command. `orlan mcp connect` writes this Node and this CLI by full path here, because
+// The orlan command. `orlan connect` writes this Node and this CLI by full path here, because
 // OpenCode started from the desktop often has no `orlan` on its PATH.
 const ORLAN = ["orlan"];
 const AGENT = ["--agent", "opencode"];
+// The Orlan intro line, hooks/orlan-intro.txt of the orlan package. `orlan connect` writes it here.
+const INTRO = "";
 
 /** Runs `orlan <args>` with the JSON the hook reads on standard input. */
 function orlan(args, input) {
@@ -74,6 +78,14 @@ export const OrlanPlugin = async ({ client }) => {
   };
 
   return {
+    // What Orlan is, in the system prompt of a session (a title or other call with no session gets nothing).
+    "experimental.chat.system.transform": async (input, output) => {
+      if (input.sessionID && INTRO) output.system.push(INTRO);
+    },
+    // The orlan commands of the agent's shell name its session (F085): the parent of a subagent's session.
+    "shell.env": async (input, output) => {
+      if (input.sessionID) output.env.ORLAN_SESSION = root(input.sessionID);
+    },
     event: async ({ event }) => {
       const properties = event.properties ?? {};
       switch (event.type) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@orlan-maker/cli",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "description": "The orlan command: connect Claude Code, Codex, Cursor or OpenCode to Orlan, and work with its topics, files and comments from the terminal.",
   "license": "MIT",
   "type": "module",
@@ -12,10 +12,8 @@
     "skills",
     "bin",
     "hooks",
-    "monitors",
     "opencode",
     ".claude-plugin",
-    ".mcp.json",
     "README.md",
     "LICENSE"
   ],
@@ -28,19 +26,12 @@
   },
   "homepage": "https://orlan.app",
   "publishConfig": {
-    "access": "public",
-    "provenance": true
-  },
-  "devDependencies": {
-    "@orlan/api": "0.1.0",
-    "@orlan/db": "0.1.0",
-    "@orlan/files": "0.1.0",
-    "@orlan/shared": "0.1.0",
-    "@orlan/sync": "0.1.0",
-    "@orlan/worker": "0.1.0"
+    "access": "public"
   },
   "scripts": {
     "build": "node scripts/build.mjs",
+    "release": "node --env-file-if-exists=../../.env scripts/publish.mjs",
+    "prepack": "node scripts/build.mjs",
     "typecheck": "tsc -p ."
   }
-}
+}

package/skills/orlan/SKILL.md

@@ -0,0 +1,88 @@
+---
+name: orlan
+description: Orlan is the shared board of a team and its AI agents. Each Orlan topic has one board (people call it the canvas) with files (HTML, PDF, PowerPoint, images), notes, comments, tasks and votes. Use when Orlan is connected and the person says the canvas, the board, the topic, "in Orlan" or "on Orlan", asks what is on the board, or asks for a diagram, page, deck, mock or other file for people to see or review. Also use for a comment, a version or a request on Orlan. Do not use for work that has no link to the board, such as a sum, a question on code, or a fix in a local file that the person names.
+---
+
+# Orlan
+
+Orlan is one board for a team and its AI agents. A person opens a topic. The topic's board holds
+files (HTML, PDF, PowerPoint, images) as page tiles, and notes, text, frames and arrows. People
+comment on regions of pages, vote and set tasks. You work on the same board: you read it, post
+files and versions, reply to comments and resolve them.
+
+## The words people use
+
+When Orlan is connected, these words mean the Orlan topic. Do not ask which one the person means.
+
+- "the canvas", "the board", "the topic", "the whiteboard" - the board of your Orlan topic.
+- "in Orlan", "on Orlan", "on the board", "put it up", "share it" - do it on the topic.
+- "the file", "the deck", "the page", "the doc" with no path - a file on the topic, when one has that
+  name or type. A path such as `./notes.txt` is a local file.
+- "the comments", "the feedback", "the review" - the open threads on the topic.
+
+`orlan brief` names your topic. With one topic, it is the one. With more, it is the one you used last,
+or the one the person names.
+
+## When to use Orlan
+
+- The person asks what is on the canvas or the board: run `orlan board` (every item with its id and
+  place, the timer, the vote and the open tasks), read the files you need
+  (`orlan files pull <file> --out <path>`), and answer from them.
+- The person asks for a diagram: a diagram on Orlan is board shapes with words and labeled arrows. Do
+  not post an HTML file or notes as a diagram, and do not draw it with notes, texts and arrows. This
+  version of the orlan command cannot draw shapes yet: tell the person so, and ask what they want
+  instead.
+- The person asks for a note, a text, a frame or an arrow on the board: `orlan board add`. Change one
+  with `orlan board change <item>`, delete one with `orlan board delete <item>`.
+- The person asks you to make something else that people look at: a page, a mock, a deck, a report, a
+  chart. Make the file, check it, then post it to the topic:
+  `orlan files add <path>`. When a local rule says to keep visuals as local files, keep the local file
+  and post it too. Tell the person that it is on the board, and give its name and version.
+- The person asks you to change a file that is on the topic: pull it with `--edit`, change it, and post
+  a new version: `orlan files push <file> <path> --changelog "<what changed>"`.
+- A comment or a request names you: follow the `orlan-review` skill.
+
+## When not to use Orlan
+
+Do not call Orlan for work that has no link to the board: a sum, a general question, a question on
+code, a fix in a local file the person names, a test run. Do the work and answer. Do not post a file
+the person did not ask for.
+
+## The loop
+
+1. Brief: `orlan brief` - the topic, its files and versions, your open requests, the next step.
+2. Pull: `orlan files pull <file> --edit --out <path>` for a file you change.
+3. Work: make or change the file, and check it.
+4. Post: `orlan files add <path>` for a new file, or `orlan files push <file> <path> --changelog "..."`
+   for a new version. A version waits for a person to make it current.
+5. Reply: say what you did in the thread (`orlan comment <thread> "<text>"`), or answer a request with
+   `orlan respond`. Say in your answer what is now on the board.
+
+## More commands
+
+- `orlan board` - the board: each item with its id, type, place and text, the timer, the votes and
+  the open tasks.
+- `orlan board add note|text|frame "<text>" --at <x,y>`, `orlan board add arrow --from <item> --to <item>`,
+  `orlan board change <item>`, `orlan board delete <item>` - change the board. A person can undo each
+  change. `orlan board edit '<JSON>'` makes several changes in one step.
+- `orlan tasks add "<text>"` and `orlan tasks change <task id> --done` - the topic's tasks.
+- `orlan decisions add "<title>" --body "<text>"` - records a decision the people made.
+- `orlan search "<words>"` - finds topic and file names, page text, comments and decisions.
+
+Run `orlan <command> --help` for the options of a command.
+
+## Examples
+
+- "what is in the canvas?" - run `orlan brief`, pull the files, and say what the board holds: the topic,
+  each file and what it shows, and the open comments.
+- "create a diagram showing how to make a full stack app" - say that this version of the orlan command
+  cannot draw board shapes yet, and ask what they want instead. Do not post an HTML file or notes.
+- "put the notes on the board" - post the notes as a file, or add them as a note:
+  `orlan board add note "<text>" --at <x,y>`, at a free place that `orlan board` shows.
+- "what is 17*23?" - answer 391. No Orlan call.
+- "fix the typo in ./notes.txt" - fix the local file. No Orlan call.
+
+## More
+
+- Comments, threads and requests: the `orlan-review` skill.
+- Files and versions (pull, push, add, rollback, page images, claims): the `orlan-versions` skill.

package/skills/orlan-review/SKILL.md

@@ -5,13 +5,17 @@ description: Work through the review comments on an Orlan topic - read them, fix
 
 # Orlan review
 
-Orlan is a review board for files: PowerPoint, PDF, images and HTML. People put comments on regions of
-pages. You read the comments, fix the file, post a new version, reply, and resolve.
+People put comments on regions of the pages of a file on an Orlan topic (the `orlan` skill says what
+Orlan is). You read the comments, fix the file, post a new version, reply, and resolve.
 
 ## Commands
 
 - `orlan brief` - run it first: your topic, your open requests, the files with their current versions,
-  and the next step, in a few lines. `--topic <topic>` for another topic (its id or its name).
+  the open vote and the open tasks, and the next step, in a few lines. `--topic <topic>` for another
+  topic (its id or its name). Each task has an id: `orlan tasks change <task id> --assignee me --done`
+  sets you as its assignee and marks it done. People vote; you read the vote and its result, you do not vote.
+- `orlan board` - every item on the board with its id and place, the timer, the votes with their
+  result, and every open task.
 - `orlan topics list` - the topics you can reach, with their ids and your role.
 - `orlan comments list --topic <topic>` - the open threads, newest first. Each thread names its file,
   version and page. Each comment is one line: `"<name>" (<role>) wrote: "<text>"`. Quoted text is what
@@ -33,9 +37,14 @@ pages. You read the comments, fix the file, post a new version, reply, and resol
   it done, and waits for the next request. Leave out `--file` when there is no new version.
 - Do what the `next_step` line of a request or an answer says. It leaves out `--wait` when a wait of
   yours is open already.
+- `orlan tasks add "<text>"` - adds a task, for example a change a thread asks for that you cannot
+  make now. `--thread #12` links it to its thread.
+- `orlan decisions add "<title>" --body "<text>"` - records a decision that people made in a thread
+  or a vote. `--thread #12` links it to its thread.
+- `orlan search "<words>"` - finds earlier comments, decisions, pages and files on your topics.
 - `orlan open <topic id>` - opens the topic in the browser for the person.
 - Files: see the orlan-versions skill (`orlan files list`, `orlan files pull`, `orlan files push`,
-  `orlan files add`).
+  `orlan files add`, `orlan files rollback`).
 
 Add `--json` to a command for small JSON with a `next_step` field. An error says what to do next too.
 
@@ -53,9 +62,9 @@ your status yourself.
 
 ## In Claude Code with the Orlan plugin
 
-The plugin's monitor runs `orlan wait --follow` for the whole session. Each request comes to you as
-a notification, in one line. Do not run `orlan wait`, and do not add `--wait`: the monitor gets the next
-request. For each request: pull the file, make the change, check it, and run `orlan respond`.
+`orlan inbox` lists the open requests. `orlan wait` waits for the next request and blocks your turn:
+run it, or add `--wait`, only when the person asks you to wait for requests. For each request: pull the
+file, make the change, check it, and run `orlan respond`.
 
 ## In Codex and Cursor with the Orlan hooks
 

package/skills/orlan-versions/SKILL.md

@@ -7,17 +7,24 @@ description: Get a file from Orlan and post a new version of it with a changelog
 
 ## Commands
 
-- `orlan files list --topic <topic>` - the files of a topic: id, name, type, and the current version.
+- `orlan files list [--topic <topic>]` - the files of a topic: id, name, type, and the current version,
+  with the pages that changed from the version before.
 - `orlan files pull <file>` - downloads the current version to the folder you are in, with its own
   name. `--version 5` (or `v5`) gets an older version, `--out <path>` names the file. Add `--edit` when
   you pull it to change it: other agents and people then see your claim on the file for 15 minutes
   (`--ttl` changes it). When another agent has a claim, the answer says who and what to do next.
+- `orlan files pull <file> --pages 2,5` - saves the image of each page (`<name>-page-<n>.png`, in the
+  folder `--out` names) and prints its text, not the file. `--since 4` gets the pages that changed
+  since v4. Look at the images to see a page as people see it.
 - `orlan files push <file> <path> --changelog "<what changed>"` - posts the file as a new version.
   It must be the same type of file. The CLI sends it in one request, so a large file works too.
   It ends your claim. When a version landed after the one you pulled, Orlan refuses it with
   `stale_base` and that version's changelog: pull the newest version, make your change on it, push again.
 - `orlan files add <path>` - posts a local file as a new file on your topic and puts it on the board.
-  `--topic <topic>` names the topic; the default is the topic you used last.
+  `--topic <topic>` names the topic; the default is the topic you used last. `--at <x,y>` puts it at
+  that point of the board (`orlan board` shows where the items are).
+- `orlan files rollback <file> --version 3 --changelog "<why>"` - posts an older version again, as the
+  newest version. It waits for a person to make it current, as a push does.
 - `<file>` is the file id or the file name, and `<topic>` the topic id or its name. When a name is on two
   topics, the error lists both: give the id, or add `--topic`.
 

package/.mcp.json

@@ -1,9 +0,0 @@
-{
-  "mcpServers": {
-    "orlan": {
-      "type": "http",
-      "url": "${ORLAN_SERVER:-https://orlan.app}/mcp",
-      "headersHelper": "\"${CLAUDE_PLUGIN_ROOT}/bin/orlan\" mcp headers --agent claude-code"
-    }
-  }
-}

package/dist/mcp.js

@@ -1,113 +0,0 @@
-/**
- * A small MCP client over Streamable HTTP, for the MCP test of `orlan status` and `orlan mcp connect`:
- * it proves that the agent's MCP server works. The daily commands use plain HTTP (AgentApi, F038). A
- * test is one MCP session of the agent token: it starts the session, calls its tool, and closes it. The
- * client names itself "orlan-cli", so Orlan keeps these sessions off the Agents tab and sends no
- * "session ended" notification for them. Every call is in the audit log like any agent call.
- */
-import { OrlanError } from "./http.js";
-const PROTOCOL_VERSION = "2025-06-18";
-/** The JSON-RPC answer with this id, from a JSON body or from a server-sent event stream. */
-async function answerOf(response, id) {
-    const text = await response.text();
-    const type = response.headers.get("content-type") ?? "";
-    const messages = type.includes("text/event-stream")
-        ? text
-            .split(/\r?\n\r?\n/)
-            .map((event) => event
-            .split(/\r?\n/)
-            .filter((line) => line.startsWith("data:"))
-            .map((line) => line.slice(5).trimStart())
-            .join("\n"))
-            .filter((data) => data.length > 0)
-            .map((data) => JSON.parse(data))
-        : [JSON.parse(text)];
-    const answer = messages.find((message) => message.id === id);
-    if (!answer)
-        throw new OrlanError("Orlan's MCP server gave no answer.");
-    if (answer.error)
-        throw new OrlanError(`Orlan's MCP server refused the call: ${answer.error.message}`);
-    return answer;
-}
-export class McpClient {
-    sessionId;
-    nextId = 1;
-    url;
-    /** The agent token: the file downloads send it as their Bearer header too. */
-    token;
-    version;
-    constructor(server, token, version) {
-        this.url = new URL("/mcp", server);
-        this.token = token;
-        this.version = version;
-    }
-    async post(body) {
-        let response;
-        try {
-            response = await fetch(this.url, {
-                method: "POST",
-                headers: {
-                    authorization: `Bearer ${this.token}`,
-                    "content-type": "application/json",
-                    accept: "application/json, text/event-stream",
-                    ...(this.sessionId ? { "mcp-session-id": this.sessionId, "mcp-protocol-version": PROTOCOL_VERSION } : {}),
-                },
-                body: JSON.stringify(body),
-            });
-        }
-        catch (error) {
-            throw new OrlanError(`Orlan's MCP server at ${this.url} did not answer: ${error.message}.`);
-        }
-        if (response.status === 401) {
-            throw new OrlanError("Orlan did not accept the agent token. It was revoked or replaced: run `orlan mcp connect` again.", "not_signed_in");
-        }
-        if (!response.ok && response.status !== 202) {
-            throw new OrlanError(`Orlan's MCP server answered ${response.status}.`);
-        }
-        return response;
-    }
-    async request(method, params) {
-        const id = this.nextId++;
-        const response = await this.post({ jsonrpc: "2.0", id, method, params });
-        if (method === "initialize")
-            this.sessionId = response.headers.get("mcp-session-id") ?? undefined;
-        return (await answerOf(response, id)).result;
-    }
-    async open() {
-        await this.request("initialize", {
-            protocolVersion: PROTOCOL_VERSION,
-            capabilities: {},
-            clientInfo: { name: "orlan-cli", version: this.version },
-        });
-        if (!this.sessionId)
-            throw new OrlanError("Orlan's MCP server started no session.");
-        await (await this.post({ jsonrpc: "2.0", method: "notifications/initialized" })).text();
-    }
-    /** Calls a tool and returns its JSON answer. A refusal ("Refused: <code>") throws with that code. */
-    async call(tool, args = {}) {
-        if (!this.sessionId)
-            await this.open();
-        const result = (await this.request("tools/call", { name: tool, arguments: args }));
-        const text = result.content?.find((part) => part.type === "text")?.text ?? "";
-        if (result.isError) {
-            const code = /^Refused: ([a-z_]+)/.exec(text)?.[1];
-            throw new OrlanError(`Orlan refused ${tool}: ${text.replace(/^Refused: /, "")}`, code);
-        }
-        return JSON.parse(text);
-    }
-    /** Ends the session (HTTP DELETE). */
-    async close() {
-        if (!this.sessionId)
-            return;
-        const sessionId = this.sessionId;
-        this.sessionId = undefined;
-        await fetch(this.url, {
-            method: "DELETE",
-            headers: {
-                authorization: `Bearer ${this.token}`,
-                "mcp-session-id": sessionId,
-                "mcp-protocol-version": PROTOCOL_VERSION,
-            },
-        }).catch(() => undefined);
-    }
-}

package/monitors/monitors.json

@@ -1,7 +0,0 @@
-[
-  {
-    "name": "orlan-requests",
-    "command": "\"${CLAUDE_PLUGIN_ROOT}/bin/orlan\" wait --follow --agent claude-code",
-    "description": "Orlan requests: a mention of this agent on the board"
-  }
-]