Skip to content
TYPO3Dev Companion

It answers before it guesses

A local server for the three audiences that do TYPO3 work. Every answer names the source it came from and the versions it holds for.

Install

It runs as a subprocess of your client. It needs PHP 8.2 or newer and nothing else — no daemon, no database, and no network unless a tool asks docs.typo3.org for a page.

bash 
# standalone: clone, install once
$ composer install
✓ published 9 task skills to .agents/skills

Settings

What a project has to set, and what it can leave alone. One entry per value: the name it is written under, the facts a machine checks, and a sentence saying what happens either way.

siteTitle required #
type
string
default
"TYPO3"
The name the site calls itself — the browser tab, the header lockup, and the fallback for any page that declares no title of its own.
cache.lifetime #
type
int
default
86400
unit
seconds
How long a rendered page may be served from cache. 0 disables caching, which is a development setting and never a production one.

Before you file an issue

The three questions the install step raises, kept on the page it raises them on. Folded, because a reader who has none of them is reading the next section instead of scrolling past three answers.

The client starts it and nothing is registered
The binary ran with a PHP older than 8.2 and exited before it announced anything. Run php -v as the client runs it — a shell and a desktop client rarely have the same one.
It answers, but not about my installation
Nothing was found to read. The server takes the project root as an argument and falls back to bundled knowledge without it, which is the answer you are getting.
A tool says the installation would not boot
It read the package registry from disk instead, and the answer says so rather than looking complete: every declared package is in it and none of the dynamically registered ones.

Where to go next

The signpost at the end of an overview, and the one place a card wall belongs: four ways on, read down as one block rather than compared as four things.

The tool surface

Every tool the server registers, what it is asked and what it answers with.

Read the reference

The bundled knowledge

What ships inside the package, how it is versioned, and what it is not.

See what is in it

Writing a task skill

The shape of a skill, and the one rule that decides whether it earns a file.

Write one

What is written down

Decisions, requirements and the records that hold them together.

Read the records