@aitne-sh/aitne 0.1.6 → 0.1.8

package/agent-assets/agent-profiles/_safety.md

@@ -24,28 +24,60 @@
 - **Read-before-write**: PATCH `mode=replace` replaces the entire section.
   Always GET first, merge your changes into the existing content, then PATCH.
   Prefer `mode=append` when simply adding new entries.
-- **Every Bash invocation that hits the daemon API MUST begin with the
-  literal `curl` token.** The session's allow-list is `Bash(curl *)`,
-  prefix-matched against the FULL command string under `dontAsk`. Any
-  wrapping shape is silently denied (no tool result, no error — the
-  call simply does not run):
-  - `echo '{...}' | curl ...` → starts with `echo` → denied
-  - `cat <<JSON | curl -d @-` → starts with `cat` → denied
-  - `bash -c "curl ..."` / `( curl ... )` / `var=x curl ...` → denied
-  - `curl ... ; curl ...` / `curl ... && curl ...` → chained-curl denied
-  Write a single, flat curl call. If you see no response from Bash at
-  all (no stdout, no stderr, no `PA_API_ERROR`), your command was
-  silently denied — rewrite it to start with literal `curl`.
+- **One shell call = one operation.** Every shell invocation that hits
+  the daemon API MUST be a single, flat `curl …` — never combine
+  operations in one call. The following shapes are denied by every
+  backend's shell policy:
+  - Sequencing — `... ; ...`, `... && ...`, `... || ...`
+  - Pipe — `curl … | jq …`, `curl … | head`, `curl … | tee …`,
+    even a single `|`. This includes the very natural-looking
+    `curl http://localhost:8321/api/foo | jq .x` — denied.
+  - Subshell / command substitution — `$(...)`, `` `…` ``
+  - Wrapper-led — starts with `echo`, `cat`, `bash -c`, `sh -c`,
+    `(`, or a variable assignment like `VAR=val curl …`
+  - Multi-target — `curl URL1 URL2 …`, `curl … --next …` / `-:`
+  When you need to consume a response, parse the JSON body in your own
+  response text — do NOT pipe it to `jq` / `sed` / `awk` / `grep`.
+  When you need multiple HTTP calls, issue them as **separate** shell
+  invocations. When you need a large body, use the heredoc-into-curl
+  shape documented below — `curl … -d @- <<'JSON' … JSON` keeps the
+  command starting with `curl` (do NOT pipe from `cat <<JSON | curl …`,
+  which starts with `cat` and is denied).
+- **The shell surface is intentionally narrow.** Each backend's policy
+  permits only `curl http://localhost:${port}/...` and `git …` (no
+  `push --force`, `reset --hard`, `clean`). Common utilities — `jq`,
+  `sed`, `awk`, `tee`, `echo`, `cat`, `head`, `tail`, `grep`, `find`,
+  `ls`, `wc`, `xargs` — are NOT on the shell allow-list. Use the
+  daemon API's structured query params (`?fields=`, `?limit=`,
+  `?since=`, `?folder=`, …) or your backend's built-in read tools
+  (Claude: `Read` / `Grep` / `Glob`; Gemini: `read_file` /
+  `grep_search` / `list_directory` / `glob`) instead of trying to
+  filter shell output.
+- **How a denial surfaces, by backend** — recognise the shape so you
+  rewrite and retry instead of looping on it:
+  - **Claude Code** — `Bash` PreToolUse hook. Chained-curl / `--next` /
+    multi-URL / wrapper shapes return a visible block decision with a
+    reason string. Tools or commands that aren't in the session's
+    `Bash(curl *)` allow-list under `dontAsk` are silently denied (no
+    stdout, no stderr, no `PA_API_ERROR`) — if a `Bash` call returns
+    NOTHING at all, your command was denied; rewrite to a single flat
+    `curl …` starting with the literal `curl` token.
+  - **Gemini CLI** — `run_shell_command` denial returns a visible
+    error of the form `Error executing tool run_shell_command: Tool
+    execution denied by policy. <reason>` and ends the turn as a
+    decisive failure (no retry, no fallback on resume — the chat just
+    fails). Same fix: rewrite as a single flat `curl …` (no `|`, no
+    `;`, no `&&`, no `$(…)`, no `jq`/`sed`/`awk`) and try again.
 - **Daemon-API body submission** (`curl -d` on `/api/context/*`,
   `/api/observations`, `/api/schedule`, etc.). Two safe shapes:
   - Inline JSON — `-d '{"key":"value"}'`. Use for small / single-line
     bodies. Escape internal newlines as `\n`.
   - Stdin heredoc on the SAME curl line — `curl ... -d @- <<'JSON'`
