Skip to content

v1.2.0 — Google without the setup

Choose a tag to compare

View all tags
@isamu isamu released this 17 Jul 08:55
v1.2.0
580f79c

Highlights

Link Google with no Cloud setup (#2131)

Linking now takes a click and a consent screen — no Google Cloud project, no client JSON. Google demands a client secret at its token endpoint even under PKCE, which is what used to dead-end users at "OAuth クライアント認証情報が見つかりません". The mulmoserver broker applies that secret on your behalf.

It is stateless: it stores no token and no authorization code. Its callback hands the code — never a token — back to your machine, which performs the exchange itself. Refresh tokens still live only on your machine (~/.config/mulmo/), so there is no central store to breach.

  • Bring your own OAuth client? A desktop client JSON in ~/.secrets/ still wins and keeps the whole flow local — self-hosters lose nothing.
  • Existing links keep working: tokens record which client minted them, and renewals use the right one.
  • Hardening: the broker URL must be HTTPS unless loopback, and the consent URL it returns must be https://accounts.google.com before any browser opens.

Google Tasks and Drive tools (#2115)

The google tool gains seven kinds — list task lists, list / add / complete tasks, and list / create / read Drive files. Drive is drive.file-scoped: the app only ever sees files it created, never your wider Drive.

These shipped in packages earlier today but could not reach npx mulmoclaude@1.1.1 users — a 0.x caret range does not cross a minor, so the launcher never resolved them. This release is what actually delivers them.

Host-neutral link guidance (#2128)

The unlinked-state guidance named MulmoClaude-only flows, misdirecting MulmoTerminal users (the plugin runs on both hosts). Wording is now host-neutral; each host's own help carries the specific steps.

📦 npm: mulmoclaude@1.2.0

Full Changelog

See CHANGELOG.md for the complete list.

Assets 2
Loading