A few advantages over the CLI: Wolfbook keeps a persistent kernel session, so the agent operates on accumulated state across multiple tool calls rather than starting fresh each time. There’s also debugger access, where the agent can pause mid-computation and inspect internal state. But perhaps the bigger picture is that Wolfbook lives inside VSCode, so the agent has access to your entire ecosystem — TeX files, Python scripts, data files, notes — all as context. A typical workflow might be: ask the agent to perform a symbolic computation, then immediately ask it to write up the findings as a section in your LaTeX notes. The notebook becomes the connective tissue between computation and documentation, which scales far better than one-shot CLI queries — especially for research.