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 no longer holds, it changes rather than stands.
On your machine
The five that decide if this installs at all. An open one closes the last, so the list stays a list.
Does it send anything anywhere?
One path leaves the machine and it draws as the exception: a
read from docs.typo3.org, only on a request
for a documentation page. Everything else gets its answer from bundled
knowledge, from files on disk, or from the installation.
Does it write to my installation?
No. Every source is a read, and the package files get a read
rather than a run. 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 ones
registered at run time, and the answer states that rather than looks complete.
Which TYPO3 versions does it work with?
Every version still in support, and one release past it. A version past its end of life stands named in the result rather than refused. So an installation nobody has updated yet still gets an answer.
Running 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 gets a request 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 live installation fall back to the package files. They say what that leaves out.
What happens to a wrong answer I report?
A person reads it. Where the answer came from bundled
knowledge the fix ships with the next release and the changelog names
that release.
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.