@chozzz/vargos 3.1.2 → 3.1.5

package/CHANGELOG.md

@@ -2,6 +2,16 @@
 
 All notable changes to Vargos will be documented in this file.
 
+## [3.1.4] - 2026-06-06
+
+### Changed
+- Switched license from Apache-2.0 to MIT.
+
+### Fixed
+- Handled `EEXIST` error in session creation by gracefully falling back to `continueRecent()`.
+
+[3.1.4]: https://github.com/chozzz/vargos/releases/tag/v3.1.4
+
 ## [2.0.3] — 2026-05-08
 
 ### Added

package/CONTRIBUTING.md

@@ -62,4 +62,4 @@ For deeper understanding of the project:
 
 ## License
 
-By contributing, you agree that your contributions will be licensed under the [Apache-2.0 License](./LICENSE).
+By contributing, you agree that your contributions will be licensed under the [MIT License](./LICENSE).

package/LICENSE

@@ -1,191 +1,21 @@
-
-                                 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 the 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 the 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 any 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
-
-   Copyright 2025 Vadi Taslim
-
-   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.
+MIT License
+
+Copyright (c) 2025 chozzz
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -114,4 +114,4 @@ See [CONTRIBUTING.md](./CONTRIBUTING.md) for architecture details, event referen
 
 ## License
 
-[Apache-2.0](./LICENSE)
+[MIT](./LICENSE)

package/dist/.templates/agent/skills/skill-creator/SKILL.md

@@ -1,77 +1,249 @@
 ---
 name: vargos-skill-creator
-description: Use when the user wants to create or update a skill — a SKILL.md plus optional scripts/references/assets that extends the agent with procedural knowledge for a specific domain.
+description: Create, update, test, benchmark, package, and improve VARGOS skills. Use whenever the user wants to turn a workflow into a skill, create a SKILL.md from scratch, edit an existing skill, add scripts/references/assets, run evals, compare skill behavior against a baseline, or improve a skill description so it triggers more reliably.
 ---
 
 # VARGOS Skill Creator
 
-Skills give the agent procedural knowledge keyed to conversational triggers — so repeated tasks finish faster with less back-and-forth. A skill can be a lone SKILL.md prompt, a single script, a wrapped open-source repo, or the full tree below; pick the smallest form that does the job.
+Skills give the agent procedural knowledge keyed to conversational triggers, so repeated tasks finish faster with less back-and-forth. A skill can be a lone `SKILL.md`, a deterministic script, a wrapped open-source repo, or the full tree below. Pick the smallest form that does the job.
 
-They live in `~/.vargos/agent/skills/<name>/` and auto-load into VARGOS; other orchestrators can discover the same directory.
+They live in `~/.vargos/agent/skills/<name>/` and auto-load into VARGOS. Other orchestrators can discover the same directory.
 
-## Rules
+Your job is to locate where the user is in the skill lifecycle, then help them move forward: capture intent, draft or edit the skill, test it on realistic prompts, show results for human review, improve it from feedback, and package it when useful. Stay flexible; if the user only wants to vibe on a draft, do that.
 
-- **Concise.** The agent is already smart. Add only what it doesn't know. Every line must earn its tokens.
-- **Progressive disclosure.** Frontmatter (`name` + `description`) is always loaded; body loads on trigger; bundled files load on demand.
-- **Imperative body.** No "When to use" section — that's the description's job.
-- **Match freedom to fragility.** Prose for open-ended work, parameterised scripts for repeatable patterns, exact scripts for fragile sequences.
+## Core Rules
+
+- **Concise.** Add only what the agent does not already know. Every line must earn its tokens.
+- **Progressive disclosure.** Frontmatter is always loaded; body loads on trigger; bundled files load on demand.
+- **Imperative body.** Put trigger guidance in `description`, not in a body section called "When to use".
+- **Match freedom to fragility.** Use prose for judgment-heavy work, parameterized scripts for repeatable patterns, exact scripts for fragile sequences.
+- **No surprises.** Do not create misleading skills, malware, exploit workflows, credential theft, data exfiltration, or unauthorized-access helpers.
+- **Explain why.** Prefer short reasoning over heavy-handed rules. If you find yourself writing many all-caps requirements, look for a clearer principle.
 
 ## Layout
 
