@awak-app/simy-cli 0.7.29 → 0.7.31

package/README.md

@@ -312,7 +312,30 @@ existing enabled plugins. Unrelated plugins and hooks are preserved.
 `--no-workflow-prompt` skips initial preparation and background installation of
 missing sources. Provider plugin enablement and hook trust remain provider-owned.
 
-SQM checks apply when you explicitly select `@simy`, invoke the SQM skill, or ask to use SQM for the current task. Ordinary PR creation and `git push` do not opt in. Upgrading and restarting the daemon migrates the legacy global PR gate and shipped personal skills; unrelated hooks are preserved. Start a new coding session to reload skill instructions.
+For conversation continuation, select SIMY in the Codex app with `@` and ask
+`continue this task` (Japanese: `この作業を続けて`). The `continue` skill uses the
+running app's existing Auto Continue switch and background coordinator. In
+Codex CLI, use its native `$simy:continue` skill selector; in Claude Code use the
+native `/simy:continue` command. Claude Code does not define `@simy` as a plugin
+command: use the slash command for an explicit invocation. Merely mentioning
+SIMY or seeing it in a menu does not start work.
+
+The current plugin and CLI must both be installed, the SIMY app must be running
+and signed in, and the original provider must be connected with its required
+hooks enabled and trusted. A running original turn finishes before SIMY sends
+another one. The chat command uses the exact original conversation; it never
+starts a second Claude process or replaces a task to bypass a stop. Existing
+stops, approval waits, goals, corrections and history retain their meaning.
+
+The entry reports the same real work state, reason and next action shown by the
+app. ON or `accepted: true` means delegation was saved; it does not prove a
+provider turn executed. Inspect an exact target again with
+`simy delivery auto-continue status --provider codex|claude --session UUID`.
+`on` and `off` use the same target syntax. After a lost response, read status
+before retrying. An old CLI that lacks this command needs its normal update;
+the retired local delivery agents remain retired.
+
+SQM checks apply when you explicitly request a quality check with `@simy`, invoke the SQM skill, or ask to use SQM for the current task. A continuation request selects `continue` instead. Ordinary PR creation and `git push` do not opt in. Upgrading and restarting the daemon migrates the legacy global PR gate and shipped personal skills; unrelated hooks are preserved. Start a new coding session to reload skill instructions.
 
 After installation, restart Codex and find and install **SIMY** in **Plugins**
 before using `@simy` in a new task.
@@ -382,8 +405,8 @@ provider refresh display an unknown execution state.
 
 List-only hiding supports multiple selection and restoration without changing
 provider archive state or execution consent. Codex archive/restore is a separate
-explicit operation; Claude archive/restore must be performed in Claude, and SIMY
-reads its Desktop archive metadata on refresh. Related GitHub PR summaries are
+explicit operation. Claude Desktop Code-tab archive/restore is available through
+the terminal commands below on macOS, with native provider state readback. Related GitHub PR summaries are
 read from structured provider metadata and refreshed through an installed,
 authenticated `gh` CLI, with bounded reads, a one-minute cache, timestamps and
 failure indicators. A merge alone never completes a conversation, and known
@@ -1338,6 +1361,12 @@ Connect an existing NVIDIA/SSH machine from **Remote connections…** in the
 conversation sidebar. SIMY merges its conversations and sends operations to the
 original machine. See [setup, access requirements and recovery](docs/remote-codex-sessions.md).
 
