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.
Fix bug in database:updateschema
database:updateschemaFull list of changes. TER release page
Make a dummy TYPO3 extension available, when installing console via composer. This provides the possibility for other extensions to depend on typo3_co
database:updateschema command to not remove fields or tables with *.change type. To get tables or fields removed, the table.prefix and field.prefix type was added.cache:flush command if TYPO3 isn't set up yetconfiguration:set commandFull list of changes. TER release page
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Fix a bug triggered by a breaking change in TYPO3 7.6.x
Full list of changes. TER release page
Add autocomplete command, to generate shell code for auto completion. Works for bash and zsh shell.
autocomplete command, to generate shell code for auto completion. Works for bash and zsh shell.Additionally 3.3.0 incorporates some bugfixes and improved documentation
Full list of changes. TER release page
Fix extension:dumpautoload command
extension:dumpautoload commandFull list of changes. TER release page
Do not throw exceptions on E_STRICT notices any more
Full list of changes. TER release page
Fix install:setup command with latest TYPO3 master
Full list of changes. TER release page
Cloning the repository as way to install it has been deprecated. The extension files will be removed with the next major release.
helhum/typo3-console is not an extension any more, but a regular composer binary, which will be pulled into your vendor folder in composer based TYPO3 projects. Not required files will then no longer be delivered, when fetching the composer package as distribution and not by source.
The git repository itself still contains all TYPO3 extension files, so cloning will work until the next major version release. It is however not recommended to do so.
If you need the console as extension in non composer based projects, then download and install it from TER, by using the TYPO3 extension manager.
typo3cms binary from the project root is now deprecated. It is recommended to use the composer installed binary instead. Custom installation code will be removed with the next major version.cache:flush --force with TYPO3 8.xfrontend:request work again with TYPO3 8.xFull list of changes. TER release page
Fix binary for non composer mode
Improved documentation of some commands
database:export commandFull list of changes. TER release page
After over three months of development, we are proud to present a new major version of TYPO3 Console. It has:
After over three months of development, we are proud to present a new major version of TYPO3 Console. It has:
Configuration/Commands.phpextension:* commands like extension:setup, extension:setupactive and renamed commands like extension:activateinstall:fixfolderstructure to create the required TYPO3 folder structure so that e.g. the typo3temp folder can always be discarded and recreated during deploymentinstall:generatepackagestates command to be easier to configure (through environment variable) and more reliablebackend:lockforeditors command, which locks the backend only for editorsconfiguration commands, which makes it not only possible to remove, but also to view and change TYPO3 configuration from command linedatabase:import/export commands to interact with the (MySQL) database without the need to specify credentials. It also features an interactive mode which opens a MySQL console.--verbose switch to database:updateschema to be able to see the executed SQL during the process../typo3cms script is now a symlink and works only in dedicated TYPO3 directory. This is in line with how composer works and a preparation for having a real composer bin script. Other scripts will stop working.install:generatepackagestates command now takes the to be active TYPO3 packages from an environment variable and not the composer.json any more. Every third party extension is now considered active.extension: commands have been renamed for better and more consistent namingThe full change log can be examined on Github
Dropping support for previously supported TYPO3 versions is now (correctly) considered to be a breaking change.
This version includes only a few bugfixes compared to version 1.3.0.
There are no braking changes, so upgrading from 1.3.0 should be straightforward.
Starting with this version, we will now follow more clearly a:
Bugfixes will be released by increasing the bugfix version (e.g. going from 2.0.1 to 2.0.2).
When features are added, that do not break backwards compatibility, the minor version is increased (e.g. going from 2.1.1 to 2.2.0).
When braking changes are incorporated, a new major version will be released. Dropping support for previously supported TYPO3 versions is now (correctly) considered to be a breaking change.
Users with TYPO3 versions 7.6 and above are strongly advised to switch to typo3 console 2.0.0 and higher.
Please set the requirement in your root composer.json files to "helhum/typo3-console": "^2.0.0"!
Users with TYPO3 versions 6.2.x must stay with typo3 console 1.1.x for now.
Please set the requirement in your root composer.json files to "helhum/typo3-console": "~1.1.3"!
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
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
Add install:fixfolderstructure command
install:fixfolderstructure commandFull list of changes. TER release page
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.