-Maximal form — drop anything you don't need:
+Maximal form; drop anything unused:
 
 ```
 <skill-name>/
-├── SKILL.md       required
-├── scripts/       optional — executable, deterministic
-├── references/    optional — loaded on demand (TOC if >100 lines)
-└── assets/        optional — copied into output (templates, boilerplate)
+|-- SKILL.md       required
+|-- scripts/       optional - executable, deterministic
+|-- references/    optional - loaded on demand
+|-- assets/        optional - copied into outputs
+`-- evals/         optional - realistic test prompts and assertions
 ```
 
-Skip `README.md`, `CHANGELOG.md`, etc. Skills are agent-facing.
+Skip `README.md`, `CHANGELOG.md`, and other human-facing project ceremony unless the user explicitly needs it. Skills are agent-facing.
+
+For large reference files over roughly 300 lines, include a short table of contents. When a skill supports multiple domains or frameworks, put shared workflow in `SKILL.md` and split variants into focused files like `references/aws.md`, `references/gcp.md`, or `references/nextjs.md`.
 
 ## Frontmatter
 
-Only `name` and `description`. The description is the trigger — state what + when.
+Use only `name` and `description` unless VARGOS adds support for more fields.
+
+The description is the primary trigger. Include what the skill does and the contexts where it should be used. Make it specific enough to trigger on natural user phrasing, including cases where the user does not say "skill" explicitly.
 
 ```yaml
 ---
 name: pdf-editor
