@tday-com/mcp 0.4.6 → 0.4.8

package/README.md

@@ -44,7 +44,7 @@ One server, `tday`. Each time it starts it asks tday what your account can use,
 
 - `demo_features` / `demo_docs` - your features (newest first) and the docs pages that still need a demo.
 - `demo_guide` - how tday wants a demo made.
-- `demo_app_notes` - how your apps were started before. A note that is new on this machine, or changed since you approved it, is shown to you before your agent may use it.
+- `demo_app_notes` / `demo_app_note_save` - how your apps were started before, kept in your repo's `.tday` folder (`.tday/apps/<app>.md`). Your agent writes them on your machine and never commits; commit `.tday/` to share them with your team's agents. Nothing in them is sent to tday.
 - `demo_check` - before recording, a read-only look at where the demo's data would live and what it could reach.
 - `demo_start`, then `demo_beat` for each narrated line.
 - `demo_review` - the review page. Your agent uploads with `demo_upload` only after you confirm with the code it shows you.
@@ -109,7 +109,7 @@ Run any of them with `npx -y @tday-com/mcp@latest <command>`.
 }
 ```
 
-`--prefix` keeps npx from reading the repo's `package.json`: the agent starts the server in your repo, and a repo whose `overrides` pin one of this package's dependencies would otherwise fail the start (`EOVERRIDE`). `install` writes this entry pinned to its own version, so your agent never picks up a new release on its own. Run `install` again to update. Pin the version in an entry you write by hand too. If you add the entry yourself, run `npx -y @tday-com/mcp@latest install` once afterwards, so the browser sign-in can link the server to your tday account.
+`--prefix` keeps npx from reading the repo's `package.json`: the agent starts the server in your repo, and a repo whose `overrides` pin one of this package's dependencies would otherwise fail the start (`EOVERRIDE`). `install` writes this entry pinned to its own version. When tday releases a newer version, the server re-pins its own entries to it as it starts (only to a version tday names and that npm shows tday's release workflow published; Codex's TOML is never edited), so your agent runs it from its next start; `TDAY_MCP_AUTO_UPDATE=0` keeps the version you have. By hand: `npx --prefix ~ -y @tday-com/mcp@latest update`. Pin the version in an entry you write by hand too: an `@latest` entry is never rewritten. If you add the entry yourself, run `npx -y @tday-com/mcp@latest install` once afterwards, so the browser sign-in can link the server to your tday account.
 
 For Gemini CLI, put the same `mcpServers.tday` object in `~/.gemini/settings.json`. VS Code's user `mcp.json` keys entries by `servers` and names the transport: `{ "servers": { "tday": { "type": "stdio", "command": "npx", "args": ["--prefix", "<your home directory>", "-y", "@tday-com/mcp@<version>", "serve"] } } }`.