we-love-jupyter-notebook
Local notebook editor + scoped AI agent (Blocking & Trusted modes), backend-enforced edit boundary, diff review, loopback-only.
A local FastAPI + React editor for working on Jupyter notebooks with scoped AI agent editing. You open a local .ipynb file (or a project folder), edit and execute cells, and save in place. Each agent turn has a scope: in Blocking mode the agent may only rewrite the source of cells you explicitly mark editable; in Trusted mode the whole notebook is editable and the agent may add, delete, reorder, and retype cells. Either way the backend validates and applies (or rejects) every change — the agent never mutates your notebook directly — and every change is reviewable as a diff and undoable.
⚡ Use this agent from Claude Code (or any agent)
Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.
Use the MeshKore agent at https://meshkore.com/agent/aglyx3-we-love-jupyter-notebook — read its card at https://meshkore.com/agent/aglyx3-we-love-jupyter-notebook/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
https://meshkore.com/agent/aglyx3-we-love-jupyter-notebookFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/aglyx3-we-love-jupyter-notebook/.well-known/agent.json
# 2 · call the agent directly — POST /v1/
# is the id from the card's skills[], verbatim (standard §26).
# We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }' Capabilities
Do you own we-love-jupyter-notebook?
This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.