René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Get deepnote sync and publish ready for the editor and agents","articleBody":"The VS Code / Cursor extension (deepnote/vscode-deepnote) and coding agents are going to drive `deepnote sync` and `deepnote publish`. Today they can't do that reliably. This issue collects the CLI changes they need.\n\n## Current state\n- `@deepnote/cli@0.8.0` on npm has no `publish` or `static-site access`; they exist only on `main`. `deepnote streamlit publish` is still in #466.\n- `publish` and `static-site access` output only human-readable text. `-q` hides the URL (`packages/cli/src/commands/publish.ts:327-347`).\n- `publish` needs `--project-id`. No command lists projects or returns their ids.\n- `sync` always covers every project in the workspace. There is no per-project filter.\n- Only `sync`, `run` and `schedule` read `.env`, each from its own folder. `publish`, `static-site access` and `streamlit publish` don't read it.\n- Nothing creates a starter app. A static app is just a folder that `publish` uploads.\n\n## Tasks\n- [ ] Release `@deepnote/cli`, `@deepnote/cloud` and `@deepnote/mcp` with `publish`, `static-site access` and `streamlit publish`, once #466 merges.\n- [ ] Add `-o json` to `publish`, `static-site access` and `streamlit publish`:\n  - Static: `{url, projectId, apiAccess, filesUploaded, pruned}`\n  - Streamlit: `{appId, url, status}`\n  - A divergence (\"Deepnote changed these files since the last sync\") gets its own error code or exit code, so callers can offer \"sync first\" or \"force\".\n- [ ] Look up `DEEPNOTE_TOKEN` in `.env` the same way for every command that needs a token: the command's folder first, then parent folders up to the sync root. The missing-token error should tell the user to add `DEEPNOTE_TOKEN` to `.env`.\n- [ ] Make `--project-id` optional for `publish` and `streamlit publish`. When the folder is inside a synced project, take the id from `.deepnote-sync.json` or from the `.deepnote` file's project id.\n- [ ] Add `deepnote projects list -o json`, returning id, name, folder path and URL.\n- [ ] Add `deepnote sync --project \u003cid|path>` to sync a single project. This is separate from the speed-up in #535.\n- [ ] Add `deepnote app init \u003cdir> --template static|ts|streamlit`, which creates a starter app. The TS template builds to a folder that `publish` can upload. The extension and agents will share these templates.\n- [ ] Update `skills/deepnote/references/{cli-publish,cli-sync,apps}.md` and `docs/`, as AGENTS.md requires.\n\n## Done when\nAn agent with no TTY and only a `.env` file can do all of this without running `--help` or parsing text:\n1. Create an app.\n2. Sync one project.\n3. Publish the app.\n4. Get the URL back as JSON.\n\nUnblocks the vscode-deepnote work on agent setup and on sync and publish buttons.\n\n🤖 Generated with [Claude Code](https://claude.com/claude-code)\n","author":{"url":"https://github.com/jamesbhobbs","@type":"Person","name":"jamesbhobbs"},"datePublished":"2026-09-28T12:17:59Z","url":"https://github.com/deepnote/deepnote/issues/543"}