daily-twitter-briefing browser reroute

Date: 2026-04-23 Scope: remediation step 1 only, daily-twitter-briefing

What changed

Removed the skill instruction that routed X/Twitter browsing through profile="user".
Replaced it with the managed OpenClaw browser path: host browser, managed openclaw profile.
Added an explicit reason in the skill: this workflow is timeline reading, not a live personal-browser workflow, so it should avoid the signed-in Chrome attach path and the resulting consent prompts.
Added a guardrail: if X is not logged into the managed browser yet, stop and ask Pete to sign in manually there. Do not fall back to profile="user".

The next scheduled twitter briefing should use the managed browser lane instead of Pete's signed-in Chrome session.
That should remove the avoidable Chrome remote-debugging approval prompts tied to this skill.

Open /Users/vinny/.openclaw/workspace/skills/daily-twitter-briefing/SKILL.md and confirm there is no profile="user" instruction.
On the next scheduled run, confirm the browser call targets the managed browser path, either by:

no profile="user" in the run transcript for this skill, and
browser activity landing in the orange-tinted OpenClaw browser instead of Pete's normal Chrome session.

If the run stops on X login, that is expected for a first managed-browser pass. Pete should sign in manually in the OpenClaw browser once, then rerun or wait for the next cron window.