-    + body + `JSON`. Note: the heredoc is redirected into `curl`'s
-    stdin so the command still STARTS with `curl`; do NOT pipe from
-    `cat <<JSON | curl …` (that starts with `cat` and is silently
-    denied). `@-` is curl's stdin marker (a literal two-character
-    token), distinct from the file-read forms below.
+    + body + `JSON`. The heredoc is redirected into `curl`'s stdin so
+    the command still STARTS with `curl`; do NOT pipe from
+    `cat <<JSON | curl …` (that starts with `cat` and is denied).
+    `@-` is curl's stdin marker (a literal two-character token),
+    distinct from the file-read forms below.
 
   Never use `-d @<filepath>` / `--data-raw '@<filepath>'` /
   `-F field=@<filepath>`. They are file-read shapes — safe mode

package/agent-assets/agent-profiles/profile-importer.md

@@ -17,7 +17,7 @@ Concrete examples:
 | Source line | Acceptable target | NOT acceptable |
 |---|---|---|
 | `Works at Acme.` | `- Works at Acme.` | `- Employed full-time at Acme Corp.` |
-| `母 Yoko (1955–)` | `- 母 Yoko (1955–)` | `- Mother: Yoko, born 1955, currently alive` |
+| `Mother Yoko (1955–)` | `- Mother Yoko (1955–)` | `- Mother: Yoko, born 1955, currently alive` |
 | `Likes coffee, hates morning meetings` | two bullets, one per clause, copied verbatim | `- Prefers coffee over morning meetings` |
 | `Living in Tokyo since 2019.` | `- Living in Tokyo since 2019.` | `- Resides in Tokyo (5+ years).` |
 

package/agent-assets/agent-profiles/routine.md

@@ -7,7 +7,7 @@ You execute autonomous scheduled routines (morning/evening). No direct user inte
 - Write all state changes via Daemon API. Follow rules/management.md for autonomy levels and source of truth.
 - On step failure (API error, missing data), log to Agent Log and continue with remaining steps.
 - Register follow-up wake-ups (POST /api/schedule) before ending.
-- User-facing text obeys notify skill § Universal user-facing message discipline. This profile's posture: silent-by-default — user-visible output is only via explicit POST /api/notify. Per-routine wrap-up contracts (evening review, hourly check) own the go/no-go decision and layer on top of the universal section.
+- User-facing text obeys notify skill § Universal user-facing message discipline. This profile's posture: silent-by-default — user-visible output is only via explicit POST /api/notify, either from a per-routine contract (hourly check) or from user-authored `routines/*.md` rules that explicitly invoke it.
 
 ## Output discipline
 - Agent Log entries: max 1 sentence. Action + outcome, no narration.
@@ -27,6 +27,7 @@ rendered fresh per session — trust it over memory.
 the daemon's `/api/<key>/*` routes and
 `POST /api/integrations/<key>/exec` both return `410`. Consult the
 per-integration skill body materialised under `.claude/skills/` /
-`.codex/skills/` / `.gemini/skills/` for the exact tool namespace and
-the destructive-confirm contract that still applies.
+`.codex/skills/` / `.gemini/skills/` (OpenCode reuses `.claude/skills/`)
+for the exact tool namespace and the destructive-confirm contract that
+still applies.
 

package/agent-assets/docs/concepts/agent-day.md

@@ -17,19 +17,24 @@ tags:
   - core
   - timing
   - memory
+  - routines
 status: stable
 ask_examples:
   - When does the agent day actually roll over?
   - Why is my late-night work showing up under yesterday?
   - How do I change the day boundary?
+  - What is dayBoundaryHour?
 locale: en-US
 created: 2026-04-25
-updated: 2026-04-25
+updated: 2026-05-15
 keywords:
   - day boundary
   - 04:00
   - dayBoundaryHour
   - rollover
+  - agent day
+  - getAgentDayBoundsUtc
+  - getAgentDayDateStr
 related:
   - features/routines/morning-routine
   - features/memory-files/today

package/agent-assets/docs/concepts/auth-health.md

@@ -7,6 +7,8 @@ aliases:
   - auth probe
   - auth recovery
   - credentials
+  - auth health monitor
+  - subscription auth warning
 category: concepts
 summary: |
   The auth-health monitor probes each backend's credentials at startup
@@ -17,19 +19,26 @@ tags:
   - core
   - safety
   - backends
