Skip to content

docs: document the notte stack project commands - #45

Open
giordano-lucas wants to merge 2 commits into
mainfrom
docs/notte-stack-reference
Open

docs: document the notte stack project commands#45
giordano-lucas wants to merge 2 commits into
mainfrom
docs/notte-stack-reference

Conversation

@giordano-lucas

Copy link
Copy Markdown
Member

Why

notte-cli's check-skills guard requires every user-facing command to be mentioned in plugins/notte/skills/. nottelabs/notte-cli#75 adds nine commands under notte stack, so that PR cannot go green until this one lands — the guard reads this repository's main branch, not the submodule pin.

What

One reference, notte-browser/references/stack-projects.md, alongside the existing function-management.md and friends.

It covers when to reach for notte stack over notte functions — the former manages a directory of functions with shared code, the latter one function by id — plus the layout and its single discovery rule, the command surface, notte.toml, environments, secrets, what check enforces, and the constructs the bundler rejects with the fix for each.

Two things worth flagging

  • notte stack needs uv, which also supplies the Python the runtime uses. Nothing else in the CLI does, so it is called out rather than assumed.
  • self_healing only works for functions an agent built. It resumes the thread that created them, and a CLI deploy has none — the API refuses it with a 400. Documented so nobody sets it and wonders why.

Both are the kind of thing otherwise found by hitting them.

🤖 Generated with Claude Code

giordano-lucas and others added 2 commits September 1, 2026 16:40
notte-cli's check-skills guard requires every user-facing command to be
mentioned here, and `notte stack` adds nine that were not.

Covers the layout and the one discovery rule, the command surface, the
typical flow, notte.toml including the metadata that deploy now applies on
every run, environments, secrets, what check enforces, and the constructs the
bundler rejects with the fix for each.

Notes two things that are otherwise found the hard way: uv is required for
these commands and supplies the Python itself, and self_healing only works for
functions an agent built, since it resumes the thread that created them and a
CLI deploy has none.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@greptile-apps

greptile-apps Bot commented Sep 3, 2026

Copy link
Copy Markdown

Greptile Summary

This documentation-only PR adds a reference for managing multi-function projects with notte stack and expands the existing Function guidance with source-download commands.

  • Documents stack layout, discovery, configuration, environments, secrets, validation, deployment, and bundler restrictions.
  • Adds current and version-specific notte functions download examples.
  • Adds no automated validation for the newly documented command surface.

Confidence Score: 4/5

The PR appears safe to merge, with the non-blocking concern that its newly documented command surface has no automated drift detection.

The changes are limited to documentation, and no concrete incorrect command or runtime contract was established; the remaining actionable concern is the absence of tests for the expanded CLI guidance.

Files Needing Attention: plugins/notte/skills/notte-browser/references/stack-projects.md

Important Files Changed

Filename Overview
plugins/notte/skills/notte-browser/references/stack-projects.md Adds the complete stack-project reference, but no automated check accompanies its extensive CLI command and configuration contracts.
plugins/notte/skills/notte-browser/references/function-management.md Replaces manual URL downloading with concise latest-version and version-specific CLI download examples.
plugins/notte/skills/notte-browser/SKILL.md Adds the function-download command to the primary Function command catalog.

Fix all with Greploop Fix All in Claude Code

Prompt To Fix All With AI
### Issue 1
plugins/notte/skills/notte-browser/references/stack-projects.md:55-65
**Command docs lack validation**

The new command surface has no automated documentation or command-surface validation test, so later CLI changes can leave agents executing stale or unsupported syntax without CI detecting the drift.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Reviews (1): Last reviewed commit: "docs: document the notte stack project c..." | Re-trigger Greptile

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant