well_get_browser_task

io.github.WellApp-ai/well-mcp · Verify this server

Read where the person's newest browser task of this conversation stands: in their own Chrome (queued, running, waiting for them, or ended) or in the Well browser (running or ended), since when, and its last step. It hands nothing off and changes nothing. Call it when the person's latest message only asks where a browser task already handed off in this conversation stands ("so, the certificate?", "where is it at?", "alors, cette attestation ?", "où en est ma tâche ?"), with no ask to run it again. An ask to run it again or to retry it hands the task off again, never here. Never decide from the conversation that a task waits, runs or is done: only this result knows. Well sends the task's status itself, as a fixed line: follow the result's `message`. When the result has no `task_status`, no browser task was handed off from this conversation. When the token authorizes one workspace, call this directly — no workspace call is needed first. When it authorizes several, this read will not guess which one you mean: pass `workspace_id` on the call.