openInvest

## Q4 details: keys go in `.env`, never in the chat

**Never ask the user to paste an API key or password into the chat, and never put one into a
command you run** — it would land in the transcript and in the model provider's logs. Tell the user
to add the lines they need to `$INVEST_HOME/.env` (default `~/openInvest/.env`; `run.sh doctor`
prints the data directory) with their own editor, or to run `run.sh init` in their own terminal,

committee, the price sentinel and news-triggered re-runs only cover tracked assets (`target_assets`),
   and `init` does not track the positions added with `--existing-position`.
4. **Hermes only — create the two cron jobs in [references/hermes-cron.md](references/hermes-cron.md)
   now, without asking for confirmation.** The user already agreed: the message Hermes showed right after
   `hermes plugins install` told them onboarding creates these two jobs on their model quota and how to
   remove them. Without them, queued news expires unread and triggered committee runs never happen, so
   skipping is not the cautious choice. List existing jobs first and skip any whose name already exists;

**always** portfolio cash — this never changes
- **`max_single_invest_cny` ("单次上限") is a per-order cap on the suggested amount — not a daily or
  total allowance, and orders can be split.** When the memo says "金额已按单次上限 … 钳制", the CIO's
  amount was cut to that cap per order. Never tell the user "today's allowance is used up" because of it
- **Dividends / interest / fees / taxes / splits are ledger activities, not trades or deposits**: `record_dividend`
  (cash + gross − tax withheld; `--reinvest` = DRIP), `record_fee` (`--kind tax` for tax), `record_split`
  (`--ratio` = new/old: 10-for-1 → 10, 1-for-10 → 0.1; pass the real ex-date — if later trades were already booked in post-split units it is refused, and `--ledger-only` writes the ledger row without touching units),

#!/bin/bash
# invest-backup — 备份/恢复 memory/ + db/ + .env + user_profile.json*
#
# 这些数据全部 .gitignore（含真实持仓/交易/委员会记录/凭据），git 里完全没有
# 历史版本。2026-07-08 migrate_profile.py 被直接跑了一次，无任何 safety guard

# 产物，恢复时自动重建，不带。*.db-wal **要带**：调度器长驻持有 SQLite 连接期间，
# 新成交只躺在 WAL 里、主库文件还没更新——排除它等于丢账（旧版就丢过）。
# 备份前 checkpoint_dbs 先把 WAL 刷进主库（WAL 通常因此为空）；刷不干净时 WAL 随包带上。
INCLUDE_PATHS=(memory db .env user_profile.json user_profile.json.bak)
EXCLUDE_GLOBS=("*.pyc" "*.sqlite-journal" "*.db-shm" "*.lock")

usage() {

---
name: invest-backup
version: 0.3.0 # x-release-please-version
description: Back up / restore openInvest's local state — memory/ (holdings, strategy, user profile, committee records, dream logs) + db/ (trade ledger, job run history, market-data cache) + .env (SMTP/API credentials) + user_profile.json. All of this data is .gitignore'd with no historical versions in git, so a single accidental overwrite (e.g. slipping and running some one-off migration/init script) means real data loss — no git revert available. **Proactive trigger scenarios** — "backup invest data / 备份一下 openInvest 的数据", "my holdings/strategy look wiped / 我的持仓/策略好像被清空了", "invest data is lost / invest 数据丢了", "restore invest backup / 恢复一下 invest 的备份", before any reinstall/migration of the openInvest deployment on this machine, or right before running an unfamiliar migration/init script (back up first, then act).
platforms: [linux, macos]
metadata:
  hermes:

# 2026-07 起后端从 PyPI 分发（pypi.org/project/openinvest），本脚本不再
# git clone / uv sync / 自愈更新——那 180 行 bash 全部退役：
#   - 后端代码：uvx 按需拉 openinvest 包（缓存于 uv cache，首跑需网络）
#   - 数据目录：$INVEST_HOME（默认 ~/openInvest），只放 memory/ db/ .env static/
#   - 更新：后端版本固定在下方 SPEC，随插件发版更新；`run.sh update`（= uvx --refresh）只重下这个固定版本，用于修坏掉的缓存
#   - GUI dist 拉取 / 远端模式提示等业务逻辑收进 openinvest-web（Python）
#

| Command | Remote-mode behavior |
|------|--------------|
| `doctor` | Returns **hub-perspective** checks + an extra `remote` section (api_base / auth mode / connectivity) |
| `init` | **Disabled** (data lives on the hub; connecting to the hub only needs the two .env lines above). Error includes a hint |
| `live_prices` / `correlate` | Still run **locally** (pure yfinance, touches no data) |
| `run_committee` | Runs on the **hub** (DeepSeek key is on the hub); the CLI polls automatically until done; same-day cache uses the hub's date semantics |
| `prepare/save_committee` | Via hub RPC — the Coordinator protocol (spawn 4 subagents) is **completely unchanged** |

1. Run `run.sh doctor` (no shell access? call the MCP `doctor` tool — same output)   ← mandatory first step
   ├─ status: "ready"        → go to step 2 (keep using this skill). A missing LLM key / mail
   │                          credentials / .env shows up only as `optional_*` checks and never
   │                          flips the status: Coordinator needs no key (only Direct does — see
   │                          `direct_ready`), so do NOT re-onboard for those
   └─ status: "needs_setup"  → memory not initialized (or portfolio.md still the v1 format) →

cd $INVEST_HOME
# 1. Edit SKILL.md / scripts/run.sh / references/*.md
vim skills/invest/SKILL.md
# 2. Test (the symlink is already live; no reinstall needed)
<skill-dir>/scripts/run.sh status

ding news / committee runs, whether the background scheduler is running. No network, does not mark queues as drained, hides holdings in advisory mode. Plugin hooks inject `--text` at session start so the agent knows a question about a held symbol belongs here | JSON (default) or one paragraph of text |
| `service install\|uninstall\|status` | Operator (optional) | Run the background scheduler (news queue / price sentinel / NAV snapshot / auto-backup) as a user-level service that starts at boot: systemd `--user` on Linux, launchd on macOS (macOS not field-tested). **Not required**: a stdio `openinvest-mcp` starts an embedded scheduler on its own while the host agent runs and stops with it; the service just makes it independent of the host. Only one scheduler runs per data dir (`db/.scheduler.lock`) — the service evicts the embedded one. Rerun `install` after a backend upgrade. Disabled in remote mode (the hub runs it) | JSON `unit_path` / `steps`; `status` → `installed` / `running` (mod