Choosing the agent that answers
- Pick your copy of Claude Code from a list instead of typing a path. Settings ▸ AI now shows every copy it finds on this Mac, each with the version it reports, so two of them can be told apart. Choose… is still there for one installed somewhere unusual, and choosing one now updates the model list above it straight away — the hint has always said it would, and until now you had to close Settings and open it again.
- And MojoPad says plainly that it runs Claude Code and not any agent. The setting took any path and checked only that the file could be run, so naming a different agent put that agent in the model chooser still labeled Claude Code (your own agent) — and MojoPad went on to start it and hand it your question. It could never have worked. Everything MojoPad allows or refuses a run — which tools it may use, which folders it may see, that it may not reach the tools you have connected — is written in Claude Code’s own instructions, and another program takes none of them. You would have been promised a boundary and given a sentence. MojoPad now asks what a program is before offering it, and quotes back what it said for itself when the answer is no.
- A folder counted as a program. Every folder on a Mac can technically be run, so naming one was accepted, reported in Settings as found, and then failed every question with an error that blamed Claude Code. It is now recognized as a folder and said so.
- “Not installed” was the answer to three different problems. A copy that was never installed, one moved after you chose it, and a program that turns out to be something else all got the same sentence — including in the diagnostics report you would send to show what was wrong. Each now says which it is, and where MojoPad looked.
- A warning about your own agent stopped appearing over and over. With your own agent chosen, work MojoPad starts by itself — the quiet thinking that happens while you are elsewhere — cannot use it, because that work stays on this Mac by design. Rather than doing what it has always promised and quietly using a model here instead, it stopped and told you, every time, about work you had never asked for. It now uses a model on this Mac, which is what it would have done if you had never touched the chooser.
- A research run can be stopped in the moment after you start it. A run was only stoppable once it was properly under way, so pressing Stop in the first seconds found nothing to stop, said nothing had stopped, and the run started anyway.
- Settings no longer pauses while it asks your agent what it can do, and a run that has been given one of your connected tools now says, in its own steps, that it is held inside its boundaries by one instruction rather than two. It still may not write files or run commands, and may still use only the tools named — but that is a change you should hear about rather than infer.
- A wiki set to stay on this Mac now says everything a research run would send — your question, and any pages you pin to it. It named only the question before.
Papers a script collects
- “Did not arrive” now says which kind of nothing it was. Collecting the papers a report cites, every way a fetch could fail arrived as the same empty answer: a publisher refusing automated downloads, a paper that was never there, a file over the size limit, a question you had declined yourself. Worse, the commonest case carried no explanation at all — when a site simply answers no, that answer reached your script with nothing attached. There is now
mojo.fetchResultbesidefetchData: the same request through the same door and the same permission, saying whether anything arrived, what the site answered, which kind of failure it was in a word your script can act on, and where the answer actually came from after redirects — which is how you tell a publisher’s landing page from the file you asked for.fetchDatais unchanged, so scripts you have already written keep working. - And the reason is written into the run’s log. It has always been described that way and it went to the status line instead, which clears after a few seconds — so a script fetching twenty papers overwrote it nineteen times and a run you stepped away from left no trace. A file that could not be kept is written down the same way: a paper that arrived and could not be filed used to look exactly like one that never arrived.
Asking permission
- Twenty papers no longer means twenty questions stacked on top of each other. Fetching from several sites at once raised a question for each, all at the same moment, each answered against an answer the one before it had not finished saving — so you answered the same site twice. Questions for the same site now wait for each other, and the second usually has nothing left to ask. Different publishers still ask separately, because they are separate decisions.
- A site you were sent to says it was a redirect. When one site handed you on to another, MojoPad asked about the new one with Remember this already ticked — so a site could arrange a permanent permission for somewhere you never chose, just by pointing at it. The question now says the site was not the one your script asked for, and the box starts empty.
Moving pages
- Moving pages from the Pages palette can be taken back. The Undo beside a move arrived last release on the row menu only; the bulk bar in the Pages palette had its own Move that offered none, which is the control most likely to be moving twenty pages at once. Both go the same way now, and each page returns to the folder it came from at the position it held.
Getting things into MojoPad
- “Add to MojoPad” is in the Finder. Right-click a file — a PDF, a Markdown note, an image — and MojoPad is in the Services menu alongside everything else that can take it. It arrives as a page, and MojoPad says what came in and where it went, rather than leaving you to go and look.
- And you can say which wiki things land in. With more than one wiki open, Settings ▸ Web Clipper ▸ Add to decides where a file added this way goes: a wiki you name, or ask each time.
- A script started from the Plugin menu shows up while it is running, not only once it has finished.
Writing plugins
- The scripting reference documents what a script can actually do. Two calls that exist were written down nowhere —
mojo.readData, which hands back the bytes of a file page, andmojo.exportFolder, which writes files into a folder you choose. The calls that reach the tools you have connected were missing too, which read as though a plugin could not reach them; it always could. - And one sentence in it was simply wrong. Under What a script cannot do it said no call opens a connection — in the same chapter that documents fetching from the web. That is the sentence somebody careful would have relied on. It now says what is true: a script reaches the pages of the wiki you have open; it reaches the web only where you have allowed it, one site at a time; and it writes outside the wiki only into a folder you choose, every time.