+  - operations
 status: stable
 ask_examples:
   - Why is the dashboard showing a degraded backend?
   - How does the agent check that I'm still logged in to Claude?
   - What happens when my Codex token expires?
+  - What is the SubscriptionAuthWarning banner?
 locale: en-US
 created: 2026-04-25
-updated: 2026-05-04
+updated: 2026-05-15
 keywords:
   - auth
+  - authentication
   - credentials
   - probe
   - degraded
+  - auth health monitor
+  - auth recovery
+  - api-key-probe
+  - SubscriptionAuthWarning
 related:
   - concepts/backends-and-tiers
   - concepts/costs-and-quotas

package/agent-assets/docs/concepts/backends-and-tiers.md

@@ -5,32 +5,38 @@ title: Backends and Tiers
 id: backends-and-tiers
 aliases:
   - models
-  - claude codex gemini
+  - claude codex gemini opencode
   - heavy tier
   - light tier
+  - main backend
+  - fallback backend
 category: concepts
 summary: |
-  Aitne runs on three backends — Claude Code, Codex, Gemini CLI.
-  Each backend has a heavy and a light tier; the dispatcher picks the
-  binding for every ProcessKey based on operator configuration.
+  Aitne runs on four backends — Claude Code, Codex, Gemini CLI, OpenCode.
+  Each backend exposes light, medium, and high model tiers; the dispatcher
+  picks the binding for every ProcessKey based on operator configuration.
 section: backends
 tags:
   - core
   - backends
   - models
   - cost
+  - routing
 status: stable
 ask_examples:
   - Which model does my morning routine use?
   - How do I switch from Claude to Codex?
   - What is the difference between heavy and light tier?
+  - What is OpenCode and when should I use it?
+  - How does Aitne fail over when a backend hits its quota?
 locale: en-US
 created: 2026-04-25
-updated: 2026-05-04
+updated: 2026-05-15
 keywords:
   - claude
   - codex
   - gemini
+  - opencode
   - opus
   - sonnet
   - haiku
@@ -40,11 +46,13 @@ keywords:
   - vertex
   - foundry
   - azure-openai
+  - openrouter
+  - routing
+  - fallback
 related:
   - concepts/process-keys
   - concepts/costs-and-quotas
   - features/operations/backend-routing
-  - guides/use-cloud-providers
 ui_anchors:
   - /settings/models
 ---
@@ -53,21 +61,28 @@ ui_anchors:
 
 ## TL;DR
 
-Three backends are supported: **Claude Code** (default),
-**Codex**, and **Gemini CLI**. Each backend exposes three classes of
-model used at install time:
-
-- **Main** (Sonnet 4.6 / GPT-5.4-mini / Gemini 3 Flash) — the default
-  for owner-facing work (DMs, daily / weekly / monthly review,
-  morning routine, dashboard chat, scheduled tasks).
-- **Delegated** (Haiku 4.5 on Claude; latest light tier on Codex /
-  Gemini) — cheaper model used for "simple" backend surfaces with no
-  owner in the loop: Gmail classification, GitHub event triage,
-  git-poll observers, calendar-change handlers, the
-  `delegated_task` invoker.
-- **Heavy** (Opus 4.7 / GPT-5.5 / Gemini 3 Pro) — registered but
-  *not* auto-selected. Operators opt in per-process from
-  `/settings/models`.
+Four backends are supported: **Claude Code** (default), **Codex**,
+**Gemini CLI**, and **OpenCode**. Each backend exposes three classes
+of model used at install time:
+
+- **Medium / Main** (Sonnet 4.6 / GPT-5.4-mini / Gemini 3 Flash /
+  Sonnet 4.6 via OpenCode) — the default for owner-facing work (DMs,
+  daily / weekly review, morning routine, dashboard chat, scheduled
+  tasks).
+- **Lite / Delegated** (Haiku 4.5 on Claude and OpenCode; latest
+  light tier on Codex / Gemini) — cheaper model used for "simple"
+  backend surfaces with no owner in the loop: Gmail classification,
+  GitHub event triage, git-poll observers, calendar-change
+  handlers, the routine pre-pass fetcher, the `delegated_task`
+  invoker.
+- **High / Heavy** (Opus 4.7 / GPT-5.5 / Gemini 3 Pro / Opus 4.7
+  via OpenCode) — registered but *not* auto-selected. Operators opt
+  in per-process from `/settings/models`. After morning-routine
+  Phase 7 (2026-05-16) the only flows that run heavy by default are
+  `setup` (one-shot wizard) and `knowledge.import` (owner-uploaded
+  files). The first morning routine after setup runs on medium
+  tier with a daemon-prepared `<roadmap_skeleton>` block instead of
+  the retired heavy `routine.morning_routine_initial`.
 
 Every ProcessKey resolves to a backend + model binding via
 `BackendRouter`. Aitne **does not store or read subscription-plan
