@vibes.diy/prompts 14.3.167 → 14.3.168

package/cli-footer.md

@@ -4,16 +4,17 @@
 
 1. Run `npx vibes-diy system` to get the coding rules
 2. Write `App.jsx` following the rules above
-3. Run `npx vibes-diy push` to deploy — prints a live HTTPS URL
+3. Run `npx vibes-diy push --vibe <handle>/<app-slug>` to deploy — prints the handle/app-slug it used and a live HTTPS URL
 4. Edit and push again to iterate
 
 ### Other Commands
 
-- `npx vibes-diy push --access gated` — deploy so anyone can view but only members write (`open` is the default, `private` is members-only)
-- `npx vibes-diy push --access private` — deploy for you and the members you invite, and nobody else
-- `npx vibes-diy push --app-slug other-name` — deploy to a different app slug instead of the directory name
-- `npx vibes-diy unpublish <vibe>` — take a deployed vibe down (reversible; code and data are kept)
-- `npx vibes-diy publish <vibe>` — make it live again, or promote a `--mode dev` draft to production
+- Name the app as `handle/app-slug` on every command (a bare slug falls back to your default handle — fine at a terminal, never in a script or agent)
+- `npx vibes-diy push --vibe <handle>/<app-slug> --access gated` — deploy so anyone can view but only members write (`open` is the default, `private` is members-only)
+- `npx vibes-diy push --vibe <handle>/<app-slug> --access private` — deploy for you and the members you invite, and nobody else
+- `npx vibes-diy push --handle <handle> --app-slug other-name` — deploy to a different app slug instead of the directory name
+- `npx vibes-diy unpublish <handle>/<app-slug>` — take a deployed vibe down (reversible; code and data are kept)
+- `npx vibes-diy publish <handle>/<app-slug>` — make it live again, or promote a `--mode dev` draft to production
 - `npx vibes-diy login` — authenticate this device (run once before first push)
 - `npx vibes-diy mcp --help` — start an MCP server for AI agent data access (Claude Desktop / Cowork)
 - `npx vibes-diy help` — show all available commands

package/llms/github.md

@@ -65,7 +65,7 @@ own, and `:write` includes `:read`:
 | `contents:read` | read its code | `/contents`, `/readme`, `/git`, `/commits`, `/compare`, `/branches`, `/tags`, `/releases` (GET) |
 | `contents:write` | read and change its code | the same paths, writing; merging a pull request |
 | `pull_requests:read` | read its pull requests | `/pulls`, `/pulls/{n}`, `/pulls/{n}/files`, `/reviews`, `/comments` (GET) |
-| `pull_requests:write` | review, comment on, edit and close pull requests | reviews, review comments, requested reviewers, comments and labels on a pull request's conversation, and editing a pull request (title, body, base, open or closed) |
+| `pull_requests:write` | review, comment on, edit and close pull requests | reviews, review comments, requested reviewers, comments and labels on a pull request's conversation, and editing a pull request (title, body, base, open or closed); updating a pull request's branch also needs `contents:write` |
 | `issues:read` | read its issues | `/issues`, `/issues/{n}`, `/labels` (GET) |
 | `issues:write` | label and comment on issues | opening, editing, labelling, assigning and commenting on issues |
 | `statuses:read` | read whether commits are passing | `/commits/{ref}/status`, `/commits/{ref}/statuses` |
@@ -144,7 +144,8 @@ call needs a permission `config.github.permissions` leaves out — add it),
 `permission_not_consented` (declared, and the person connected the repo before
 the app asked for it — show them **Connect again** with the
 `buildGithubInstallUrl()` link), `permission_not_granted` (GitHub itself
-refused: the vibes.diy GitHub App does not hold that permission yet),
+refused: the vibes.diy GitHub App does not hold that permission yet on that
+account, which the account owner accepts on GitHub),
 `unsupported_method`, `body_too_large`, `upstream_error`. Branch on
 `err.reason` and tell the person which one it was.
 
@@ -603,7 +604,8 @@ channel.
   declaration answers `permission_not_declared`; one the person has not agreed
   to yet answers `permission_not_consented`, and pressing Connect again shows
   them the new list. `permission_not_granted` means GitHub itself refused,
-  because the vibes.diy GitHub App does not hold that permission. Record the
+  because the vibes.diy GitHub App does not hold that permission on that
+  account yet. Record the
   reason on the person's record and show it, so they see exactly what happened
   and what one tap fixes it.
 - **Each app gets the repos chosen for it.** The person ticks repos per app, and

package/mcp-footer.md

@@ -5,7 +5,8 @@ Tools: vibes_list_apps, vibes_list_databases, vibes_get, vibes_put, vibes_delete
 `vibes_generate` builds a brand-new vibe from a text prompt and deploys it live —
 it takes minutes and spends your AI credits. The new app is separate from the
 `--app-slug` this server was started with; the data tools keep pointing at that
-one.
+one. Always pass `--handle` with `--app-slug`: without it the server binds to
+whatever the account's default handle is when it starts.
 
 `vibes_add_seed_data` adds the live version's sample data (its `seed.json`) to the
 app's databases, keeping your edits; `vibes_remove_seed_data` takes it out again.
@@ -36,7 +37,7 @@ Add to .mcp.json in your project root:
   "mcpServers": {
     "my-vibe": {
       "command": "npx",
-      "args": ["vibes-diy", "mcp"]
+      "args": ["vibes-diy", "mcp", "--app-slug", "APP", "--handle", "USER"]
     }
   }
 }
@@ -44,4 +45,4 @@ Add to .mcp.json in your project root:
 
 ### Test interactively
 
-    npx @modelcontextprotocol/inspector npx vibes-diy mcp --app-slug APP
+    npx @modelcontextprotocol/inspector npx vibes-diy mcp --app-slug APP --handle USER

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vibes.diy/prompts",
-  "version": "14.3.167",
+  "version": "14.3.168",
   "type": "module",
   "main": "./index.js",
   "exports": {
@@ -39,10 +39,10 @@
   "license": "Apache-2.0",
   "dependencies": {
     "@adviser/cement": "~0.5.34",
-    "@vibes.diy/api-types": "14.3.167",
-    "@vibes.diy/call-ai-v2": "14.3.167",
-    "@vibes.diy/identity": "14.3.167",
-    "@vibes.diy/use-vibes-types": "14.3.167",
+    "@vibes.diy/api-types": "14.3.168",
+    "@vibes.diy/call-ai-v2": "14.3.168",
+    "@vibes.diy/identity": "14.3.168",
+    "@vibes.diy/use-vibes-types": "14.3.168",
     "arktype": "~2.2.6",
     "json-schema-faker": "~0.6.3"
   },