PicoClaw widens setup across auth, language and routing

sipeed/picoclaw PR #926 is the inspected primary source: “feat(auth): add Anthropic OAuth setup-token login.” The related records below were inspected as supporting context rather than independent confirmation.

The facts

- sipeed/picoclaw PR #926 was created 2026-02-28T18:40:12Z and was closed at inspection; its title is “feat(auth): add Anthropic OAuth setup-token login.” - sipeed/picoclaw issue #3272 was created 2026-07-20T15:47:50Z and was closed at inspection; its title is “Feature: Add Japanese localization to PicoClaw WebUI and Launcher.” - sipeed/picoclaw issue #3298 was created 2026-07-26T13:15:41Z and was open at inspection; its title is “[Feature] Add AI Router as an OpenAI-compatible provider preset.” - The repository reported 29828 stars, 51 open issues, default branch main, and last push 2026-07-30T18:32:36Z. - The latest tagged-release baseline checked was nightly published 2026-07-02T01:26:53Z.

What changed

sipeed/picoclaw PR #926 reports: Summary Add support for Anthropic OAuth setup tokens (sk-ant-oat01-*) as an alternative to API keys via new --setup-token flag and interactive login menu Integrate Anthropic usage endpoint to display 5-hour and 7-day utilization in auth status Add streaming support for OAuth tokens (required by Anthropic API) and normalize model IDs (dots → hyphens) for API compatibility Remove.env.example to avoid templating secrets Test plan [ ] Run picoclaw auth login -p anthropic and verify interactive menu shows setup token + API key options [ ] Run picoclaw auth login -p anthropic --setup-token and verify it accepts valid sk-ant-oat01-* tokens [ ] Verify invalid/short tokens are rejected with clear error messages [ ] Run picoclaw auth status with an OAuth credential and verify usage percentages display [ ] Verify chat works end-to-end with an OAuth setup token (streaming path) [ ] Run existing tests: go test

sipeed/picoclaw issue #3272 reports: Summary Please add Japanese (ja / ja-JP) localization to PicoClaw and the WebUI Launcher. The main PicoClaw documentation already provides a Japanese translation, but the WebUI Launcher currently does not offer Japanese as a UI language. Current state web/frontend uses i18next and has locale resources for English, Simplified Chinese, Portuguese (Brazil), Bengali, and Czech. The language selector on the main app header exposes those languages, but the launcher login/setup screens currently expose only English and Simplified Chinese. web/backend/i18n.go currently supports only English and Chinese for launcher/system-tray strings. The launcher CLI help currently documents only en and zh. The repository includes Japanese project documentation, so Japanese users are already an intended audience. Requested changes 1. Add a complete Japanese frontend resource (for example, web/frontend/src/i18n/locales/ja.json). 2. Add Japanese to every relevant language selector, including launcher login/setup and the authenticated WebUI. 3. Add Japanese dayjs locale handling and

sipeed/picoclaw issue #3298 reports: Affiliation disclosure: I maintain AI Router and would contribute this on its behalf. The Goal / Use Case PicoClaw can already connect to AI Router through the generic openai provider by setting api_base to https://api.ai-router.dev/v1. That works, but users cannot select a named AI Router preset or receive the endpoint automatically in the Web UI. The current provider catalog already has the right reusable behavior: OpenAI-compatible transport, Bearer authentication, and authenticated GET {api_base}/models discovery. This proposal should therefore remain a small preset, not a new protocol implementation. Proposed Solution Would maintainers prefer either of these scopes? 1. Add a first-class ai-router catalog entry with the fixed default API base, SupportsFetch: true, and the existing OpenAI-compatible HTTP transport. Do not hard-code a model inventory; retain fetched and manually entered model IDs. 2. If another named provider is not wanted, add only a factual custom-provider example to

Why it matters

Configuration breadth is product work only if each path has a real ownership and failure contract. A closed OAuth proposal and localization request are evidence of direction, not proof that every package or deployment includes them. The operator test is whether authority, persisted state and the visible outcome still describe the same event after retries, restarts or delegation.

Current

The primary record was closed when captured on 2026-08-07. The release baseline was nightly published 2026-07-02T01:26:53Z. Repository metadata, pull requests, issues, release records, Google News discovery, Hacker News discovery, Lobsters, Metamesh and the rendered ClawCharts row were checked. ClawCharts selected the subject; it did not prove the claim.

Evidence

The primary URL is https://github.com/sipeed/picoclaw/pull/926. Supporting records are https://github.com/sipeed/picoclaw/issues/3272 and https://github.com/sipeed/picoclaw/issues/3298. Source bodies, timestamps and states are preserved in the daily evidence bundle. Test counts, reproductions and deployment observations remain attributed to their authors unless explicitly identified as independently rerun.

Source boundary

Open work is described as open, closed work as closed, and operator reports as reports. A pull request is evidence of proposed or reviewed direction, not proof of a shipped release. Search residue, package mirrors and historically published source spines were excluded.

Operator take

Check the merged commit and package baseline before advertising availability; test OAuth callback failure, locale fallback and provider-model discovery as separate lanes. Preserve a before-state receipt, make the smallest reversible change, and verify the original failure independently after intervention.

Caveat

Public project records are mutable. Status, scope and evidence can change after publication. This brief records the inspected state and does not authorize changes to a reader’s deployment.

Source inspected; source state, environment and release boundary remain explicit.