Native coding agents on real websites. Safari setup and privacy.
Contact the developer through GitHub Issues
Use this support channel for installation questions, bug reports, and feature requests. The developer replies in the issue thread. A free GitHub account is required to send a request. Read existing questions and replies without an account.
Please include:
Do not include API keys, tokens, private code, or personal information.
In build 5 or later, open the AgentOnWeb macOS app and click Try Interactive Demo. This opens a populated, interactive offline demo without DSH, an account, a model subscription, or an API key. The Safari toolbar menu provides the same demo. Sample conversations and tool results are clearly labeled; the presentation controls and scratchpad are interactive.
Enable AgentOnWeb in Safari Settings → Extensions. Open an ordinary HTTP or HTTPS website and allow access for that website. Reload a page that was already open before enabling the extension. Safari internal pages, the Start Page, and protected pages cannot display an injected workspace.
In build 5 or later, the toolbar opens a menu with Try interactive demo, Show / hide on this website, and Allow local workspace access. The containing app also has the demo button, independent of Safari permissions.
For DSH, live agent features require DeepSeek Harness running on the same Mac with the AgentOnWeb plugin. Follow the complete setup guide. Provider credentials are configured in DSH, not in the extension. Provider usage may incur charges.
If no runtime is found, check that dsh web is running and restart it after installing the plugin. Allow access to localhost and 127.0.0.1 from the toolbar menu. Approve the connection in DSH. Follow the local-session prompts when returning to your website.
Setup guide · Privacy policy · Source and releases
Use Codex or Claude Code on your websites with macOS + Chrome. Install the Chrome store extension and follow the one-command setup guide. The installer configures the terminal service and Chrome connection, detects installed CLIs on PATH, and asks which Codex/Claude Code/Pi notification integrations to install.
If Local terminal is missing, check aow service status or keep aow terminal running. Use aow service open to reopen private pairing/connection management. Type cd and your CLI commands inside the browser shell. All connected views can type into the same shell; focus its view to control terminal dimensions. If the shell exited, use + to create another one. Refreshing a view preserves a running shell; a host or computer restart ends live shell processes.
Reinstalling a running service does not load new host code immediately. Finish your terminal work before stopping and reinstalling the service. Never include the private setup URL or raw service logs in public issues.
On macOS + Chrome, aow setup configures the service and native pairing, and shows a terminal menu for the Codex/Claude Code/Pi integrations detected on PATH. Select all, comma-separated numbers/names, or 0 to skip integrations. For unattended setup use --agents codex,claude, --agents all or --agents none; missing CLIs are always skipped. Review AgentOnWeb hooks in your CLI’s /hooks, then launch a new Codex or Claude Code session in a new host terminal for session notifications. If an older host is running, finish terminal work, run aow service uninstall, then aow setup. Before removing the npm package run aow uninstall. See setup, upgrade and uninstall.