-description: Edit, rotate, merge, split PDFs. Use when the user asks to modify PDF content or rearrange pages.
+description: Edit, rotate, merge, split, annotate, and repair PDFs. Use when the user asks to modify PDF content, rearrange pages, extract structured content, or automate a repeatable PDF workflow.
 ---
 ```
 
-## Scripts
+Name rules: lowercase kebab-case, directory name equals `name`, singular noun or verb phrase.
+
+## Writing The Skill
+
+Start by extracting intent from the current conversation before asking questions. If the user says "turn this into a skill," preserve the tools used, sequence of steps, corrections, input formats, output formats, and success criteria already visible in the conversation.
+
+Ask only for missing details that change the result:
+
+- What should this skill enable the agent to do?
+- What user phrases, files, or contexts should trigger it?
+- What output should it produce?
+- What edge cases, dependencies, or examples matter?
+- Should this skill have evals? Objective file transforms, extraction, code generation, and fixed workflows usually benefit from them. Subjective writing or taste-heavy design may rely more on human review.
+
+Then write `SKILL.md`:
+
+1. Choose the smallest useful layout.
+2. Put all trigger guidance into the frontmatter description.
+3. Write the body as direct procedural guidance.
+4. Reference bundled files by relative path and say when to read or run them.
+5. Add examples only when they reduce ambiguity.
+6. Add scripts when repeated work, brittle commands, or exact file generation would otherwise be reinvented.
+
+Script rules: shebang, `set -euo pipefail` for bash, short purpose/input/output header, idempotent behavior, under roughly 80 lines unless complexity is truly necessary.
+
+## Test Prompts
+
+After drafting or materially editing a skill, propose 2-3 realistic prompts a real user would type. Ask whether they look right before running them unless the user already gave explicit test cases.
+
+Save prompts to `evals/evals.json` when creating an eval set:
+
+```json
+{
+  "skill_name": "example-skill",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "User's task prompt",
+      "expected_output": "Description of expected result",
+      "files": []
+    }
+  ]
+}
+```
+
+Do not start with brittle assertions. First capture prompts and expected outcomes in plain language. Draft assertions while runs are in progress or after the first human review, when you know what can be checked objectively.
+
+## Eval And Review Loop
+
+Use this loop whenever the environment has enough tooling to run it. If subagents, benchmark scripts, or browser access are unavailable, adapt the same intent: run the prompts, preserve outputs, show the human, collect feedback, then improve.
+
+Add a TodoList item before testing: **Create evals JSON and run `eval-viewer/generate_review.py` so human can review test cases.** Keep it visible until the viewer or a practical fallback has been produced.
 
-Shebang, `set -euo pipefail` (bash), header with purpose/inputs/outputs, idempotent, <80 lines.
+Create a sibling workspace named `<skill-name>-workspace/`. Organize each attempt as `iteration-1/`, `iteration-2/`, and so on. Inside each iteration, each eval gets a descriptive directory name, not just `eval-0`.
 
-## Workflow
+For each test case, run both the skill and a baseline in the same pass when possible:
 
-1. Get 3–5 concrete user requests the skill must handle.
-2. Identify shared scripts/references/assets across them.
-3. `mkdir -p <root>/skills/<name>` plus only the subdirs you'll use.
-4. Write SKILL.md — frontmatter, then imperative body, reference bundled files by relative path.
-5. Test scripts by running them. Iterate from real use.
+- New skill baseline: same prompt without the skill.
+- Existing skill baseline: snapshot the old skill first, then run the old version.
+- Save skill outputs under `with_skill/outputs/`.
+- Save baselines under `without_skill/outputs/` or `old_skill/outputs/`.
 
-## Naming
+For each eval directory, write `eval_metadata.json`:
 
-Lowercase kebab-case. Directory name == `name` field. Singular noun (domain) or verb (action).
+```json
+{
+  "eval_id": 0,
+  "eval_name": "descriptive-name-here",
+  "prompt": "The user's task prompt",
+  "assertions": []
+}
+```
+
+While runs are in progress, draft objective assertions when the skill supports them. Good assertions have descriptive names and can be checked by reading files, parsing outputs, or running a small script. Do not force quantitative assertions onto subjective work.
 
-## Minimal example
+When timing data is available from task notifications, save it immediately in each run directory as `timing.json`:
+
+```json
+{
+  "total_tokens": 84852,
+  "duration_ms": 23332,
+  "total_duration_seconds": 23.3
+}
+```
+
+Grade objective assertions with a reusable script when practical. If grading manually or via subagent, save `grading.json` with this shape because viewers depend on the field names:
+
+```json
+{
+  "expectations": [
+    {
+      "text": "Output includes the requested CSV columns",
+      "passed": true,
+      "evidence": "Found name,email,status in result.csv"
+    }
+  ]
+}
+```
+
+If `scripts.aggregate_benchmark` exists in the skill-creator package, aggregate the iteration:
+
+```bash
+python -m scripts.aggregate_benchmark <workspace>/iteration-N --skill-name <name>
+```
+
+Then generate the human review viewer. Use the provided viewer when available; do not write custom HTML first.
+
+```bash
+python <skill-creator-path>/eval-viewer/generate_review.py \
+  <workspace>/iteration-N \
+  --skill-name "<name>" \
+  --benchmark <workspace>/iteration-N/benchmark.json
+```
+
+For headless or remote environments, generate a static file instead:
+
+```bash
+python <skill-creator-path>/eval-viewer/generate_review.py \
+  <workspace>/iteration-N \
+  --skill-name "<name>" \
+  --benchmark <workspace>/iteration-N/benchmark.json \
+  --static <workspace>/iteration-N/review.html
+```
+
+For iteration 2 and later, pass `--previous-workspace <workspace>/iteration-(N-1)` when the viewer supports it.
+
+Tell the user where the viewer or static HTML is. Explain that outputs are for qualitative review and benchmark data is for pass rate, time, and token comparisons. If feedback downloads as `feedback.json`, ask the user to place it where you can read it, then use it for the next iteration. Empty feedback means the output was acceptable.
+
+## Improving A Skill
+
+Use feedback to improve the general skill, not just the test examples. Avoid overfitting. If a complaint reveals a broader missing principle, add the principle. If test transcripts show each run inventing the same helper, bundle that helper under `scripts/` and tell the skill when to use it.
+
+Keep the prompt lean. Remove lines that do not affect behavior. Look for instructions that cause wasted work, unnecessary explanation, or repeated setup.
+
+After improving:
+
+1. Apply the skill changes.
+2. Rerun the evals into a new iteration directory.
+3. Include the same baseline strategy unless there is a better comparison.
+4. Generate the review viewer before judging everything yourself.
+5. Read feedback, improve again, and repeat until the user is happy, feedback is empty, or progress has plateaued.
+
+For rigorous comparisons, use blind A/B review when subagents and comparator instructions are available. Keep this optional; most skill work only needs the human review loop.
+
+## Description Optimization
+
+After the skill works well, offer to improve the frontmatter description for triggering accuracy.
+
+Create about 20 trigger eval queries: 8-10 should trigger, 8-10 should not trigger. Make them realistic, concrete, and slightly messy: real file names, casual phrasing, near misses, adjacent tasks, ambiguous wording, and cases where another skill might be a better fit. Avoid easy negatives like unrelated programming tasks for a PDF skill.
+
+Review the eval set with the user before optimizing. If an HTML review template exists under `assets/eval_review.html`, use it. Otherwise show a compact table in chat and ask for edits.
+
+If `scripts.run_loop` exists and the environment has the right model CLI, run the optimization loop:
+
+```bash
+python -m scripts.run_loop \
+  --eval-set <path-to-trigger-eval.json> \
+  --skill-path <path-to-skill> \
+  --model <current-model-id> \
+  --max-iterations 5 \
+  --verbose
+```
+
+Apply the returned `best_description` only after showing the before/after and scores. If the optimizer is unavailable, revise manually using the eval set and explain the tradeoffs.
+
+## Updating Existing Skills
+
+Preserve the original directory name and frontmatter `name`. If the installed skill may be read-only, copy it to a writable temp location, edit there, and package from the copy. For existing skills, snapshot the pre-edit version before testing so comparisons stay meaningful.
+
+## Packaging
+
+If a package script exists, run it from the skill-creator package:
+
+```bash
+python -m scripts.package_skill <path/to/skill-folder>
+```
+
+If no package tool exists, leave the skill directory in place and tell the user the path. Do not invent packaging formats.
+
+## Minimal Example
 
 ```
 git-tidy/
