Questions
The ones that arrive by email every week, answered here so they do not have to be. Every answer holds for the releases named in it; where one does not hold any more it is changed rather than left standing.
What it does to your machine
The five that decide whether this can be installed at all. Opening one closes the last, so the list stays a list.
Does it send anything anywhere?
One path leaves the machine and it is drawn as the exception: a
read from docs.typo3.org, made only when a tool
was asked for a documentation page. Everything else is answered from bundled
knowledge, from files on disk, or from the installation.
Does it write to my installation?
No. Every source is read, and the package files are read rather
than executed. The one thing written anywhere is what you ask for
explicitly — the task skills, into .agents/skills.
Which releases does it answer for?
12.4, 13.4, 14.3 and main from bundled knowledge; changelog
lookups go down to 7.0. Anything read from your installation follows that
installation, whatever it runs.
What happens when the installation will not boot?
The tool reads the package registry from disk instead and says so
in the result. It returns every declared entry and none of the dynamically
registered ones, and the answer states that rather than looking complete.
Which TYPO3 versions does it work with?
Every version still receiving support, and one release past it. A version that has reached its end of life is named in the result rather than refused, so an installation nobody has updated yet still gets an answer.
What running it costs
What does it need installed?
PHP 8.2 or newer, and a TYPO3 project it can read. No daemon, no
database of its own, and no network unless a tool is asked for a
documentation page.
How long does an answer take?
Around 240 ms from bundled knowledge. Anything that needs the
installation booted takes as long as booting it, which is why the tools that
can answer without it say so.
Can it run in CI?
Yes, and it answers less there: nothing boots, so the tools that need a running installation fall back to reading package files and say what that leaves out.
What happens to a wrong answer I report?
It is read by a person. Where the answer came from bundled
knowledge the fix ships with the next release and the changelog names the
release it was fixed in.
Not here?
The server answers questions about TYPO3 itself, which is what it is for. Questions about the server go to the repository, and an answer that was wrong goes to the form that collects those.
An answer here is not version-bound the way a tool's is
These hold for the releases they name and are maintained by hand.
What a tool returns carries its own binding, and that binding is the
one to trust where the two disagree.