monomind 2.7.11 → 2.7.13

package/packages/@monomind/cli/.claude/commands/monitoring/agent-metrics.md

@@ -1,65 +0,0 @@
----
-name: monitoring:agent-metrics
----
-
-# agent metrics
-
-Show agent performance metrics — tasks completed, success rate, and memory vectors by agent type.
-
-## Usage
-
-```bash
-npx monomind agent metrics [agentId] [options]
-```
-
-The optional `agentId` positional argument filters to a specific agent. Omit for all agents.
-
-## Options
-
-| Flag | Short | Type | Default | Description |
-|---|---|---|---|---|
-| `--period` | `-p` | string | `24h` | Time period: `1h`, `24h`, `7d`, `30d` |
-| `--format` | — | string | — | Output format: `json` |
-
-## Examples
-
-```bash
-# All agents — last 24 hours
-npx monomind agent metrics
-
-# Last hour
-npx monomind agent metrics --period 1h
-
-# Last 7 days
-npx monomind agent metrics -p 7d
-
-# Specific agent
-npx monomind agent metrics agent-001
-
-# JSON output
-npx monomind agent metrics --format json
-```
-
-## Output Sections
-
-**Summary table** — total agents, active agents, tasks completed, average success rate, memory vector count
-
-**By Agent Type table** — per-type breakdown: count, tasks completed, success rate
-
-**Memory** — vector count and search backend (HNSW-indexed once vectors exist)
-
-## Data Source
-
-Metrics are read from `.swarm/agents/` state files and `.swarm/swarm-activity.json`. If no agents have been spawned yet, the output will note this with a suggestion to run `agent spawn`.
-
-## MCP Tool
-
-```javascript
-mcp__monomind__agent_status({ agentId: "agent-001" })
-```
-
-## See Also
-
-- `status agents` — live agent status table
-- `agent health` — per-agent health check with `--watch` mode
-- `agent list` — list all agents

package/packages/@monomind/cli/.claude/commands/monitoring/agents.md

@@ -1,71 +0,0 @@
----
-name: monitoring:agents
----
-
-# status agents
-
-Show detailed agent status — ID, type, current task, uptime, and success rate for all running agents.
-
-## Usage
-
-```bash
-npx monomind status agents [options]
-```
-
-## Options
-
-| Flag | Type | Description |
-|---|---|---|
-| `--format` | string | Output format: `json` |
-
-## Examples
-
-```bash
-# Show all agents
-npx monomind status agents
-
-# JSON output
-npx monomind status agents --format json
-```
-
-## Output Columns
-
-| Column | Description |
-|---|---|
-| ID | Agent identifier |
-| Type | Agent type (coder, reviewer, tester, etc.) |
-| Status | `healthy` / `degraded` / `stopped` |
-| Current Task | Task the agent is executing (or `-`) |
-| Uptime | How long the agent has been running |
-| Success | Task success rate (%) |
-
-## Related Commands
-
-```bash
-# Quick agent count overview (in main status)
-npx monomind status
-
-# Agent performance metrics by type
-npx monomind agent metrics
-
-# Agent health check
-npx monomind agent health
-
-# List all agents
-npx monomind agent list
-```
-
-## MCP Tool
-
-```javascript
-mcp__monomind__agent_list({
-  includeMetrics: true,
-  status: "all"
-})
-```
-
-## See Also
-
-- `status` — full system status including agents
-- `agent metrics` — performance metrics over time
-- `agent health` — per-agent health checks

package/packages/@monomind/cli/.claude/commands/monitoring/status.md

