OpenClaw
Connect OpenClaw in Settings → OpenClaw on desktop or mobile. Then choose OpenClaw in desktop’s Start thread → Run on, or mobile’s Jot actions → Hand off → OpenClaw. Progress, results, and follow-up messages stay in a saved Sharick thread.
Prepare your gateway
Section titled “Prepare your gateway”Enable hooks on your OpenClaw gateway and expose a hooks URL reachable from the device running Sharick. HTTPS is recommended. Mobile also accepts HTTP after confirmation, for example over a trusted NetBird connection. HTTP itself does not encrypt your hooks token or work; keep the device connected to the trusted VPN or network whenever you use it. Sharick cannot verify that your VPN is on. Desktop requires HTTPS.
Use a dedicated hooks token, not your Gateway login token.
Merge these settings into your existing configuration, choosing your actual agent ID and a long random token:
{ "hooks": { "enabled": true, "token": "<dedicated-random-hook-token>", "path": "/hooks", "allowedAgentIds": ["main"], "allowRequestSessionKey": true, "allowedSessionKeyPrefixes": ["sharick:", "hook:"] }}Sharick uses sessionMode: "persistent" and a stable sharick:<thread ID>
session key. This requires an OpenClaw version supporting persistent hook
sessions. See the official hooks configuration.
Apply gateway changes through your deployment’s normal configuration procedure.
Connect and verify reporting
Section titled “Connect and verify reporting”- Enter your hooks base URL, for example
https://gateway.example/hooks, the hooks token, and optionally an agent ID. Sharick appends/agent. - Save the connection and allow OpenClaw to report to Sharick. On mobile, an HTTP URL first shows Use HTTP for this connection? with its exact address. Cancel keeps your draft; Use HTTP saves consent for that endpoint on this device. Changing the address requires confirmation again.
- On mobile, Sharick first checks the hooks URL and token with an empty request that does not launch an agent. A failed check stops setup before creating a reporting thread.
- Sharick sends a small verification task. OpenClaw reads the scoped reporting endpoint and sends a real completion callback. Setup stays incomplete until that callback arrives.
The gateway token is stored on the current device: encrypted storage in Sharick Desktop and secure device storage on mobile. It is not uploaded to Sharick’s server. Configure each device separately. When using a different gateway URL, enter its token again.
Work that starts in OpenClaw
Section titled “Work that starts in OpenClaw”OpenClaw can bring an existing job to you without a Sharick-created handoff. Its question arrives in Inbox with a phone push. The Inbox card offers concrete answer buttons; open the conversation to review the proposal and history, write your own direction, or pause the work. All replies stay linked to the original OpenClaw session.
On the OpenClaw machine, use a Sharick CLI build containing openclaw commands:
-
Run
sharick loginwith a dedicated MCP API key from Sharick settings (todo:writescope, or the first-party full-access key). Authentication is a one-time setup; never paste the key into a task or question file. -
Keep the receiver running on that machine:
Terminal window sharick openclaw watch \--hooks-url http://127.0.0.1:18789/hooks \--hooks-token-file /path/to/dedicated-hooks-token.txt -
Have OpenClaw write its actual proposal as a JSON file:
{"title": "SEO: review query evidence before rewriting","message": "The SEO report shows impressions without clicks, but the sample is small.","question": {"summary": "Review query evidence before changing the page?","proposal": "Compare the page's query data across non-overlapping periods before choosing a rewrite.","options": [{"id": "review", "label": "Review evidence", "message": "Review query evidence first. Do not publish changes."},{"id": "defer", "label": "Defer changes", "message": "Defer SEO changes for now."}]}} -
From that existing OpenClaw job, invoke:
Terminal window sharick openclaw ask --session hook:existing-seo-job \--agent minibossclaw --file proposal.jsonUse the job’s actual existing session key and agent ID. A key does not create permission: the gateway’s caller-key and prefix policy must permit that session. Do not invent a new key to bypass a rejected request.
askpins the receiver to the default local hooks address above; if this gateway uses another address, pass the same--hooks-urlto both commands.
The CLI prints the resulting Inbox URL and the actual push outcome. no_device
or failed means the Inbox item exists but a phone push was not delivered.
Retry the same ask after a lost response; the saved capability and initial
request reconcile against the existing work, without another question or nudge.
Use a new session for genuinely different work, not for a follow-up.
Your mobile answer is saved on Sharick’s server. The receiver polls it and sends it through OpenClaw hooks with the exact original session key; OpenClaw reports progress or another question directly to Sharick. The phone does not need a local hooks token or a live NetBird connection to answer this work. The receiver and gateway must be running. If they are offline, the answer remains saved and shows waiting for OpenClaw. No AI intermediary relays results or interprets the person’s choice.
Pause is cooperative. Sharick shows Pause requested until OpenClaw reports that it has stopped. A hooks request cannot forcibly interrupt an already running tool; it may wait for the current turn. Resume work is explicit. A delayed completion cannot overwrite a newer pause. Session details → Revoke Sharick access disconnects reporting and the receiver for that work; it does not stop the OpenClaw process.
After uncertain delivery, the receiver does not silently replay the direction. The conversation exposes Retry delivery with confirmation, preserving the original message and recording the person’s retry separately. Gateway replay protection is bounded; inspect history before retrying an uncertain action.
Read, report, correct
Section titled “Read, report, correct”sharick openclaw status --session <key> --agent <id> reads the saved thread,
including its actual work state, current human message ID, question, and
history. sharick openclaw report --session <key> --agent <id> --file report.json
appends a report using the saved, scoped capability. The receiver also gives
OpenClaw direct GET/POST instructions in the continued session.
A report references the human message being answered (or the external opening
event before any human reply). To withdraw an obsolete question, append
kind: "correction_appended" with withdrawQuestionEventPublicId and a reason
in message. The proposal and correction remain in history; its nudge is
quieted. A new question is a new event in the same work, not a new session.
The authenticated bootstrap endpoint is POST /api/v1/mcp/openclaw/work.
The scoped thread endpoints are GET/POST .../report and GET/POST .../receiver.
The receiver claims each direction before invoking hooks. These are transport
adapters over the same actor-attributed thread events and human answer/control
contract; adding a future local AI runtime need not create a different Inbox
or conversation experience.
Continue the same work on mobile
Section titled “Continue the same work on mobile”Name each connection in Settings and choose a default for new work. Existing work keeps its original gateway and agent, even after you change the default. A second device asks you to restore that original connection; it does not send an earlier conversation to its own default.
Today, Inbox, Todo, and linked Briefing items open the same saved conversation. When OpenClaw offers alternatives, short answer buttons appear alongside the question. Use Review wording or give direction for the proposal, sources, history, or a custom reply. Asking a question leaves the decision open. In the conversation, you can explicitly make your message an answer, or keep it as discussion.
The reporting protocol accepts an optional question object on kind: "question":
{ "summary": "A short, self-contained question and recommendation.", "proposal": "The draft wording to review in the conversation.", "options": [ { "id": "keep", "label": "Keep pending", "message": "Keep pricing explicitly pending." }, { "id": "omit", "label": "Leave pricing out", "message": "Omit pricing for now." } ]}Supply two to five alternatives. Human answers reference the question event;
ordinary messages do not settle it. Read earlier pages from the same scoped
report endpoint with ?beforeSequence=<historyBeforeSequence> when a response
includes that cursor. Report against the specific human message you are
answering, so a delayed result cannot settle newer direction.
How reporting works
Section titled “How reporting works”Each thread gets a dedicated reporting capability. OpenClaw can read that thread and append progress, questions, results, or corrections; it does not receive your Sharick login or access to unrelated threads. The server stores only a hash of the capability. Treat the OpenClaw session history as private, because the task includes this scoped credential.
The handoff includes reporting instructions automatically. It does not require installing a skill or configuring a full-account MCP API key just to return results. Existing Sharick MCP workflows can still be configured separately when an agent needs broader tools; see the MCP guide.
Hook admission means the gateway accepted the request, not that work is done.
Only agent reports appear as progress or completion. deliver: false suppresses
OpenClaw’s external-channel announcement; it does not disable Sharick reporting.
Model and token usage are shown only when available, never inferred from admission.
Delivery and recovery
Section titled “Delivery and recovery”Sharick records each message before sending it and reserves its dispatch once. If a request times out, delivery is unconfirmed. Check the thread and gateway before deliberately sending another message. Sharick does not automatically redispatch an uncertain request when you reopen a thread.
- Rejected request: check the hooks token, agent allowlist, and persistent session settings.
- No reporting callback: ensure the OpenClaw agent can make HTTPS requests to Sharick and follows the reporting instructions. A gateway admission response alone cannot verify reporting.
- Read from another device: threads are saved to your Sharick account. Connect that device to your gateway before sending follow-up messages.
Reporting credentials can be revoked through the authenticated
DELETE /api/v1/openclaw/threads/<thread ID>/credential endpoint. Revocation
is recorded in the thread history and stops further use of those credentials.