+When moving between LAN, Wi-Fi and mobile tethering, keep that same SSH alias
+and use a reachable VPN address or DNS name for its `HostName`. SIMY creates a
+fresh SSH connection after disconnection while retaining host and operation
+identity. A LAN-only address cannot provide access from another network; see
+[network switching setup](docs/remote-codex-sessions.md#switching-between-lan-wi-fi-and-a-phone-hotspot).
+
 ### Local conversation list on NVIDIA / Linux
 
 Run `simy sessions` to list local and explicitly registered SSH hosts. It reads
@@ -1384,6 +1413,62 @@ existing native protocol header. Web/gateway should preserve this marker and
 Backend should require it at claim/invocation when a destination/Photos profile
 is requested, so an old worker cannot silently ignore those required outputs.
 
+### Original conversation archive and restore
+
+Update and start SIMY on the controller and conversation host, and connect Claude
+in SIMY using the existing provider settings. For Claude, the conversation host
+must be macOS with Claude Desktop signed in to its Code tab. The graphical SIMY
+interface is unchanged; these explicit terminal commands operate the original
+provider conversation, separately from hiding it in SIMY.
+
+```sh
+simy sessions --provider claude --include-archived --json
+simy sessions provider-status --provider claude
+simy sessions provider-setup --provider claude
+simy sessions archive --provider claude --session UUID
+simy sessions restore --provider claude --session UUID
+```
+
+Replace `UUID` with the exact session ID from the list. Setup opens macOS
+Accessibility settings on the conversation host. Enable access for the application
+running SIMY (SIMY for the installed app, or the terminal application for terminal
+launches), then run `provider-status` again. On newer macOS versions this pane
+may be named “Device Control and Data Access” (デバイスの制御とデータへのアクセス).
+If macOS displays its access-request dialog, choose Open System Settings. If the
+app is not listed, use the pane's Add (+) button and select the app running SIMY.
+Complete any Touch ID/password authentication directly on the Mac; never send
+that password to SIMY or a chat. `available: true` means the installed
+Claude application and accessibility permission are present; it does not establish
+that a particular conversation is idle or its window is available. No development
+SSH key, fixed hostname, compiler, debug port, or transcript edits are required.
+
+For an already registered SSH host, add `--host SSH_ALIAS --session UUID` to setup
+and status commands, and `--host SSH_ALIAS` to archive/restore. Settings open on
+that remote Mac. Normal SSH, SIMY account/provider authorization and macOS
+permissions still apply. Linux and Windows conversation hosts report an explicit
+unsupported-platform error for Claude native control.
+
+Keep Claude available in an unlocked desktop while the operation runs. SIMY
+opens the exact Code-tab conversation and uses Claude's own archive/restore
+control. Running conversations and automatic continuation must be stopped first.
+Before opening that conversation, SIMY checks Claude's visible windows for
+unsent input, generating responses and dialogs. It leaves the current conversation
+in place if any are present or the window/input state cannot be inspected. The
+same work-state checks run again before the native archive/restore action.
+If a window closes, another dialog covers the action, or the selected identity
+changes, the command fails instead of selecting another conversation. Claude UI
+changes or unsupported languages can also make native controls unavailable;
+Japanese controls were tested on Claude Desktop 3.1623.0.
+
+The result is JSON. `ok: true` with `data.state: "verified"` means Claude's archive
+state was read back; `data.archived` is the resulting value. `changed: false`
+means the conversation already had that state. Setup/status exit with code 2
+when permission is not ready; failures exit with code 1. After a disconnect or
+unknown result, refresh the list before retrying. The optional `--request-id ID`
+correlates remote operations. Commands attach to the existing SIMY owner and do
+not start a second supervisor. Codex supports the same archive/restore commands
+with `--provider codex`.
+
 ### Delivery entry routes
 
 Crew owns `sessionLoopOptions` in the distributed loop kernel. Codex enrollment,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@awak-app/simy-cli",
-  "version": "0.7.29",
+  "version": "0.7.31",
   "description": "Local SIMY executor for non-coding Local Tasks and Agentic Loop runs.",
   "type": "module",
   "bin": {
@@ -12,7 +12,7 @@
   ],
   "scripts": {
     "start": "node ./src/index.js",
-    "test": "node --import ./test/isolate-simy-home.mjs --test --test-concurrency=2",
+    "test": "node --import ./test/isolate-simy-home.mjs --test --test-concurrency=1",
     "test:e2e:console": "node ./scripts/console-e2e.js",
     "test:e2e:work-activity": "node ./scripts/work-activity-e2e.js",
     "test:e2e:sqm-complete-loop": "node ./scripts/sqm-complete-loop-e2e.js",

package/src/agent.js

@@ -3107,6 +3107,7 @@ export async function startAgent({
           expected_evidence: [],
           required_checks: [],
           require_human_approval: input.require_human_approval === true,
+          independent_review_required: input.independent_review_required === true,
           must_not: [],
           attachments: await referenceLocalAttachmentPaths(input.attachmentPaths || []),
         };

package/src/cli-contract.js

@@ -14,7 +14,7 @@ import {
 } from "./durable-local-task-steps-contract.js";
 import { buildExecutionCapabilityContract } from "./execution-capability-contract.js";
 
-export const CLI_VERSION = "0.7.29";
+export const CLI_VERSION = "0.7.31";
 export const CLI_API_CONTRACT_VERSION = 10;
 
 export function narrativeImageCapabilityMetadata() {

package/src/cli-observability.js

@@ -7,7 +7,7 @@ import { execFile } from 'node:child_process';
 import { promisify } from 'node:util';
 import { webApiHeaders, webApiUrl } from './web-api.js';
 // Keep this leaf module package-safe: hooks load it before the full CLI contract.
-const CLI_VERSION = '0.7.29';
+const CLI_VERSION = '0.7.31';
 
 const STORE = 'cli-observability-state.json';
 const LEGACY_CONFIG = 'cli-observability.json';

package/src/codex-plugins/simy/.codex-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "simy",
   "version": "0.1.0",
-  "description": "SIMY quality and PR review, with automatic checkpoint tracking through enabled provider hooks.",
+  "description": "SIMY Auto Continue, quality checks and PR review through the original conversation's existing controls.",
   "author": {
     "name": "Specialist Doctors Inc.",
     "url": "https://github.com/SpecialistDoctors-Inc"
@@ -16,15 +16,17 @@
   "skills": "./skills/",
   "interface": {
     "displayName": "SIMY",
-    "shortDescription": "Quality and PR review.",
-    "longDescription": "Run explicitly requested quality checks and PR reviews. Enabled hooks automatically track eligible conversations from user prompts through checkpoints. Stops, permission waits and opt-outs are preserved. The local Delivery skill remains retired; independently managed work uses the CLI Agentic Loop.",
+    "shortDescription": "Continue, check and review.",
+    "longDescription": "Ask SIMY to continue unfinished work in the original conversation through the running CLI app's existing Auto Continue controller, or request quality checks and PR reviews. Read the same real work state and next action as the app. Saved delegation is not execution proof. Stops, permission waits and opt-outs are preserved. Retired local delivery agents stay retired.",
     "developerName": "Specialist Doctors Inc.",
     "category": "Developer Tools",
     "capabilities": [
+      "Auto Continue",
       "Quality",
       "Review"
     ],
     "defaultPrompt": [
+      "Enable SIMY Auto Continue for this conversation and show its actual progress.",
       "Run the SIMY SQM Loop for the current thread.",
       "Review the current pull request with SIMY."
     ],

package/src/codex-plugins/simy/hooks/acceptance-policy.mjs

@@ -20,3 +20,10 @@ export function effectiveAcceptanceCriteria(managed) {
     return eligible ? { ...criterion, check: { type: 'semantic' }, originalCheck: criterion.check } : criterion;
   });
 }
+
+export function onlyManualAcceptancePending(managed) {
+  const verified = managed?.verified || {};
+  const pending = effectiveAcceptanceCriteria(managed).filter(criterion => criterion.check?.type === 'manual'
+    ? verified[criterion.id]?.source !== 'user' : !Object.hasOwn(verified, criterion.id));
+  return pending.length > 0 && pending.every(criterion => criterion.check?.type === 'manual');
+}