@@ -79,11 +94,12 @@ install time and edited from `/settings/models`.
 Each backend authenticates via a provider API key registered on
 `/settings/models`. The provider dropdown picks one of:
 
-| Backend | Direct API key | Cloud provider options |
+| Backend | Direct API key | Cloud / aggregator options |
 |---|---|---|
 | `claude` | `anthropic` (`sk-ant-…`) | `bedrock` (Amazon Bedrock), `vertex` (Google Vertex AI), `foundry` (Microsoft Foundry) |
 | `codex` | `openai` (`sk-…`) | `azure-openai` (Codex CLI on Azure OpenAI; daemon writes a managed `config.toml` under `<dataDir>/codex-home/`) |
 | `gemini` | `google` (`AIza…`) | `gemini-vertex` (Gemini on Google Vertex AI) |
+| `opencode` | provider key forwarded to the OpenCode server (Anthropic / OpenAI / OpenRouter / …) | "Managed" mode runs a local `opencode` HTTP server on loopback; "Remote" mode points at a baseUrl you operate |
 
 API keys are the recommended and provider-supported auth method for
 headless agent use; if you skip the key the daemon falls back to the
@@ -92,18 +108,35 @@ officially support — Anthropic in particular currently prohibits the
 Claude Agent SDK on a Claude Pro / Max subscription. The dashboard
 surfaces a warning whenever a backend is on subscription auth.
 
-Cloud providers (Bedrock / Vertex / Foundry / Azure OpenAI /
-Gemini-Vertex) let teams reuse an existing enterprise contract,
-keep model traffic inside a private VPC, or take advantage of
-provider-side rate-limit pools. Aitne stores the credentials in the
-OS keychain and mirrors the corresponding env vars
-(`CLAUDE_CODE_USE_BEDROCK=1`, `CLAUDE_CODE_USE_VERTEX=1`,
-`CLAUDE_CODE_USE_FOUNDRY=1`, `GOOGLE_GENAI_USE_VERTEXAI=true`, …)
-into the backend subprocess. See
-[Use cloud providers](../guides/use-cloud-providers.md) for the
-end-to-end walkthrough and
-[Costs and Quotas](costs-and-quotas.md) for the cost shape of each
-path.
+Cloud / aggregator providers (Bedrock / Vertex / Foundry / Azure
+OpenAI / Gemini-Vertex / OpenRouter via OpenCode) let teams reuse
+an existing enterprise contract, keep model traffic inside a private
+VPC, or take advantage of provider-side rate-limit pools. Aitne
+stores the credentials in the OS keychain and mirrors the
+corresponding env vars (`CLAUDE_CODE_USE_BEDROCK=1`,
+`CLAUDE_CODE_USE_VERTEX=1`, `CLAUDE_CODE_USE_FOUNDRY=1`,
+`GOOGLE_GENAI_USE_VERTEXAI=true`, …) into the backend subprocess.
+See [Costs and Quotas](costs-and-quotas.md) for the cost shape of
+each path.
+
+## OpenCode (4th backend)
+
+OpenCode joined as a 4th backend in 2026-05. It is implemented on
+top of the `@opencode-ai/sdk` HTTP server and supports the same
+`ProcessKey` set as the other backends. Two operating modes:
+
+- **Managed** — the daemon spawns and supervises a local
+  `opencode` HTTP server on loopback. Configuration (model,
+  permissions, agent dir) is written into a managed `opencode.json`
+  under `<dataDir>/opencode-home/`.
+- **Remote** — you point Aitne at an existing OpenCode server
+  baseUrl (your own cluster or a managed deployment).
+
+OpenCode is a runtime peer of Claude / Codex / Gemini for
+dispatching ProcessKeys, but it intentionally does **not** host
+native-mode integration connectors (Gmail / Calendar / Notion go
+through the daemon's polling path or another backend's MCP). See
+`docs/design/appendices/opencode-backend.md` for the full design.
 
 ## Why This Concept Exists
 
@@ -120,11 +153,13 @@ Claude's quota is exhausted, or use Gemini for cheap polling tasks.
 
 ## Definitions
 
