ReachWeaver 0.10.0 release notes
Released on 2026-10-18.
Run a work and a family account on one network without posting to the wrong one, and get sign-up details ready for networks you are not on yet, all offline and local. 3 new commands (104 in all, none removed): profile, account-route and account-kit, plus a --persona option on draft, check and approve. No change to approval, dry-run, emergency-stop, credential or reconciliation rules, and no new live adapter.
Upgrade notes. Nothing changes for existing users: --persona, the profile file and the optional "persona" field in accounts.json are all opt-in, and without them every command behaves as in 0.9.0. Update the package with pipx upgrade reachweaver and the plugin through /plugin.
- Personas and the wrong-account guard. Keep a private profile (
reachweaver profile --init, fileconfig/profile.json, mode 600, ignored by git) with your personas (for exampleworkandfamily) and one username per network and persona. Say which persona a post is for (--persona workondraft,check,approve, orpreferences.default_persona) and ReachWeaver refuses an account that belongs to another persona and names the account or username to switch to;account-routeanswers “which account should I use” directly. An account’s persona comes from an optional"persona"field inaccounts.jsonor from matching its username against the profile; when neither tells, it refuses and says how to fix that. The guard only adds refusals: the approval hash, dry-run, emergency stop and credentials are untouched, an unreadable profile fails closed, and with no profile and no flag behaviour is unchanged. See personas and the account kit. reachweaver account-kit: sign-up details for accounts you create yourself, behind one approval (offline). From the profile it builds one plan for the platforms you name: display name, username candidates (or the nickname for platforms that use one), e-mail, phone, birth date, bio and website, limited to what each platform’s form may ask for, in the form’s language (Simplified Chinese, Japanese, Korean or English), with a short form-label word list and the steps that stay with you. Missing facts come back as questions (--questions). The plan ends with a sha256; passing its first 12 characters as--approve-planwith--out NEW_DIRwrites a new private folder with oneSIGNUP.mdper platform, which is the single approval for all of them. It does not create accounts, fill forms, drive a browser, see passwords, CAPTCHAs or codes, or check whether a username is free (browser-assist decision). The flag containsapprove, so in Claude Code the project’s deny rule keeps that approval with you. Per-platform form expectations are labelledexpectedand are not verified platform rules. The profile refuses passwords, tokens, one-time and recovery codes and identity-document numbers. New filereachweaver/signup_registry.json;config/profile.example.jsonis a synthetic example.