Version 1.0.0 · 84 tools · no servers
DevTools you can talk to,
and an agent runway you can trust.
Inspect and copy CSS from any element. Capture full-page screenshots that handle sticky headers and lazy loading. Read Markdown as a document. Then hand the wheel to your AI assistant over MCP — driving the browser you are already signed into, with a human able to see and stop what it does.
Add to Chrome — free Read the manual
Free tier is genuinely useful forever. Pro is $29.99 once, three activations, no subscription.
Why this exists
The automation layer is not the moat
Chrome DevTools MCP, Playwright MCP, mcp-chrome and Browser Use are free, well funded and good. We are not going to out-free Google and Microsoft, and we do not pretend to.
The moat is the human loop
Free tools hand a language model a firehose and hope. T3rnel puts a valve on it: credentials redacted before they reach the model, high-risk actions that stop and ask, and a timeline you can scrub backwards when a run goes wrong.
Your real browser, your real sessions
No separate automation browser, no re-authenticating, no automation flags. The agent works in the profile you are already logged into — which is the honest version of the capability other tools chase with fingerprint spoofing.
What you get
CSS inspection
Hover any element and get its real, clean, copyable CSS — with the units the author actually wrote.
Full-page screenshots
One click, the whole page, stitched — and it handles the real web rather than the ideal one.
Markdown viewer
Read .md files as documents, including the ones your agent just wrote.
Page audit and link checking
Accessibility, spelling and links — reported honestly, including what could not be checked.
Record, replay and code export
Click through a flow once. Get a maintainable test that runs in your CI without this extension.
Agent safety
The part that justifies the price: a valve between a language model and your logged-in browser.
Encrypted identity vault
Per-site credentials, encrypted on your device, never written in the clear.
On claims
Every feature on this site is shipped in the build you download, and each one has a test that fails if the claim stops being true. Where a capability has a real limit — a cross-origin stylesheet the browser will not let us read, a link status it will not let us see, a licence check a determined user can patch — this site says so on the page for that feature rather than in a footnote.
The security controls are described as mitigations, not guarantees. A tool that overstates its protection is worse than one that has none, because someone will rely on it.