NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Packagist, #1720 most downloaded on Packagist
A reliable and powerful command line interface for TYPO3 CMS
Latest stable
v9.0.1
Last release 4 months ago
07 Jul 2026
Release timing varies
gaps range from 5 weeks to 10 months
Nearly every release is documented
notes for 58 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
12 years old
159 releases · first in 2014
Drag across the ruler to compare, or tap a release to open it.
Repeatable upgrade wizards are now not marked done after execution
The full change log can be examined on Github The extension can be found at the TER release page.
Registering commands via Configuration/Console/Commands.php is deprecated. Instead the file Configuration/Commands.php should be used to register comm…
Code is now marked as compatible and tested with PHP 7.3
Instead of limiting the number of commands, specifically hiding commands that cannot run because TYPO3 is not set up yet, now all registered commands are shown. When a command is executed and fails a helpful error message is shown, to hint that TYPO3 is not set up yet.
As a "side effect" command autocompletion for all commands will always work, even when TYPO3 misses its configuration files.
Documentation rendering has now been adapted to benefit from the new infrastructure, which means documentation for the master branch will also be available.
TYPO3 Console is also available as TYPO3 extension for users not installing TYPO3 with Composer. The extension was built automatically once a new version was tagged, which meant that intermediate versions couldn't easily be used. To support the new documentation rendering infrastructure, the current state (tags but also all branches) will be available in a separate (read only) repository, which is also automatically updated on every change in the main repository.
install:setup command.upgrade:* commands have been fixed. There is still a pending bug that is not fixed with this release, but especially composer users should not be affected by this.frontend:request is now to processed, just like it should be.Configuration/Console/Commands.php is deprecated. Instead the file Configuration/Commands.php should be used to register commands, which is official TYPO3 API since TYPO3 8.7.The full change log can be examined on Github The extension can be found at the TER release page.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
A new setup step is added that optionally adds a web server config file (.htaccess or web.config) for Apache or Microsoft IIS to document root. By def
install:setupinstall:setup in description of this commanddatabase:updateschemaupgrade:all and upgrade:wizard was fixed that prevented certain wizards to be executed in TYPO3 9.5cache:flush --force now works with TYPO3 9.5database:updateschema now also works when cache tables do not exist, but extensions require database caches early in the bootstrapThe full change log can be examined on Github The extension can be found at the TER release page.
Fix an issue with sub-processes when PHP outputs error messages
The full change log can be examined on Github The extension can be found at the TER release page.
Fix extension installation for non composer mode with TYPO3 9.4
The full change log can be examined on Github The extension can be found at the TER release page.
Bootstrap fix for non composer mode with TYPO3 9.4
The full change log can be examined on Github The extension can be found at the TER release page.
The full change log can be examined on Github The extension can be found at the TER release page.
The full change log can be examined on Github The extension can be found at the TER release page.
Fix compatibility layer for non composer mode
The full change log can be examined on Github The extension can be found at the TER release page.
The option --exclude-tables for database:export is deprecated. Instead of specifying a comma separated list of tables to be excluded, the new option -…
database:export command now allows specifying excluding tables with wildcards. E.g. to exclude all cache tables you can use: typo3cms database:export --exclude 'cf_*' --exclude 'cache_*' Thanks to @mbrodala and @Nemo64 for the support!typo3cms database:export -e 'cf_*' -e 'cache_*' to export without cache tablestypo3cms database:export --connection MyConnectionThanks to @marble, the documentation and command reference rendering is much nicer now and features better indexes.
The option --install-steps-config was added to allow to directly specify a configuration file to be used for the installer
--exclude-tables for database:export is deprecated. Instead of specifying a comma separated list of tables to be excluded, the new option --exclude should be used multiple times: typo3cms database:export --exclude 'cf_*' --exclude 'cache_*'The full change log can be examined on Github The extension can be found at the TER release page.
Passing it anyway will continue to work, but is deprecated.
The complete setup process has been rewritten from scratch. Most apparently the output is now more compact and looks nicer.
What you can also grasp from the terminal cast above, is that it is now possible to hand over all argument for the setup process as environment variables.
Here is the complete list of default environment variables:
TYPO3_INSTALL_DB_USERTYPO3_INSTALL_DB_PASSWORDTYPO3_INSTALL_DB_HOSTTYPO3_INSTALL_DB_PORTTYPO3_INSTALL_DB_UNIX_SOCKETTYPO3_INSTALL_DB_USE_EXISTINGTYPO3_INSTALL_DB_DBNAMETYPO3_INSTALL_ADMIN_USERTYPO3_INSTALL_ADMIN_PASSWORDTYPO3_INSTALL_SITE_NAMETYPO3_INSTALL_SITE_SETUP_TYPEJust like in previous versions, if you use the --no-interaction flag, only required arguments need to be set. For all optional arguments the default values will be used then.
Last but not least, the whole setup process is now defined in a Yaml file. This means adding new arguments or even completely new steps is a matter of changing configuration.
Overriding the default configuration file is possible by providing the path to your own file with the TYPO3_INSTALL_SETUP_STEPS environment variable. In this file you can decide to either import the default configuration and amend it to fit your needs (e.g. using different environment variables names or even hard code know values), or create a completely customized setup workflow, or even run different setup steps in different scenarios.
We are very much looking forward to what you are going to build with this feature.
CommandDispatcher::createFromComposerRun() API changed, so that the first Composer event argument is obsolete. Passing it anyway will continue to work, but is deprecated.The full change log can be examined on Github The extension can be found at the TER release page.
Fix TYPO3 dependency declaration in ext_emconf.php (only affects TYPO3 Extension, not the composer package)
The full change log can be examined on Github The extension can be found at the TER release page.
Fix bug with cache clearing in extension:activate command
extension:activate commandThe full change log can be examined on Github The extension can be found at the TER release page.
Add --json to configuration:set command This allows setting array values by providing a JSON string: typo3cms EXTCONF/lang/availableLanguages '["de",
--json to configuration:set command
This allows setting array values by providing a JSON string:
typo3cms EXTCONF/lang/availableLanguages '["de", "fr"]' --json
typo3cms configuration:set SYS/caching/cacheConfigurations/cache_pages/options '{"compression": true}' --json--opt for mysqldump in database:export commandbackend:createadmin commandThe full change log can be examined on Github The extension can be found at the TER release page.
Mark as compatible with TYPO3 9.2
The full change log can be examined on Github The extension can be found at the TER release page.
All commands can now be registered with:
All commands can now be registered with:
"command:name" => [
// Command configuration
]
This includes also commands from command controllers.
Run level, booting steps, replaces, aliases and vendor name are now part of this configuration. All these are optional with proper defaults in case they are missing.
Defaults are:
runLevel: full booting steps: none replaces: none aliases: none vendor name: package name (or extension key for TYPO3 extensions)
This allows to specify arbitrary aliases also for command controller commands. Even different command names would be possible.
This also means, that aliases can be added as well to command controller commands.
Old registration and command controllers still work, as their registration is migrated to the new format.
Because this migrated configuration is merged with existing new configuration, it is possible to just supply some command controller commands with aliases, while not having to register every single command.
The full change log can be examined on Github The extension can be found at the TER release page.
Fix TYPO3 compatibility declaration in ext_emconf.php
The full change log can be examined on Github The extension can be found at the TER release page.
TYPO3 Console is now compatible with TYPO3 9.1 and above. Compatibility with TYPO3 9.0 has been dropped. Users are advised to upgrade to TYPO3 9.1, or
The full change log can be examined on Github The extension can be found at the TER release page.
Fixes a bug in the installer, which called the last install step twice. This could lead to two root pages being created when setup type "site" was sel
The full change log can be examined on Github The extension can be found at the TER release page.
Output command method return values again, but make clear that this is deprecated functionality
typo3-console/composer-auto-setup, when trying to setup a TYPO3 instance within a composer install process.The full change log can be examined on Github The extension can be found at the TER release page.
Fixes an issue with class loading in non composer mode when extension is not activated in extension manager
The full change log can be examined on Github The extension can be found at the TER release page.
Includes a fix for typo3-console/composer-auto-setup to work again
typo3-console/composer-auto-setup to work againThe full change log can be examined on Github The extension can be found at the TER release page.
Functionality that has been deprecated before has been removed, most notably here: the dummy extension that was installed by default with composer is…
We're delighted to present the next generation of TYPO3 command line tooling. For TYPO3 Console 5.0 the complete application layer (how commands are found and executed) has been refactored to use Symfony Console.
This means TYPO3 Console 5.0 is faster, more consistent, more compatible and more future proof than ever before.
-h ahich shows the help for a command (e.g. use typo3cms cache:flush -h to see the help for the cache flush command)../typo3cms install:generatepackagestates, you can now also type ./typo3cms i:gen and Symfony will find
the right command for you as long there is only one matching command.-v-v[vv] option is now globally available to increase verbositytypo3 and typo3cms). Since TYPO3 Console 5 has become a complete replacement for the TYPO3 built in command line layer, only typo3cms is left.backend:createadmin was introduced, which allows to add admin users to a TYPO3 instancePHP_INI_PATH environment variable.And many more cleanups, streamlining in the code base as well as the "UI" to make interacting with and creating new commands a more pleasant experience.
The good news here is, that the majority of commands will work just like before! Nevertheless some things needed to be changed in a way that could break current workflows, scripts or commands.
The most important change is, that PHP 5 and TYPO3 7.6 will not be supported with TYPO3 Console 5. If you need these, you can still use version 4.9.x, which is still maintained and will receive bugfixes, but no new features any more.
install:setuptypo3 binary is not installed with Composer any more (you won't need it anyway when using TYPO3 Console)database:export now calls mysqldump with option --single-transaction. This means if you need a consistent state of the dump, make sure all your tables use InnoDB engine (not MyIsam).A few things are deprecated, which means they still work, but won't work any more in the next major release of TYPO3 Console.
E.g. arguments as options:
extension:activate --extension-keys foo,bar is deprecated. Use extension:activate foo,bar instead.
E.g. options as arguments:
cache:flush 1 is deprecated. Use cache:flush --force instead
extension:activate and extension:deactivate are deprecated when TYPO3 is Composer managed (Composer mode). Use install:generatepackagestates to generate the active list of extensions automatically from the composer installed extensions and then extension:setupactive to set all active extensions up in your TYPO3 instance.extension:removeinactive is deprecated. Only install the extensions you need, instead of installing the code and removing it afterwards.install:setup the option --non-interactive is deprecated. Use the global option --no-interaction insteadinstall:generatepackagestates the option --activate-default is deprecated for Composer managed TYPO3. Instead require the TYPO3 core extensions you need in your project using composer.scheduler:run the option --task-id is deprecated. Use --task instead.The full change log can be examined on Github The extension can be found at the TER release page.
This is just a minor maintenance release
This is just a minor maintenance release
The full change log can be examined on Github The extension can be found at the TER release page.
Fix bug in relation with helhum/typo3-composer-setup
The full change log can be examined on Github The extension can be found at the TER release page.
Mark as compatible with PHP 7.2
The full change log can be examined on Github The extension can be found at the TER release page.
Fix extension:dumpautoload command
extension:dumpautoload commandupgrade:all command, which caused it to fail with upgrade wizards that download and install extensionsThe full change log can be examined on Github The extension can be found at the TER release page.
Make extension:dumpautoload a low level command
extension:dumpautoload a low level commandThe full change log can be examined on Github The extension can be found at the TER release page.
Fix regression in cache:flush command when being executed low level
cache:flush command when being executed low leveldatabase:updateschemaThe full change log can be examined on Github The extension can be found at the TER release page.
This release marks the feature freeze of the 4.x branch of TYPO3 Console. All new features will only be implemented in the upcoming 5.x versions. Nece
This release marks the feature freeze of the 4.x branch of TYPO3 Console. All new features will only be implemented in the upcoming 5.x versions. Necessary bugfixes will be added to 4.9.x versions however.
--skip-extension-setup for install:setup command. This option is enabled by default in non composer setups. The installation finishes with all TYPO3 core extensions set up that are marked as required and as factory default. All local extensions are marked as inactive. Don't use this option in composer setups, when you want the setup to exactly reflect the defined state (all required core extensions active and all third party extensions are active).The full change log can be examined on Github The extension can be found at the TER release page.
Fix regression in cache:flush command
cache:flush commandThe full change log can be examined on Github The extension can be found at the TER release page.
Fix regression in install:generatepackagestates when in non composer mode
install:generatepackagestates when in non composer modeThe full change log can be examined on Github The extension can be found at the TER release page.
Tweak cache:flush and install:generatepackagestates commands to be graceful when extensions require a db connection in ext_tables.php or ext_localconf
cache:flush and install:generatepackagestates commands to be graceful when extensions require a db connection in ext_tables.php or ext_localconf.php which isn't supported by TYPO3 without calling private APIinstall:generatepackagestates to gracefully exclude third part extensions when requested, despite them having the required flag set in composer.jsonThe full change log can be examined on Github The extension can be found at the TER release page.
Deprecate auto generation of PackageStates.php file. This happened anyway only when an environment variable was set and was thus not really used in th…
cache:flush --files-only is now a lowlevel command and can be executed without TYPO3 being set up (configured DB connection).install:generatepackagestates now flushes file caches (as it might change extension list).install:setup when third party extensions are installed.The full change log can be examined on Github The extension can be found at the TER release page.
Support typo3/cms-composer-installers 1.4.x, if PHP 7 is available.
typo3/cms-composer-installers 1.4.x, if PHP 7 is available.frontend:request command, which lead to a wrong URL being requested.The full change log can be examined on Github The extension can be found at the TER release page.
Fixes two bugs in upgrade commands, which lead to a wrong PackageState.php to be written and upgrade process to fail.
The full change log can be examined on Github The extension can be found at the TER release page.
Fixes a bug with extensions that require cache tables when reading ext_tables.php. For details see: https://github.com/TYPO3-Console/TYPO3-Console/pul
The full change log can be examined on Github The extension can be found at the TER release page.
Fixed a critical bug related to cHash calculation from command line. You are affected when you use the scheduler:run command for Solr indexing.
The full change log can be examined on Github The extension can be found at the TER release page.
Minor bugfix and installer refinements
The full change log can be examined on Github The extension can be found at the TER release page.
Fix issue with cache clearing during install:setup
The full change log can be examined on Github The extension can be found at the TER release page.
Fixed an edge case in install:setup which caused the installation to fail when an extension did not specify dependencies to TYPO3 system extensions co
The full change log can be examined on Github The extension can be found at the TER release page.
Just a minor bugfix for TYPO3 setup
The full change log can be examined on Github The extension can be found at the TER release page.
Properly show verbose result list for extension:setup commands
The full change log can be examined on Github The extension can be found at the TER release page.
All upgrade commands now check if there are incompatible extensions and deactivates them before proceeding
extension:setup* commands now have a --verbose option to show more details what happensinstall:extensionsetupifpossible command, which can be used in composer scripts. In case TYPO3 is not properly set up, it gracefully exits with a notice, but if TYPO3 is set up, then first executes a database schema update and then sets up all extensions. This is e.g. very useful on first deploy on a new system where a database has no tables yet.configuration:showactive now has a --json switch to output the configuration path in a machine readable way as json string.configuration:show now correctly outputs the configurationAnd many more minor fixes…
The full change log can be examined on Github The extension can be found at the TER release page.
Workaround a bug in TYPO3 argument parsing
Full list of changes. TER release page
Fix Extension icon for display in TER
Full list of changes. TER release page
Full list of changes. TER release page
Full list of changes. TER release page
Introducing commands to perform a TYPO3 upgrade from the command line:
upgrade:list Shows a list of upgrade steps that need to be performedupgrade:all Performs all necessary upgrade steps in one goupgrade:wizard Performs a single upgrade step, with the possibility to enforce (--force) the execution in case it was already marked as done beforehandThe full change log can be examined on Github The extension can be found at the TER release page.
extension:setupactive is now idempotent. No action is taken for an extension if not required
extension:setupactive is now idempotent. No action is taken for an extension if not requiredextension:setupactiveFull list of changes. TER release page
The TYPO3 install process has been refactored and is now more robust
The full change log can be examined on Github The extension can be found at the TER release page.
The database:updateschema command can now be executed when the configured database is completely empty, which makes this a great command for an initia
database:updateschema command can now be executed when the configured database is completely empty, which makes this a great command for an initial deploymentbackend:lock and backend:unlock are now idempotent. This means you can use them to ensure desired state, without hassles with different exit codes. This however means, that if your scripts depend on the previous behavior with different exit codes, you need to adapt them.The full change log can be examined on Github The extension can be found at the TER release page.
Bugfix in install:setup command
install:setup commandFull list of changes. TER release page
It is now possible to exclude database tables when using the database:export command
database:export commandAdditionally a lot of cleanup was done to pave the way for groundbreaking new features in upcoming releases.
database:import now also works when the database is empty.The full change log can be examined on Github The extension can be found at the TER release page.
Fix a bug in database:updateschema command that can lead to data loss, when auto_increment fields needs to be changed
database:updateschema command that can lead to data loss, when auto_increment fields needs to be changeddatabase:import --interactive command (thx @stucki)Full list of changes. TER release page
Fix a cache related bug in extentsion:activate command
extentsion:activate commandFull list of changes. TER release page
The command install:fixfolderstructure now also creates the needed directories for all active extensions
install:fixfolderstructure now also creates the needed directories for all active extensionsextension:activate "foo, bar, baz" now work nicelyextension:setupactive is now multiple times faster, because the database schema operation fixes have been reduced to one call instead of one per extension. Regarding the database schema, calling extension:setupactive is now functionally equivalent to calling database:updateschema "safe" (or database:updateschema "safe" or database:updateschema "*.change,*.add,table.clear", which are as well functionally equivalent). This means, that database:updateschema calls in the deployment process can be safely removed in favor of just calling extension:setupactiveextension:setupactive and extension:activate have been fixed to avoid potential data loss (see #382).The full change log can be examined on Github TER release page
Fix a small mistake in database:updateschema command
database:updateschema commandFull list of changes. TER release page
It again comes with new features, usability improvements, a lot of bugfixes and very few breaking changes. It is now better prepared than ever for TYP…
After over three months of development since release of 3.0.0, we are proud to present a new major version of TYPO3 Console. It again comes with new features, usability improvements, a lot of bugfixes and very few breaking changes. It is now better prepared than ever for TYPO3 8.4.0 and higher.
Compared to the 3.5.1 release only a few, but still nice features have been added.
database:updateschema command has been reworked. The main goal was full TYPO3 8.x support (doctrine support), but user experience has also been improved.database:updateschema now by default executes all "safe" schema update operationsdatabase:updateschema now has a --dry-run option to preview potential schema updatesextension:list command to list available extensions in the system./typo3cms script is now a regular composer binary. This means if you install helhum/typo3-console with composer, it is installed in the bin directory defined the root composer.json (by default vendor/bin). Previously it was always installed along side with the composer.json file. If you use the console as TYPO3 extension, the script will still be installed in the TYPO3 root directory.The full change log can be examined on Github TER release page
Fix a bug in database:updateschema command that can lead to data loss, when auto_increment fields needs to be changed
database:updateschema command that can lead to data loss, when auto_increment fields needs to be changedFull list of changes. TER release page
Fix a small error in database:updateschema command
database:updateschema commanddatabase:updateschema command in TYPO3 8.4 and higher to avoid potential data loss. The next version of TYPO3 Console will fully support this TYPO3 versionFull list of changes. TER release page
New command to list extensions (active, inactive or all)
cache:flush command to not truncate a hardcoded list of tables, but to use TYPO3 APIFull list of changes. TER release page
One column per quarter.