Mel – the agentic terminal
The AI terminal for teams.
For stores and agencies on PHP
Patch PHP stores fast: WooCommerce, Magento and Laravel
Mel's agent checks which PHP version and packages each store uses, updates them, and runs the tests. With approvals set to ask, you see every change, and every command that is not read-only, before it runs. Many stores can be done at once, one agent per store.
Powered by Mel's AI agent — free on your own provider key — 1,500 hosted-AI credits a month on Pro. The terminal is free.
What happened
PHP2Shell and the October 21 PHP release.
In late October 2026, a wave of security news called Black October put PHP at its centre. Two critical PHP flaws, known as PHP2Shell (CVE-2026-109618 and CVE-2026-109619), can let an attacker run code on a server without logging in. PHP released emergency updates on October 21, 2026: 8.2.35, 8.3.36, 8.4.27 and 8.5.12. Stores and agencies with many PHP sites now need to update each one.
Why it helps
The same commands, run for you.
Mel's agent runs the commands a person would run, reads the output and tells you what it found. You decide.
Know what each store runs
The agent runs php -v, composer show and composer audit, and tells you the PHP version and the packages to update.
Nothing changes without your yes
With approvals set to ask, every edit and every command that is not read-only shows on a card before it runs. You can deny any of them. A command that only reads, like php -v, runs without a card.
Many stores at once
Open one agent per store repo, each in its own worktree, and let them work side by side.
How it works
From version check to redeploy.
One store, start to end. Repeat in a new pane for the next one.
- 01
Check
Ask: "Which PHP version does this store run, and what does composer audit list?" The agent runs the commands and reads the results back.
- 02
Update
The agent proposes the update for PHP and the packages, with your package manager or your host's steps. You approve each command that changes something.
- 03
Test and redeploy
The agent runs your tests and shows the changed files. You review them, then redeploy the way you always do.
Built in
What Mel brings to the job.
Features that ship in Mel today.
SSH sessions
Open an SSH session in a pane, and the agent's tools run on that server.
One worktree per store
Track a repo, then create a worktree on a new branch, with its own agent.
Approval cards
File edits and commands that are not read-only wait on a card. A command that cannot be undone always asks.
Code review panel
See every changed file as a diff before you commit and redeploy.
For agencies
Many client stores, one window.
Give each store its own pane and its own agent. Each one checks its store, proposes the updates and runs the tests, while you approve the changes from one window.
- php -v, composer show and composer audit
- Updates you approve, step by step
- Tests run before you redeploy
- One agent per store, in its own worktree
FAQ
Questions and answers.
- Does Mel find vulnerabilities?
- No. Mel's agent runs the commands you would run, such as php -v and composer audit, and reads you the results. Composer audit checks your Composer packages. It does not check PHP itself.
- Which PHP versions are fixed?
- The October 21, 2026 release: 8.2.35, 8.3.36, 8.4.27 and 8.5.12. PHP 8.1 and older get no new release.
- Does it work on shared hosting?
- Often the PHP version is set in your host's control panel. The agent can tell you what to change there, and can still check and update your Composer packages in your project.
- Can I patch several stores at the same time?
- Yes. Open one pane per store repo, each in its own worktree, and start an agent in each. Review each one's changes before you merge.
- What does it cost?
- The terminal is free, and the agent is free on your own provider key. Pro is $20 a month with 1,500 hosted-AI credits.
More use cases
What else Mel can do.
Code review
Review diffs with full-repo context, enforce conventions, and iterate on the fix in your terminal.
ExploreBug investigation
Reproduce vague bugs, capture the evidence, and trace the cause back to the line.
ExploreRefactors & migrations
Scope a migration, apply it across the repo, verify with your build, and review the diffs.
ExploreGet started
Start with your first store.
Open the store in Mel, ask the agent which PHP version it runs, and approve the update.