# MojoPad 1.69.0 Released (Big Fixes) (User Requests) (New Features)

**URL:** <https://mojopad.discourse.group/t/mojopad-1-69-0-released-big-fixes-user-requests-new-features/139>\
**Category:** MojoPad\
**Created:** [August 21, 2026, 8:46pm UTC](https://mojopad.discourse.group/t/mojopad-1-69-0-released-big-fixes-user-requests-new-features/139 "2026-08-21T20:46:32Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mark\_Busse](https://yyz1.discourse-cdn.com/flex003/user_avatar/mojopad.discourse.group/mark_busse/32/43_2.png) [@Mark\_Busse](https://mojopad.discourse.group/u/Mark_Busse)\
**Post date:** [August 21, 2026, 8:46pm UTC](https://mojopad.discourse.group/t/mojopad-1-69-0-released-big-fixes-user-requests-new-features/139/1 "2026-08-21T20:46:33Z")

</div>

**Ask a question in words; MojoPad works out which tool answers it**

- **A property can now hold a question rather than a wiring diagram.** Connect a server and a property could already reach it — but only by naming one tool and one of its fields, and deciding forever which value went where. That is exactly right when you know the tool you want: an address goes to a scraper, an identifier goes to a lookup. It stops being right the moment what you have is a _question_. Ask a search tool to scrape and it will tell you your question is not a valid address, which is true and no help at all.
- **So pick ✦ Let AI choose the tool, and write the question.** _“Show me the five most recent headlines on that site, with a summary of each and a link to its source.”_ A model reads the page, decides which of that server’s tools answers it, writes what to send, reads what comes back, and answers in your property — reaching for a second tool if the first one did not settle it. When it gets something wrong the server says so and it tries again, which is the part you cannot do by hand: by hand, a wrong argument is just an error message.
- **You decide what it may ever reach for, and it is two separate yeses.** In Settings, beside each server, you tick the tools a model may choose among. Nothing is ticked to begin with, and nothing ticked means it may not choose at all. Then the first time a wiki wants to use them, MojoPad asks — and names the tools in the question, because “allow AI to use this server?” is not something anybody can answer. A wiki that arrives from somebody else can ask for this and get nowhere: the list it would need is not in the file.
- **The answer says what produced it.** Not a model name but the server and the tool it actually ran, kept with the value. When a fact has been assembled by something that made its own choices, what it reached for is part of the fact.
- **It works across a whole kind** , from the kind’s own page, and says how many pages it will ask about and what it will send before it does anything. There is a full walkthrough in the manual, from ticking the tools to the finished answer.

**Text you can read, whatever theme you are in**

- **Paste from another app and the words are legible.** A note pasted onto a dark theme could arrive as black text on a dark page — present, selectable, and impossible to read. The cause was never in what you copied: most apps send no colour at all, and the black is added on the way in, taken from the light background of wherever it came from. MojoPad now looks at the colour a piece of text will actually be seen against, and drops the ones that cannot be read there. Black goes on a dark theme and stays on a light one; white does the reverse.
- **Anything you chose survives.** A red, a blue, a highlight — those are decisions and they are kept whatever theme you are in, and text sitting on a highlight is judged against the highlight rather than against the page. Only the greys and blacks that another app supplies by default are dropped, because those are the ones nobody picked.
- **Emailed pages get the same treatment.** Mail is written on white paper almost without exception, so a message arriving in a dark wiki had the same problem, and now does not.

**[[Page Name]] is a link where you write it**

- **Write a link that way and you see a link.** MojoPad has understood `[[Page Name]]` on the way _out_ for a long time — in a compiled paper, a PDF, a published site. On the page itself the brackets simply sat there, and the only reason any of it lit up was the auto-linker noticing the name between them. So a contents page written as a list of `[[Section]]` read as a page of punctuation. It now resolves where you are reading it: `[[Page Name]]`, `[[Page Name|call it this]]`, and a link to a particular block all become real links you can click.
- **Your source is untouched — exactly as you typed it.** On a Markdown page the brackets stay put, including a heading or a block marker inside them: the link is how the page is _drawn_, not what it stores. A name that is not a page keeps its brackets too, so a broken link is easy to spot and anybody writing _about_ the syntax keeps their example. Plain-text and formatted pages are left alone entirely — the first because its whole promise is that the text is the text, the second because it stores the link itself. Use the Link button or ⌘L on those, which is what they keep anyway.
- **And a link made this way no longer disappears.** Link Selection to Page, the Relates-to strip and Link to a Row all write that form into a Markdown page, and the page picker — ⌘L, or typing `[[` — made a link that the next save quietly turned back into plain words. Those links now survive being saved, which they should have done all along.
- **Wiki links count as links.** One written by hand now carries the same weight in the graph and in Backlinks as one made with the Link button, instead of being scored as a passing mention.

**Smaller things**

- **A server that stops answering no longer hangs the question.** Asking a connected server what it can do had no time limit, so one that had quietly stopped responding could leave a ✦ spinning with nothing to show and no way to try again short of restarting. It gives up and says so now, and the connection is dropped rather than handed out again.
- **Panels stop offering settings that belong to something you are no longer using.** Controls that were meant to disappear sometimes stayed on screen, depending on how they had been styled — a small thing that made a panel read as though it were asking two questions at once.