
aio app logs shows why your App Builder action failed
aio app logs shows the logs of your latest activation, or of up to 50 with --limit.
Short notes on things I learned while working with Adobe Commerce (Magento 2), one idea per post.

aio app logs shows the logs of your latest activation, or of up to 50 with --limit.

Ask Composer which installed packages refuse the target version before you bump Adobe Commerce.

The fixes every Adobe Commerce store needed in autumn 2026, in one list, with links to the steps.

php -v tells you the version. On older PHP lines, the package changelog tells you whether the PHP2Shell fix was backported.

Two agents in one working copy will overwrite each other. Worktrees give each one its own folder and branch.

/init, /clear, /compact, /mcp, /permissions and /model cover most of my day.

WordPress already uses m as a query var for date archives. Your test parameter will break the page.

Traces record every action, network call and DOM snapshot. Open one and scrub through the failure.

bin/magento config:set --lock-env writes the value to env.php and greys it out in the admin.

Turn on Adobe Commerce’s query log, reproduce the slow page, then read the log instead of guessing.

Reindexing everything after a small change wastes minutes. Name the indexer you need.

Chrome tells you when it drops a cookie because of SameSite. You just have to look in the right place.