-- **Backend**: the agent runtime. One of `claude`, `codex`, `gemini`.
-- **Tier**: `heavy` or `light`. Heavy maps to the strongest model
-  (Opus / GPT-5.5 / Gemini 3 Pro). Light is the operator's day-to-day
-  tier and split at install time into Sonnet (main) vs Haiku
-  (delegated/simple).
+- **Backend**: the agent runtime. One of `claude`, `codex`, `gemini`,
+  `opencode`.
+- **Tier**: `lite`, `medium`, or `high`. `high` maps to the strongest
+  model (Opus 4.7 / GPT-5.5 / Gemini 3 Pro / Opus 4.7 via OpenCode).
+  `medium` (Sonnet 4.6 and equivalents) is the operator's day-to-day
+  tier for owner-facing work; `lite` (Haiku 4.5 and equivalents) is
+  reserved for mechanical / delegated surfaces.
 - **Main / Fallback**: each ProcessKey has a `main` backend and a
   `fallback`. The router fails over on `BackendQuotaError` /
   `BackendDecisiveFailure`.
@@ -136,7 +171,6 @@ Claude's quota is exhausted, or use Gemini for cheap polling tasks.
 | `routine.morning_routine` | claude | Sonnet 4.6 |
 | `routine.evening_review` | claude | Sonnet 4.6 |
 | `routine.weekly_review` | claude | Sonnet 4.6 |
-| `routine.monthly_review` | claude | Sonnet 4.6 |
 | `routine.hourly_check` | claude | Sonnet 4.6 |
 | `message.dm` | claude | Sonnet 4.6 |
 | `dashboard.chat` | claude | Sonnet 4.6 |

package/agent-assets/docs/concepts/costs-and-quotas.md

@@ -7,6 +7,9 @@ aliases:
   - cost
   - budget
   - quota
+  - daily cap
+  - cost cap
+  - per-token billing
 category: concepts
 summary: |
   How Aitne meters per-call costs and provider quotas, and where the
@@ -14,17 +17,21 @@ summary: |
   dashboard reports, it does not bill.
 section: cost
 tags:
+  - core
   - cost
   - quotas
-  - core
+  - backends
+  - operations
 status: stable
 ask_examples:
   - How do I see how much my agent is spending?
   - Why did the agent fail over from Claude to Codex?
   - What does the autonomous daily cost cap do?
+  - Does OpenCode billing differ from the other backends?
+  - How does Gemini's per-day quota work?
 locale: en-US
 created: 2026-04-25
-updated: 2026-05-04
+updated: 2026-05-15
 keywords:
   - cost
   - budget
@@ -33,11 +40,14 @@ keywords:
   - per-token billing
   - gemini quota
   - subscription fallback
+  - opencode
+  - openrouter
+  - daily cap
+  - autonomous cap
 related:
   - concepts/backends-and-tiers
   - concepts/auth-health
   - features/operations/cost-tracking
-  - guides/use-cloud-providers
 ui_anchors:
   - /analytics
   - /settings/models
@@ -58,6 +68,12 @@ per-call against your provider account:
 - **Codex (via Codex CLI)** — per-token billing on `OPENAI_API_KEY`.
 - **Gemini (via Gemini CLI)** — per-token billing on `GEMINI_API_KEY`
   / `GOOGLE_API_KEY`; the free tier has per-day caps.
+- **OpenCode (via `@opencode-ai/sdk`)** — billing follows whichever
+  upstream provider the OpenCode server is configured against
+  (Anthropic / OpenAI / OpenRouter / …). Aitne reads cost telemetry
+  from the SDK's `session.info.cost` + `info.tokens` fields and
+  falls back to its local `MODEL_REGISTRY` pricing when the upstream
+  reports `cost === 0` against non-zero tokens.
 
 If you skip the API key, the daemon falls back to whatever
 subscription auth the CLI already has on your machine. That fallback
@@ -139,8 +155,12 @@ register an API key on `/settings/models`.
   cost reduction per fire).
 - Morning routine on Opus via `ANTHROPIC_API_KEY` = per-token billing
   on the Opus rate; pin only when Sonnet has failed the task. **No
-  recurring routine seeds on Opus by default** — only the one-shot
-  `routine.morning_routine_initial` runs heavy out of the box.
+  recurring routine seeds on Opus by default**, and after
+  morning-routine Phase 7 (2026-05-16) **no one-shot routine seeds
+  on Opus either** — `routine.morning_routine_initial` was retired
+  and the first-run branch runs on the parent
+  `routine.morning_routine` envelope (medium tier) with a
+  daemon-prepared `<roadmap_skeleton>` block.
 - Gemini hourly check on Flash via `GEMINI_API_KEY` = ~$0.0005 per
   fire on the paid tier; free tier instead consumes a per-day quota
   slot.