mulmoclaude 1.7.2 → 1.9.0

package/README.md

@@ -51,6 +51,26 @@ npx mulmoclaude --help                       # Full flag list
 
 Each boolean flag mirrors an environment variable, so `--disable-sandbox` and `DISABLE_SANDBOX=1` do the same thing. `--help` lists the rest: `--disable-macos-reminders` (skip the macOS Reminder notification sink) plus the `--journal-force-run`, `--chat-index-force-run`, and `--persist-tool-calls` debugging toggles.
 
+## Start from an icon (macOS / Windows)
+
+```
+npx mulmoclaude create-shortcut              # macOS: MulmoClaude.app / Windows: MulmoClaude.lnk
+npx mulmoclaude create-shortcut --dir ~/Desktop
+npx mulmoclaude create-shortcut --yes        # Skip the confirmation prompt
+```
+
+Creates a real app bundle on macOS (no Electron — an `Info.plist` and a shell stub) in `/Applications`, or `~/Applications` when that is not writable. On Windows it creates a Start Menu shortcut pointing at a `.vbs` stub run through `wscript.exe`, so no console window appears; the launcher's files live under `%LOCALAPPDATA%\MulmoClaude`. Double-clicking it:
+
+1. reuses an already-running MulmoClaude by just opening the browser,
+2. checks Node.js, `npx`, and Claude Code, and explains in your system language what to do when one is missing,
+3. shows a progress page while `npx mulmoclaude@latest` starts, then switches to the app.
+
+A GUI launch gets none of your shell's `PATH`, so the bundle asks your login shell for it before looking for anything — this is why a version manager (nodebrew / nvm / asdf / Volta) still works from the icon.
+
+It also starts the server from your home directory rather than the `/` macOS hands a GUI app, so the `.env` it loads is `~/.env`.
+
+The launcher writes `~/Library/Logs/MulmoClaude/launcher.log`. The bundle carries its own copy of the launcher code, so re-run the command after upgrading. Windows is not supported yet.
+
 ## How it works
 
 The npm package ships with the pre-built client (Vite) and the server source — TypeScript, executed directly via `tsx`. No cloning, no build step for end users: `npx` downloads the package and starts the Express server.
@@ -129,7 +149,7 @@ Recommended: ≥ 32 characters of random data (shorter values trigger a startup
 - **Auto memory** — the agent maintains a typed memory layout (`conversations/memory/<type>/<topic>.md`) and reads it ambient-style.
 - **Web Push on task finish** — enable in Settings → Notifications to get a push on your phone when the answer to a question you asked is ready, even with the browser closed. Requires the RemoteHost connection + a registered device (see [`docs/remote-host.md`](https://github.com/receptron/mulmoclaude/blob/main/docs/remote-host.md#web-push-on-task-finish-2086)).
 - **Google (Calendar / Tasks / Drive)** — link your Google account in Settings → Plugins → Google and consent in the browser; no Google Cloud setup needed. The agent then gets a `google` tool covering the full round trip — list, create, edit and delete calendar events and tasks (including putting a completed task back on the list), plus the Drive files it creates — and the phone remote can trigger the same commands.
-- **Google Calendar ↔ collection sync** — a collection can mirror one of your calendars and keep itself current: the first sync starts as soon as you ask for the collection, an hourly pass follows, and a Sync button forces one. It calls the Calendar API directly rather than routing the events through the agent, so keeping it fresh costs no tokens. A **Push to Google** button beside it sends the other way, creating events for records you added and updating ones you edited — it never deletes, and it skips anything edited on both sides rather than picking a winner. Push before you sync: a pull overwrites a locally edited record as soon as Google reports a change to that event. **The refresh token stays on your machine** (`~/.config/mulmo/`) — the sign-in service applies the OAuth client secret Google requires and keeps nothing. Prefer your own OAuth client? Drop a *desktop-app* client JSON in `~/.secrets/` and the whole flow stays local (see [`docs/remote-host.md`](https://github.com/receptron/mulmoclaude/blob/main/docs/remote-host.md)).
+- **Google Calendar ↔ collection sync** — a collection can mirror one of your calendars and keep itself current: the first sync starts as soon as you ask for the collection, an hourly pass follows, and a Sync button forces one. It calls the Calendar API directly rather than routing the events through the agent, so keeping it fresh costs no tokens. A **Push to Google** button beside it sends the other way, creating events for records you added and updating ones you edited — it never deletes, and it skips anything edited on both sides rather than picking a winner. Ask for **two-way sync** and the collection pushes on the same schedule it pulls on, as one cycle, so there is no button to forget; a record the push could not send is then left alone by the pull instead of being overwritten. Without it the pull is automatic and the push is a button, so push before you sync — a pull overwrites a locally edited record as soon as Google reports a change to that event. Event **notes and location** travel in both directions alongside the title, times and colour. **The refresh token stays on your machine** (`~/.config/mulmo/`) — the sign-in service applies the OAuth client secret Google requires and keeps nothing. Prefer your own OAuth client? Drop a *desktop-app* client JSON in `~/.secrets/` and the whole flow stays local (see [`docs/remote-host.md`](https://github.com/receptron/mulmoclaude/blob/main/docs/remote-host.md)).
 
 ## Plugin authoring (`--dev-plugin`)
 
@@ -143,6 +163,13 @@ Server-side `definePlugin` factory edits still require a launcher restart (Node
 - Architecture, scripts, and the publish flow live in `docs/developer.md` of the repo.
 - Publish flow for this package: see `bin/prepare-dist.js` header comment plus `.claude/skills/publish-mulmoclaude/SKILL.md`.
 
+## Updates
+
+New releases and features are announced on X, **in Japanese**.
+
+- [Singularity Society (@SingularitySoci)](https://x.com/SingularitySoci) — release and feature announcements
+- [Satoshi Nakajima (@snakajima)](https://x.com/snakajima) — MulmoClaude's owner
+
 ## Related projects
 
 This launcher is published by [Receptron](https://github.com/receptron), who also build MulmoTerminal below.

package/bin/mulmoclaude.js

@@ -100,6 +100,11 @@ const args = process.argv.slice(2);
 if (args.includes("--help") || args.includes("-h")) {
   console.log(`
 Usage: npx mulmoclaude [options]
+       npx mulmoclaude create-shortcut [--dir <path>] [--yes]
+
+Commands:
+  create-shortcut      Create a clickable MulmoClaude.app (macOS) so the
+                       app can be started without a terminal
 
 Options:
   --port <number>      Server port (default: ${DEFAULT_PORT})
@@ -121,6 +126,15 @@ if (args.includes("--version")) {
   process.exit(0);
 }
 
+// Generates the clickable app bundle and exits — it never starts a
+// server. Imported lazily because the icon builder pulls in `sharp`,
+// which nothing else on the launch path needs.
+if (args[0] === "create-shortcut") {
+  const { runCreateShortcut } = await import("../server/utils/launcher/create-shortcut.mjs");
+  const { version } = require(join(PKG_DIR, "package.json"));
+  process.exit(await runCreateShortcut(args.slice(1), { version }));
+}
+
 const { requestedPort, portExplicit } = parsePortArg();
 const noOpen = args.includes("--no-open");
 const devPluginPaths = resolveDevPluginPaths();