連接 Actionway。
繼續使用你熟悉的 AI 產品。

Set up Actionway for Codex.

1. Confirm the host OS is macOS or Linux. If it differs, stop and ask me to copy the matching setup message from the website.
2. If your shell is sandboxed with network restrictions (e.g. the Claude Code sandbox), first allow `registry.npmjs.org`, `actionway.ai`, and `*.actionway.ai` — for Claude Code add them to `sandbox.network.allowedDomains` in settings. Blocked egress surfaces as a bare 403. Ask me before editing settings files.
3. Install by running `curl -fsSL https://actionway.ai/install.sh | sh`. The installer checks Node.js 20+ (installing the LTS if missing), installs the Actionway CLI, and runs its doctor check. Do not use `sudo` without my approval. If doctor reports failed checks, report them and stop; do not change npm registry, proxy, CA, PATH, or shell profile without my approval.
4. Before authentication, inspect the browser tools actually available in this Agent session. Prefer a user-visible, interactive built-in browser that can open external HTTPS sites and let the user sign in; a local-preview-only panel or headless browser is not enough. Do not infer this capability from the Agent name or existing login cookies. If that browser is available and the user has not chosen the system browser, run `actionway --agent-host=codex init --install-session-id=<install-session-id> --no-browser`, keep the command running, and use the documented browser tool to open and show the exact complete activation URL printed by the CLI in this conversation. `--no-browser` only stops the CLI from launching the system browser; it does not prohibit the Agent from opening the built-in browser. Request any required browser/site permission; do not bypass a refusal. A clean browser profile or a sign-in page is not a browser failure. This also applies to Claude Code's desktop Browser pane when available. Tell the user to register or sign in and explicitly approve access there. Keep the same browser profile through sign-in and approval; do not copy cookies from another browser, enter credentials, or approve on the user's behalf. If no suitable built-in browser is available, or the user explicitly chose the system browser before init, run `actionway --agent-host=codex init --install-session-id=<install-session-id>` without `--no-browser` and let the CLI open the operating system's default browser. If it cannot open a visible browser, give the user the exact activation link; do not claim it opened. If the selected built-in browser actually cannot open the page or browser incompatibility blocks sign-in, or the user explicitly asks to switch, explain the reason and open that same complete activation URL once in the system browser (or give the user the link if opening is unavailable). Only do this while the original init is still pending: keep its process, device code and install session ID unchanged; never restart init/login to switch browsers. Do not switch merely because saved logins are absent, or work around a permission refusal. Use one active authentication browser at a time, not both speculatively. The user handles credentials and the explicit access decision; never ask them to paste credentials into the conversation. For this Agent, keep the same `--agent-host` declaration immediately after `actionway` on every future Actionway command. Keep the original init process running and retain any execution-session handle. Use the execution tool's wait/resume facility in bounded waits (e.g. 10–30 seconds) until that same process exits; an empty wait result is not a CLI timeout. Give brief progress updates while the user signs in, without ending the task or asking them to say "done". Do not start another init/login while it is pending. Stop on user cancellation or terminal denial, expiry, timeout, or error; do not retry authentication automatically. If the host cannot retain/resume execution or requires a user reply to continue, explicitly report setup as pending and request only the action needed to resume.
5. Proceed only after the original init exits successfully with `initialized: true` and `authenticated: true`; a browser success page is not sufficient. Read the `skill` block in the init output and copy the complete directory at its local `source` path. Install it at `~/.codex/skills/actionway` so Codex can load it in future sessions.
6. Replace an existing destination only if it is an earlier Actionway Skill; otherwise ask me first.
7. Verify setup with `actionway --agent-host=codex whoami`, then give me three short examples from `actionway --agent-host=codex --help`. Automatically finish Skill installation and verification without another user message. Report setup complete only after the complete Skill directory is installed and whoami reports `logged_in: true` for the intended environment. For an Agent without Skill support, explicitly report CLI-only setup instead. If Skill copying or verification fails, report the unfinished step; do not restart authentication or reinstall the CLI just to retry a Skill copy. Show examples without executing them; setup does not authorize billable calls.