Skip to content

docs: warn about read_cell stale-output lag in jupyter-mcp guidance #16

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
KadenMc merged 1 commit into from
May 10, 2026
Merged

docs: warn about read_cell stale-output lag in jupyter-mcp guidance #16

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions src/aexp/vendor/limina/AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -174,6 +174,11 @@ tools over git-based round-trips for notebook work:
- **DO NOT** use `notebook_run-all-cells` — exposed but currently
returns 404 (asymmetric upstream bug). Loop `execute_cell` over
indices for multi-cell runs.
- **`read_cell` / `read_notebook` outputs lag live state.** After an
`execute_cell`, the cached output (and execution count) returned by
`read_cell` may still reflect the *prior* run. Trust `execute_cell`'s
return value to verify the most-recent execution; don't round-trip
through `read_cell` to check.
- For full setup details, troubleshooting, and the investigation log,
see `docs/setup/jupyter-mcp.md`.

Expand Down
Loading