@@ -1,108 +0,0 @@
----
-name: monitoring:status
----
-
-# status
-
-Show system status — swarm health, agents, tasks, memory, and MCP server. The primary monitoring command.
-
-## Usage
-
-```bash
-npx monomind status [options]
-npx monomind status <subcommand>
-```
-
-## Options
-
-| Flag | Short | Type | Default | Description |
-|---|---|---|---|---|
-| `--watch` | `-w` | boolean | `false` | Continuously refresh status (live view) |
-| `--interval` | `-i` | number | `2` | Refresh interval in seconds (watch mode) |
-| `--health-check` | — | boolean | `false` | Run structured health checks and exit |
-| `--format` | — | string | — | Output format: `json` |
-
-## Subcommands
-
-| Subcommand | Description |
-|---|---|
-| `status agents` | Detailed agent status table (ID, type, current task, uptime, success rate) |
-| `status tasks` | Detailed task status table (ID, type, priority, agent, progress) |
-| `status memory` | Memory backend stats (entries, size, HNSW, performance metrics) |
-
-## Examples
-
-```bash
-# One-shot status snapshot
-npx monomind status
-
-# Live watch mode (refreshes every 2s)
-npx monomind status --watch
-
-# Watch with custom interval
-npx monomind status --watch -i 5
-
-# Health checks with pass/warn/fail output
-npx monomind status --health-check
-
-# JSON output for scripting
-npx monomind status --format json
-
-# Detailed agent table
-npx monomind status agents
-
-# Detailed task table
-npx monomind status tasks
-
-# Memory backend details
-npx monomind status memory
-```
-
-## Status Display Sections
-
-- **Swarm** — ID, topology, health (`healthy` / `degraded` / `stopped`), uptime
-- **Agents** — active / idle / total counts
-- **Tasks** — pending / running / completed / failed / total
-- **Memory** — backend, entries, size, search time, cache hit rate
-- **MCP Server** — running state, transport, port
-- **Performance** — CPU usage, memory usage, vector search speed
-
-## Health Check Mode
-
-`--health-check` runs structured checks and exits with code 0 (all pass) or 1 (any fail):
-
-| Check | Pass Condition |
-|---|---|
-| System Running | MCP/swarm reachable |
-| Swarm Health | status = `healthy` |
-| Agents Available | active > 0 |
-| MCP Server | running |
-| Memory Backend | backend != `none` |
-| Task Success Rate | < 5% failure rate |
-
-## Watch Mode
-
-`--watch` clears the screen and re-renders on each interval. Press `Ctrl+C` to exit.
-
-## MCP Tools (equivalent)
-
-```javascript
-// Swarm status
-mcp__monomind__swarm_status({ includeMetrics: true })
-
-// Memory stats
-mcp__monomind__memory_stats({})
-
-// Task summary
-mcp__monomind__task_summary({})
-
-// Agent list
-mcp__monomind__agent_list({ includeMetrics: true, status: "all" })
-```
-
-## See Also
-
-- `agent metrics` — performance metrics per agent type
-- `agent health` — agent-specific health check
-- `swarm status` — swarm-specific status
-- `doctor` — comprehensive system diagnostics

package/packages/@monomind/cli/.claude/commands/monobrowse.md

@@ -1,21 +0,0 @@
----
-name: monobrowse
-description: Launch monomind browse for web UI testing and automation — native TypeScript CDP client, no external binary needed
----
-
-Invoke the agent-browser-testing skill to test or automate a web UI.
-
-`monomind browse` is built-in — no install needed. Invoke the skill:
-
-Skill("agent-browser-testing")
-
-Pass the user's argument (if any) as the URL or task description: $1
-
-Use the full monomind browse workflow:
-1. `npx monomind browse open <url>`
-2. `npx monomind browse snapshot -i`
-3. Act using element refs (@e1, @e2, ...)
-4. Re-snapshot to verify
-5. Report results (PASS / FAIL / WARN)
-
-Examples: `/monobrowse`, `/monobrowse https://example.com`, `/monobrowse test the login flow`

package/packages/@monomind/cli/.claude/commands/monoes/README.md

@@ -1,30 +0,0 @@
----
-name: monoes:README
-description: monoes tool family commands — install and manage monotask, mono-agent, and mono-clip
----
-
-# monoes Commands
-
-Commands for interacting with the `monoes` tool family — separate sibling projects (not part of this monorepo) that live alongside it on disk.
-
-| Tool | What it is | Distribution |
-|---|---|---|
-| `monotask` | P2P kanban / task board (Rust, CLI + Tauri desktop app) | Homebrew tap `monoes/tap` (renamed from `nokhodian/tap`) |
-| `mono-agent` | Workflow/browser automation agent (Go CLI + Wails GUI), binary name `monoagentcli` | Prebuilt GitHub releases (`monoes/mono-agent`), or build from source |
-| `mono-clip` | Desktop clipboard/utility app (Tauri + SvelteKit) + `mclip` CLI sidecar | Homebrew tap `monoes/tap` (renamed from `nokhodian/tap`) |
-
-## Files
-
-- [install.md](./install.md) — Detect, install, and troubleshoot any of the three tools; records their existence in monomind's memory once installed
-- [monoagent.md](./monoagent.md) — Drive the mono-agent CLI (`monoagentcli`): logins, search/message/comment, actions, workflows, node execution
-- [monotask.md](./monotask.md) — Drive the monotask CLI: boards/columns/cards, spaces, GitHub/Linear/mail sync
-- [monoclip.md](./monoclip.md) — Drive mono-clip's `mclip` sidecar CLI: clipboard history and folders
-
-## Crash reporting
-
-All four tools (monomind, mono-agent, monotask, mono-clip) auto-file a GitHub issue on their own repo when they hit an uncaught crash — on by default, `monomind crash-reporting disable` to opt out. That only covers hard crashes. If a user is stuck on non-crash friction with any of these tools — a confusing error, undocumented behavior, something that looks like a real bug — suggest opening an issue yourself (`gh issue create -R monoes/<repo> ...`) rather than staying silent about it.
-
-## See Also
-
-- CLAUDE.md Knowledge Graph / memory sections — how monomind persists cross-session knowledge
-- CLAUDE.md's "Crash reporting" behavioral rule

package/packages/@monomind/cli/.claude/commands/monoes/install.md

@@ -1,163 +0,0 @@
----
-name: monoes:install
-description: Detect, install, and troubleshoot the monoes tool family (monotask, mono-agent, mono-clip), then record their existence in monomind's memory
----
-
-# monoes install
-
-Installs one or more tools from the `monoes` family:
-
-| Tool | What it is | Distribution |
-|---|---|---|
-| **monotask** | P2P kanban / task board (Rust, CLI + Tauri desktop app) | Homebrew tap `monoes/tap` (renamed from `nokhodian/tap` — see Gotchas) — `monotask` formula (CLI) + `monotask` cask (desktop) |
-| **mono-agent** | Workflow/browser automation agent (Go CLI + Wails desktop GUI "MonoAgent"), binary name `monoagentcli` | No Homebrew tap — prebuilt CLI binary + desktop app zip on GitHub releases (`monoes/mono-agent`), or build from source |
-| **mono-clip** | Desktop clipboard/utility app (Tauri + SvelteKit) | Homebrew tap `monoes/tap` (renamed from `nokhodian/tap`) — `mono-clip` cask (desktop only, no CLI, but see mclip sidecar below) |
-
-Sibling repos, if present, live at `../mono-agent`, `../mono-clip`, `../monotask` relative to this repo (i.e. `/Volumes/media/projects/monoes/<name>` on this machine) — used as the source-build fallback and as the source of truth for what each tool does.
-
-## Steps
-
-### 1. Detect current state
-
-Run these checks (batch in one message):
-
-```bash
-command -v monotask; command -v monoagentcli; command -v mclip
-ls /Applications 2>/dev/null | grep -iE "monotask|mono ?clip|mono ?agent"
-brew tap 2>/dev/null | grep -iE "nokhodian|monoes/tap"
-which brew
-which go
-which gh
-```
-
-Note for each tool whether: not installed / CLI installed / desktop app installed / both.
-
-### 2. Ask the user what to install
-
-Use `AskUserQuestion` (multiSelect) with options: **All three**, **monotask**, **mono-agent**, **mono-clip** — skip options that detection already shows as fully installed (mention that in the option description). Each selected tool gets **both its CLI and its desktop app by default** — don't ask a CLI-vs-Desktop follow-up. If a tool already has one half installed (e.g. desktop app present, CLI missing), just install the missing half.
-
-### 3. Install each selected tool
-
-**monotask** (prefer Homebrew — use the fully-qualified `monoes/tap/monotask` name; see Gotchas for why; installs both CLI and desktop app by default):
-```bash
-brew tap monoes/tap   # no-op if already tapped
-brew install monoes/tap/monotask            # CLI
-brew install --cask monoes/tap/monotask     # Desktop app
-```
-**Important**: the formula installs the raw binary as `monotaskcli` (not `monotask`), and Homebrew will refuse to auto-link it if the `monotask` cask is also installed ("monotask cask is installed, skipping link"). After install, check `command -v monotask` — if missing, find and symlink it:
-```bash
-ln -sf "$(brew --cellar)"/monotask/*/bin/monotaskcli "$(brew --prefix)/bin/monotask"
-```
-Fallback if Homebrew unavailable or the formula 404s, and `../monotask` exists locally (requires Rust 1.78+):
-```bash
-cd ../monotask
-cargo build -p monotask-cli --release
-cp target/release/monotaskcli /usr/local/bin/monotask
-```
-
-**mono-clip** (Homebrew cask; the `mclip` CLI sidecar auto-installs on first launch, so launch it once as part of install):
-```bash
-brew tap monoes/tap
-brew install --cask monoes/tap/mono-clip
-```
-**Important**: apply the Gatekeeper fix (see Troubleshooting) to `/Applications/MonoClip.app` **immediately after install, before the first launch** — macOS's `syspolicyd`/AppleSystemPolicy can silently move the unsigned app straight to Trash on its first launch attempt, not just show a "damaged" dialog. If that already happened, the app is recoverable: reinstall from Homebrew's cache (`brew reinstall --cask --force monoes/tap/mono-clip`) rather than trying to resurrect it from Trash (there may be an unrelated stale app of the same name already in Trash from a prior session). Then launch it once via explicit path (not `open -a`, which can resolve to a stale same-named app elsewhere on disk — see the mono-agent gotcha below) to trigger the `mclip` CLI symlink:
-```bash
-find /Applications/MonoClip.app -print0 | xargs -0 xattr -c
-codesign --force --deep --sign - /Applications/MonoClip.app
-open /Applications/MonoClip.app
-sleep 2
-ls ~/.local/bin/mclip   # confirm the symlink appeared
-```
-
-Fallback if `../mono-clip` exists locally (requires Rust, Node 18+, pnpm, Tauri CLI):
-```bash
-cd ../mono-clip
-pnpm install
-pnpm build:mclip    # required: builds the mclip sidecar into src-tauri/binaries/mclip-<target-triple>
-                    # (tauri.conf.json's externalBin needs this to exist first — not wired into
-                    # beforeBuildCommand, must be run manually; skipping it fails the bundle step)
-cargo tauri build   # → src-tauri/target/release/bundle/macos/MonoClip.app
-```
-
-**mono-agent** (no Homebrew tap — prefer the prebuilt release binary/app; binary name is `monoagentcli`, desktop app name "MonoAgent"; macOS Apple Silicon shown, swap the asset suffix for other platforms; installs both CLI and desktop app by default):
-```bash
-curl -fsSL https://github.com/monoes/mono-agent/releases/latest/download/monoagentcli-darwin-arm64 -o monoagentcli
-chmod +x monoagentcli
-sudo mv monoagentcli /usr/local/bin/
-```
-(Other CLI assets on the same release: `monoagentcli-darwin-amd64`, `monoagentcli-linux-amd64`, `monoagentcli-windows-amd64.exe`.)
-
-Desktop app "MonoAgent" ships as a zip on the same release (`MonoAgent-darwin-arm64.zip` / `MonoAgent-linux-amd64.tar.gz` / `MonoAgent-windows-amd64.exe`):
-```bash
-curl -fsSL https://github.com/monoes/mono-agent/releases/latest/download/MonoAgent-darwin-arm64.zip -o /tmp/MonoAgent.zip
-unzip -q -o /tmp/MonoAgent.zip -d /tmp/monoagent-extract
-cp -R /tmp/monoagent-extract/MonoAgent.app /Applications/MonoAgent.app   # NOT sudo cp — sudo makes it root-owned
-                                                                          # and breaks the codesign step below
-find /Applications/MonoAgent.app -print0 | xargs -0 xattr -c
-codesign --force --deep --sign - /Applications/MonoAgent.app
-open /Applications/MonoAgent.app   # explicit path, not `open -a MonoAgent` — see Gotchas
-```
-**Important**: use `cp -R` (no `sudo`) to place the app — a `sudo`-owned copy makes `xattr -c` fail on the root-owned `com.apple.provenance` attribute and produces a broken/partial codesign ("internal error in Code Signing subsystem"), confirmed live. And launch it via the explicit `/Applications/MonoAgent.app` path, not `open -a MonoAgent` — if a stray local dev build exists anywhere on disk (e.g. `../mono-agent/wails-app/build/bin/MonoAgent.app` from a prior `wails build`), Launch Services can resolve the bare app name to that one instead of the one just installed.
-
-Fallback if offline/no network access to GitHub, and `../mono-agent` exists locally (requires Go 1.25+, per `go.mod`):
-```bash
-cd ../mono-agent
-CGO_ENABLED=0 go build -o bin/monoagentcli ./cmd/monoagentcli    # or: make build-cli (same output, matches canonical CI build)
-sudo cp bin/monoagentcli /usr/local/bin/monoagentcli
-```
-
-### 4. Troubleshoot as issues come up
-
-Known issues from each project's README/Makefile — apply the fix automatically when the matching error appears, then retry once:
-
-- **`brew`**: not installed → offer `/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"` (confirm with user first, this is a real install action).
-- **The tap was renamed**: `nokhodian/tap` now redirects to `monoes/tap`. If both end up tapped (e.g. from an old muscle-memory command), formula/cask lookups become ambiguous — `Error: Formulae found in multiple taps: * monoes/tap/monotask * nokhodian/tap/monotask`. Fix: always use the fully-qualified `monoes/tap/<name>` form (as in the install commands above); if something was already installed from the old tap name, `brew uninstall nokhodian/tap/<name>` then reinstall from `monoes/tap/<name>` (this reinstalls the identical package under its current tap, not a downgrade/different version — safe). To just clear the ambiguity without touching either install, `brew untap --force nokhodian/tap` is safe as long as the installed formula/cask's `INSTALL_RECEIPT.json` already points at `monoes/tap` (check with `brew info <formula>` or `cat "$(brew --cellar)/<name>"/*/INSTALL_RECEIPT.json`).
-- **Faster path for all of the above**: this repo's own `npx monomind doctor -c monoes-tools --install` runs and auto-fixes exactly these three known issues (tap ambiguity, monotask's missing `monotask`→`monotaskcli` symlink, mono-clip's quarantine flag) — it's an opt-in doctor component, not part of the default `doctor` run, since these are unrelated sibling tools rather than monomind dependencies. Prefer it over manually reapplying the fixes below.
-- **`Refusing to load cask/formula ... from untrusted tap monoes/tap` (or `nokhodian/tap`)** → run `brew trust monoes/tap` (or `brew trust --formula monoes/tap/monotask` / `--cask monoes/tap/<name>` if it's scoped to one item), then retry the install.
-- **`"<App> is damaged and can't be opened"` (Gatekeeper, unsigned app) — or the app silently vanishes / relaunches from Trash**: macOS's `syspolicyd` can reject an ad-hoc-signed app on its very first launch and move it to Trash without any visible dialog (confirmed via `log show --predicate 'eventMessage contains "<AppName>"'`: `AppleSystemPolicy: Security policy would not allow process`). Apply this **before** the first launch, not after:
-  ```bash
-  find /Applications/<App>.app -print0 | xargs -0 xattr -c
-  codesign --force --deep --sign - /Applications/<App>.app
-  ```
-  If the app already got trashed: don't try to recover it from `~/.Trash` (there may be an unrelated older copy of the same app name sitting there from a prior session, and `open -a <App>` can resolve to the wrong one). Instead reinstall from Homebrew's cache — `brew reinstall --cask --force <tap>/<name>` re-extracts a fresh copy into `/Applications` — then apply the fix above immediately, then launch.
-- **`open -a <App>` launches the wrong copy, or a stray dev build**: macOS Launch Services resolves a bare app name against *every* registered app bundle by that name on disk, not just the one in `/Applications` — a leftover local build (e.g. `../mono-agent/wails-app/build/bin/MonoAgent.app` from a prior `wails build`) can win. Always launch by explicit path after install: `open /Applications/<App>.app`.
-- **`sudo cp`-ing an app bundle into `/Applications` breaks the Gatekeeper fix**: use plain `cp -R` (no `sudo`) to place `.app` bundles — Homebrew casks install them user-owned, and a root-owned copy makes `xattr -c` fail on `com.apple.provenance` and can produce a broken/partial `codesign` ("internal error in Code Signing subsystem"). `sudo` is only needed for placing plain CLI binaries into `/usr/local/bin`, not `.app` bundles into `/Applications`.
-- **Go build fails, `go: command not found`** → `brew install go`.
-- **`curl` to the mono-agent release 404s or times out** → confirm the asset name matches the current platform exactly (`monoagentcli-darwin-arm64` etc. — check `gh release view -R monoes/mono-agent --json assets -q '.assets[].name'` for the current list (omit the tag argument entirely to get latest — `gh release view latest ...` is invalid syntax and returns "release not found"), since asset names have changed across past renames), then fall back to the source-build path.
-- **`cargo tauri` not found** → `cargo install tauri-cli` (or check `../mono-clip`/`../monotask` `package.json` for a pinned `@tauri-apps/cli` dev dependency and use `pnpm tauri` instead).
-- **Sibling repo missing** (`../<name>` doesn't exist) → tell the user the source-build fallback isn't available on this machine and stick to the Homebrew path, or ask for the repo path.
-- Any other failure → show the actual error output to the user and ask how they want to proceed. Don't retry silently more than once per issue.
-
-### 5. Verify
-
-After each install, confirm it actually works:
-```bash
-monotask version 2>&1 || true         # subcommand, not --version flag
-monoagentcli version 2>&1 || true    # mono-agent CLI
-mclip --help 2>&1 | head -1 || true  # mono-clip CLI sidecar (after the launch-once step above)
-ls /Applications/Monotask.app /Applications/MonoAgent.app /Applications/MonoClip.app 2>&1
-```
-
-### 6. Record knowledge in monomind
-
-For every tool that ends this run **installed and verified** (not for ones skipped or left failing), store a memory entry so monomind's routing/agents know it exists:
-
-```bash
-npx monomind memory store --namespace tools --key "tool:monotask" \
-  --value "monotask — P2P kanban/task board, Rust. CLI: 'monotask <cmd>' (Homebrew formula installs the raw binary as 'monotaskcli' and won't auto-link to 'monotask' if the same-named cask is present — symlink manually, see install.md). Desktop: Monotask.app. Both CLI and desktop app installed by default. Source: ../monotask. Installed via Homebrew (monoes/tap, renamed from nokhodian/tap). Use /monoes:monotask to interact with it." \
-  --tags "external-tool,cli,desktop,installed"
-
-npx monomind memory store --namespace tools --key "tool:mono-agent" \
-  --value "mono-agent — workflow/browser automation agent, Go + Wails. CLI binary name: 'monoagentcli' (renamed from monoes -> monoagent -> monoagentcli; built from ./cmd/monoagentcli). Desktop app: MonoAgent.app (installed via the release zip, not a cask — cp -R without sudo, then xattr -c + codesign --force --deep --sign - before launch; launch via explicit /Applications path, not open -a, since stray local dev builds can shadow it). Both CLI and desktop app installed by default. Prebuilt binaries on GitHub releases (monoes/mono-agent), no Homebrew tap. Source: ../mono-agent. Use /monoes:monoagent to interact with it." \
-  --tags "external-tool,cli,desktop,installed"
-
-npx monomind memory store --namespace tools --key "tool:mono-clip" \
-  --value "mono-clip — desktop clipboard utility, Tauri + SvelteKit. Desktop app: MonoClip.app (unsigned — apply xattr -c + codesign --force --deep --sign - BEFORE first launch, or macOS silently trashes it). Also ships a CLI sidecar, 'mclip' (list/add/get/pin/folder + an MCP stdio server), auto-symlinked to ~/.local/bin/mclip on first GUI launch — install.md now launches it once as part of install to guarantee the CLI is present too. Source: ../mono-clip. Installed via Homebrew (monoes/tap, renamed from nokhodian/tap, cask). Use /monoes:monoclip to interact with it." \
-  --tags "external-tool,cli,desktop,installed"
-```
-
-Only run the `memory store` calls for the tools actually installed this run — don't overwrite entries for tools the user chose to skip.
-
-### 7. Summarize
-
-One short report: what got installed, what was skipped (and why), what's left to fix, and which memory entries were written.

package/packages/@monomind/cli/.claude/commands/monoes/monoagent.md

@@ -1,148 +0,0 @@
----
-name: monoes:monoagent
-description: Drive the mono-agent CLI (binary `monoagentcli`) — browser-automation bots, workflows, and node execution for Instagram/LinkedIn/X/TikTok/Gemini and API-connected services
----
-
-# monoes monoagent
-
-Interact with **mono-agent** — a Go CLI, source at `../mono-agent`, GitHub `monoes/mono-agent`. Not installed? Run `/monoes:install` first.
-
-**Binary name is `monoagentcli`** (as of release `v0.5.2`, "Binary renamed to monoagent", and finalized to `monoagentcli` in the `v0.7.0`-era release pipeline rework). The project went through two renames: `monoes` → `monoagent` → `monoagentcli`. The Cobra root `Use:` field, the `Makefile`, `.github/workflows/release.yml`, and the actual GitHub release assets all agree on `monoagentcli` — that's current truth. **The README.md in the repo still shows the old `monoes` name in its examples — it's stale, don't follow it.**
-
-Given the user's request in `$ARGUMENTS`, pick the matching command(s) below and run them via Bash. If nothing matches cleanly, run `monoagentcli <subcommand> --help` to double-check rather than guessing a flag shape — **not** `monoagentcli ref commands`, whose hand-maintained flag docs are themselves stale for several commands (see Gotchas). `monoagentcli ref nodes` / `ref node <type>` (the node catalogue) is a separate, more reliable code path and fine to use.
-
-## Global flags (available on every subcommand)
-
-| Flag | Default | Purpose |
-|---|---|---|
-| `--db-path` | `~/.monoagent/monoagent.db` | SQLite state |
-| `--output-dir` | `~/.monoagent/output` | `export` destination |
-| `--config-dir` | `~/.monoagent/configs` | XPath/selector cache |
-| `--headless` | `false` | Run Chrome headless |
-| `--workers` | `1` | Parallel workers |
-| `-v, --verbose` | | Verbose logging |
-| `--json` | | Machine-readable output |
-| `--log-file` | | Log to file |
-| `--profile` | `""` (falls back to `settings.active_profile_id`, then `"default"`) | Active profile |
-
-**Two separate state directories exist** — don't confuse them: `~/.monoagent/*` (DB, output, config-dir — the flags above) vs. `~/.monoes/*` (workflows, installed action templates, crawl captures, the persistent Chrome login profile, Gemini image downloads, ONNX models). This split predates the binary rename and hasn't been cleaned up — real, not a typo.
-
-## Setup / auth
-
-- **Social platforms** (instagram, linkedin, x, tiktok, gemini): `monoagentcli login <platform>` opens a real Chrome window, waits for manual login, saves cookies (30-day expiry). `monoagentcli login status` / `monoagentcli logout [platform|--all]`.
-  - `gemini` needs **no API key** — browser automation against gemini.google.com after login. `monoagentcli login gemini` unlocks `gemini.generate_text` / `gemini.generate_image` / `gemini.chat_session` nodes for free.
-- **API/OAuth services** (Slack, GitHub, Google Sheets, Notion, Stripe, etc.): `monoagentcli connect <platform>`, `monoagentcli connect list --all`, `monoagentcli connect test <id>`, `monoagentcli connect refresh <id>`.
-- A Chrome extension bridge listens on `:9222`; if connected it's preferred over launching Chromium directly. Only one process (CLI or the Wails desktop app, product name "MonoAgent") should hold it at a time.
-- Multiple isolated identities: `monoagentcli profile list|create <name>|switch <name-or-id>|current` — sessions/workflows/actions/connections are all scoped per-profile.
-
-## Command tree
-
-```
-monoagentcli login <platform> [--timeout 3m]        # instagram|linkedin|x|tiktok|telegram|email|gemini
-monoagentcli login status
-monoagentcli logout [platform] [--all]
-
-monoagentcli search <platform> --keyword TEXT [--max 50] [--timeout 10m]
-monoagentcli message <platform> <username> --text TEXT [--timeout 10m]
-monoagentcli comment <platform> <post-url...> --text TEXT [--timeout 10m]
-
-monoagentcli run [action-id] [--file PATH] [--queue] [--watch --interval 30s] [--timeout 10m] [--param k=v ...]
-monoagentcli action list|get <id>|create --type --platform [--keyword] [--message]|import --file PATH
-monoagentcli action pause|resume|delete <id>
-monoagentcli action targets <id>
-monoagentcli action template capture <url> [--headless] [--wait 8] [--out PATH]
-monoagentcli action template install <file>          # writes ~/.monoes/actions/<platform>/<type>.json
-monoagentcli action template list
-
-monoagentcli crawl <url> [--headless] [--wait 8]     # standalone HTML capture for ActionDef authoring
-
-monoagentcli workflow list [--json]
-monoagentcli workflow get <id>
-monoagentcli workflow create <name> [--description] [--active]
-monoagentcli workflow import [--file PATH] [--overwrite]   # reads stdin if no --file
-monoagentcli workflow export <id> [--output PATH]
-monoagentcli workflow run <id>                       # positional — NOT --id
-monoagentcli workflow activate <id> / deactivate <id>
-monoagentcli workflow delete <id> [--force]
-monoagentcli workflow executions <workflow-id> [--limit 20] [--json]
-monoagentcli workflow migrate                        # SQLite store -> ~/.monoes/workflows/*.json
-monoagentcli workflow node add <workflow-id> --type --name [--config json] [--x] [--y]
-monoagentcli workflow node list <workflow-id>
-monoagentcli workflow node set <workflow-id> <node-id> [--config] [--name] [--x] [--y]
-monoagentcli workflow node remove <workflow-id> <node-id>
-monoagentcli workflow connect <workflow-id> --from nodeID[:handle] --to nodeID[:handle]
-monoagentcli workflow disconnect <workflow-id> <connection-id>
-
-monoagentcli node list [--filter STRING]             # control.* data.* http.* db.* comm.* ai.* image.* instagram.* ...
-monoagentcli node run <node-type> [--config json] [--input json] [--output pretty|json|jsonl] [--credential id-or-platform]
-
-monoagentcli connect <platform>
-monoagentcli connect list [--platform] [--json] [--all]
-monoagentcli connect test <id> / remove <id> / refresh <id> [--timeout 5m]
-
-monoagentcli people list [-p platform] [-n 50] / get <id> / delete <id> / import --file --platform
-monoagentcli list ls / create --name / show <id> / delete <id> / add-item <list-id> --username --platform
-monoagentcli template list / get <id> / create --name --body [--subject] / delete <id>
-monoagentcli config list / get <name> / set <name> <value> / delete <name>
-monoagentcli schedule list / add <action-id> --cron "..." [--start-date] [--end-date] / remove <action-id>
-
-monoagentcli export [--output-dir PATH]              # always writes people_export.json + actions_export.json
-monoagentcli status [--json]
-monoagentcli version
-monoagentcli update                                  # self-update from monoes/mono-agent GitHub releases
-monoagentcli init [--claude]                         # installs action-template-generator skill into ~/.claude/skills/
-monoagentcli profile list / create <name> / switch <name-or-id> / current
-
-monoagentcli ref commands|nodes|node <type>|workflow|expressions|examples|crawling   # offline docs, no side effects
-```
-
-## Examples
-
-```bash
-# One-time login, then a quick search
-monoagentcli login instagram
-monoagentcli search instagram --keyword "golang developer" --max 50
-
-# One-off DM / comment
-monoagentcli message instagram johndoe --text "hello"
-monoagentcli comment instagram https://instagram.com/p/xyz --text "nice!"
-
-# Free-tier AI node via Gemini browser automation (no API key)
-monoagentcli login gemini
-monoagentcli node run gemini.generate_text --config '{"prompt":"Summarize AI news today"}'
-
-# Workflow lifecycle
-monoagentcli workflow list
-monoagentcli workflow run <workflow-id>
-monoagentcli workflow activate <workflow-id>     # registers cron/webhook triggers for this process's lifetime
-
-# Connect an API service and inspect connections
-monoagentcli connect github
-monoagentcli connect list --all
-
-# When unsure, check the CLI's own docs instead of guessing
-monoagentcli ref commands
-monoagentcli ref node gemini.generate_image
-```
-
-## Gotchas (verified against source and the live GitHub release)
-
-- Binary name is `monoagentcli` — not `monoes`, not `monoagent`. The repo's own README.md still shows `monoes` in its examples (pre-rename); the Makefile, `root.go`'s Cobra `Use:` field, `release.yml`, and the actual assets on the latest GitHub release (`v0.10.3`) all confirm `monoagentcli`.
-- Prebuilt binaries exist — no need to build from source if a release matches your platform:
-  ```bash
-  curl -fsSL https://github.com/monoes/mono-agent/releases/latest/download/monoagentcli-darwin-arm64 -o monoagentcli
-  chmod +x monoagentcli && sudo mv monoagentcli /usr/local/bin/
-  ```
-  (Also available: `-darwin-amd64`, `-linux-amd64`, `-windows-amd64.exe`. Desktop app "MonoAgent" ships separately as `MonoAgent-darwin-arm64.zip` / `-linux-amd64.tar.gz` / `-windows-amd64.exe`.)
-- `workflow run/get/export`, `workflow node add/connect`, and `node run` take **positional** arguments (`workflow run <id>`, `node run <node-type>`). The README's "CLI Reference" section shows `--id`/`--type`/`--from`/`--to` flag forms that don't match the actual Cobra signatures — don't copy that section literally.
-- There is **no `schedule run` daemon command**, despite `monoagentcli ref workflow`/`ref examples` referencing one. Cron execution only happens via `trigger.schedule` nodes inside a `workflow activate`d workflow, which only fires while that process is alive.
-- `export` always writes `people_export.json` + `actions_export.json` — there's no `--format csv`.
-- `people import` requires **both** `--file` and `--platform`.
-- No standalone always-on daemon ships with the CLI; `run --watch --interval` (polls pending actions) and `workflow activate` (in-process scheduler) are the closest things — the Wails desktop app ("MonoAgent") is the real long-running host in normal use.
-- `monoagentcli update` self-updates from the latest `monoes/mono-agent` GitHub release — prefer it over re-running the install command.
-- `monoagentcli ref commands`' built-in flag/usage docs (the hardcoded `cliDocs` table in `ref.go`) are hand-maintained and stale for several commands — they describe flags that don't exist on the real Cobra definitions (e.g. claims `run` takes `--platform`/`--list`/`--text`, `search` takes `--limit`/`--output`, `message`/`comment` take `--list`/`--delay`, `people` has `add`/`export`/`remove` subcommands instead of the real `list`/`get`/`delete`/`import`, `list create` takes a positional name instead of `--name`, and `export` supports `--format csv`). Don't rely on `ref commands` for exact flag names — use `--help` on the actual subcommand instead. `ref nodes` / `ref node <type>` is a separate, accurate code path.
-
-## See Also
-
-- `/monoes:install` — install mono-agent if the `monoagentcli` binary isn't found
-- `../mono-agent/README.md` — mostly accurate for feature scope, but stale on the binary name and some flag shapes; verify against `cmd/monoagentcli/root.go` / `ref.go` if something looks off