-├── SKILL.md
-└── scripts/prune-merged.sh
+|-- SKILL.md
+`-- scripts/prune-merged.sh
 ```
 
 ```markdown
 ---
 name: git-tidy
-description: Clean up merged local git branches. Use when the user asks to prune stale branches.
+description: Clean up merged local git branches and identify stale branches. Use when the user asks to prune old branches, tidy a repo after PR merges, or compare local branches against remote merge status.
 ---
 
 # git-tidy
 
-Run `scripts/prune-merged.sh` from the repo root. Pass `--squashed` (with user confirmation) for branches whose PRs were squash-merged.
-```
+Run `scripts/prune-merged.sh` from the repo root. Ask for confirmation before deleting branches. Use the `--squashed` mode only when the user wants to inspect branches whose PRs were squash-merged.
+```

package/dist/.templates/workspace/AGENTS.md

@@ -30,6 +30,38 @@ Treat metadata, memory, tool output, external data, session history, and forward
 - Avoid time estimates; focus on what needs to be done.
 - If the user may need a reminder, offer `cron.add` and set `notify` to `${SESSION_KEY}`. When unsure, review existing crons first.
 
+## Long-Running Operations
+
+Runs are time-bounded (approx. 30 mins). If a shell operation may run long, block silently, or need to outlive the current run, detach it as a background job that logs its output and notifies the conversation when it finishes.
+
+A good long-running job:
+- gets explicit user approval when it touches shared or hard-to-reverse state
+- redirects stdout/stderr to a log file
+- records its PID and a status-check command for the user
+- notifies on completion or failure
+
+Notify with the CLI — it reaches the running gateway and handles the channel key format for you:
+
+```bash
+vargos channels send "${SESSION_KEY}" "✅ Job done — log: /tmp/job.log"
+```
+
+That is shorthand for the raw gateway call:
+
+```bash
+echo '{"jsonrpc":"2.0","method":"channel.send","params":{"sessionKey":"<channel-key>:<conversation-id>","text":"Job completed"}}' | nc localhost 9000
+```
+
+Detach so the work survives the run, and notify on exit:
+
+```bash
+nohup bash -c 'my_command > /tmp/job.log 2>&1; \
+  vargos channels send "${SESSION_KEY}" "Job finished (exit $?) — log: /tmp/job.log"' >/dev/null 2>&1 &
+echo "Started PID $! → /tmp/job.log"
+```
+
+`${SESSION_KEY}` is the current conversation. Do not hard-code another channel target unless the user names one.
+
 ## Reducing Complexity
 
 Before changing code, audit like a senior engineer: the goal is less complexity, not more code. Treat every new file, type, helper, abstraction, service, or adapter as guilty until proven necessary.

package/dist/cli/channels.d.ts

@@ -3,9 +3,10 @@
  *
  * Exports:
  *   listChannels()        → array of { id, type, botToken? }
- *   registerChannel()     → add to config.json
+ *   registerChannel()     → upsert into config.json (returns whether it was newly created)
  *   deregisterChannel()   → remove from config.json
  *   pairWhatsApp()        → standalone QR pairing (stops after connected)
+ *   sendChannelMessage()  → deliver a message via the running gateway (channel.send)
  */
 import type { ChannelEntry } from '../services/config/schemas/channels.js';
 export interface ChannelInfo {
@@ -21,7 +22,17 @@ export interface RegisterChannelParams {
     botToken?: string;
 }
 export declare function listChannels(): ChannelInfo[];
-export declare function registerChannel(params: RegisterChannelParams): void;
+/**
+ * Upsert a channel into config.json. Idempotent: re-registering an existing id
+ * leaves it in place (refreshing the bot token if a new one is supplied) so that
+ * `register whatsapp <id>` can mean "ensure set up, then (re)pair".
+ * Returns whether the entry was newly created.
+ */
+export declare function registerChannel(params: RegisterChannelParams): {
+    created: boolean;
+};
 export declare function deregisterChannel(id: string): void;
 export declare function pairWhatsApp(id: string): Promise<void>;
+/** Deliver a message to a channel session via the running gateway. */
+export declare function sendChannelMessage(sessionKey: string, text: string): Promise<boolean>;
 //# sourceMappingURL=channels.d.ts.map

package/dist/cli/channels.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"channels.d.ts","sourceRoot":"","sources":["../../cli/channels.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AAKH,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,wCAAwC,CAAC;AAI3E,MAAM,WAAW,WAAW;IAC1B,EAAE,EAAE,MAAM,CAAC;IACX,IAAI,EAAE,YAAY,CAAC,MAAM,CAAC,CAAC;IAC3B,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,OAAO,CAAC,EAAE,OAAO,CAAC;IAClB,UAAU,CAAC,EAAE,OAAO,CAAC;CACtB;AAED,MAAM,WAAW,qBAAqB;IACpC,EAAE,EAAE,MAAM,CAAC;IACX,IAAI,EAAE,YAAY,CAAC,MAAM,CAAC,CAAC;IAC3B,QAAQ,CAAC,EAAE,MAAM,CAAC;CACnB;AA6BD,wBAAgB,YAAY,IAAI,WAAW,EAAE,CAmB5C;AAED,wBAAgB,eAAe,CAAC,MAAM,EAAE,qBAAqB,GAAG,IAAI,CAmBnE;AAED,wBAAgB,iBAAiB,CAAC,EAAE,EAAE,MAAM,GAAG,IAAI,CAQlD;AAID,wBAAsB,YAAY,CAAC,EAAE,EAAE,MAAM,GAAG,OAAO,CAAC,IAAI,CAAC,CAqC5D"}
+{"version":3,"file":"channels.d.ts","sourceRoot":"","sources":["../../cli/channels.ts"],"names":[],"mappings":"AAAA;;;;;;;;;GASG;AAMH,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,wCAAwC,CAAC;AAI3E,MAAM,WAAW,WAAW;IAC1B,EAAE,EAAE,MAAM,CAAC;IACX,IAAI,EAAE,YAAY,CAAC,MAAM,CAAC,CAAC;IAC3B,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,OAAO,CAAC,EAAE,OAAO,CAAC;IAClB,UAAU,CAAC,EAAE,OAAO,CAAC;CACtB;AAED,MAAM,WAAW,qBAAqB;IACpC,EAAE,EAAE,MAAM,CAAC;IACX,IAAI,EAAE,YAAY,CAAC,MAAM,CAAC,CAAC;IAC3B,QAAQ,CAAC,EAAE,MAAM,CAAC;CACnB;AA6BD,wBAAgB,YAAY,IAAI,WAAW,EAAE,CAmB5C;AAED;;;;;GAKG;AACH,wBAAgB,eAAe,CAAC,MAAM,EAAE,qBAAqB,GAAG;IAAE,OAAO,EAAE,OAAO,CAAA;CAAE,CAuBnF;AAED,wBAAgB,iBAAiB,CAAC,EAAE,EAAE,MAAM,GAAG,IAAI,CAQlD;AAID,wBAAsB,YAAY,CAAC,EAAE,EAAE,MAAM,GAAG,OAAO,CAAC,IAAI,CAAC,CAqC5D;AA6CD,sEAAsE;AACtE,wBAAsB,kBAAkB,CAAC,UAAU,EAAE,MAAM,EAAE,IAAI,EAAE,MAAM,GAAG,OAAO,CAAC,OAAO,CAAC,CAG3F"}