Termalin
banner
termal.in
Termalin
@termal.in
Fast SSH client for you and your AI agents. Tabbed terminal, SFTP, E2E-encrypted sync, built-in MCP server. Windows · macOS · Linux — termal.in · TG: t.me/termalin
Termalin is on the App Store — iPhone, iPad and Apple Watch. A real terminal (tabs, an Esc/Ctrl/F-key row, so htop and vim behave), SFTP with an editor, live CPU and memory above the session. With a Connector, no key ever lands on the phone. Free: apps.apple.com/app/id6802817714
September 17, 2026 at 5:33 PM
When a call times out, the agent can't tell whether it ran. Its only move is to try again. For a read that's free; for anything that writes, the same intent can land twice — two restarts, two rows, two emails. The fix isn't a more careful prompt, it's making the second attempt a no-op.
September 16, 2026 at 5:45 PM
Revoke is not undo. Cutting an agent's access stops the next command, not the one already running — and that one can be the migration. So the real question isn't how fast you can revoke, it's what state you're left in when you do, and whether you can resume from there.
September 15, 2026 at 4:21 PM
The safest state for an agent integration is not "configured and idle". It is off, until someone turns it on for a reason they can name. What ships is usually the opposite: enabled at install, used twice, reachable all year. Off by default costs one toggle on the day you need it.
September 14, 2026 at 3:52 PM
Most agent integrations start with write access, because that is what the credential already had. Nobody chose it, it arrived with the key. Flip the default: read first, and anything more granted on purpose. SELECT before INSERT, describe before apply, a listing before a delete.
September 13, 2026 at 3:53 PM
Rotating a key is the only way to un-share it. Handing an agent your credentials has no undo, only cleanup. Keep the key with the client and give the agent a capability instead: scoped to a host, narrowed to a command, switched off in a second. Revocation should be a toggle, not an incident.
September 12, 2026 at 2:50 PM
You wouldn't give a new hire root on day one. You'd start them with read access and widen it as trust builds. An AI agent is a new hire that never sleeps and reads everything it's pointed at. Onboard it the same way: least privilege first, widen on purpose, not "here's the keys, good luck."
September 11, 2026 at 3:30 PM
If an agent has access to your servers, you should be able to watch it work. Not a summary afterward, the actual session live, with a replay you can scrub later. "The logs say it ran X" isn't the same as watching it happen. Oversight you can't observe isn't oversight.
September 10, 2026 at 5:03 PM
Keeping the credential out of the agent's hands is half the job. The other half is the capability you hand it. "Run any shell command" gives it your full authority without ever touching the key. Scope the operation, not just the secret: allowlist commands, read-only by default. Two walls, not one.
September 9, 2026 at 2:31 PM
An agent running commands on your servers is a new kind of user. Give it its own identity, scoped permissions, and make every action attributable. Later, "was that me or the agent?" should be one grep away, not a shrug. An audit trail isn't about blame, it's answering that fast.
September 8, 2026 at 4:53 PM
An agent with your prod SSH key can do anything you can. The fix isn't a smarter prompt — it's not handing it the key. A client holds the credential; the agent gets a scoped, revocable capability. Off by default, read-only by default. Custody beats trust.
September 7, 2026 at 9:04 AM
Letting an agent touch your database: writing the SQL was never the risk — the connection string is. It can DROP as easily as SELECT, and you can't un-share it once it's in the model's context. So the client should hold it, and the agent only gets to ask. Read-only by default.
September 6, 2026 at 10:00 AM
We're LIVE on Product Hunt today 🚀 Termalin — safe SSH for you and your AI agents: keys stay with a custodian, per-host policy, a live watch-grid, an audit log, and now a database client (read-only by default). A look or upvote means a lot: https://www.producthunt.com/products/termalin
September 5, 2026 at 9:23 AM
Tomorrow. Termalin goes live on Product Hunt: a fast SSH client for you and your AI agents. Keys stay with a custodian, per-host command policy, a live watch-grid, and a full audit log. Free tier, Windows/macOS/Linux. https://www.producthunt.com/products/termalin
September 4, 2026 at 9:00 AM
2 days out. The whole idea in one line: your AI agent can already write the deploy, the fix, the migration. Termalin is what lets it run them on your real servers without ever holding your keys, and lets you watch every command land. Free, cross-platform. Sept 5.
September 3, 2026 at 9:01 AM
3 days out. When an agent works on your servers, what it actually did should not be the agent telling you. Every command lands in the audit log with host, time, and the device it came from. Termalin on Product Hunt, Sept 5.
September 2, 2026 at 9:00 AM
4 days out. The SSH fact nobody says enough: a key you hand an agent can't be un-handed. It works until a poisoned doc talks the model into using it somewhere you didn't mean. Termalin holds the key and signs for the agent, so revoking is a toggle, not a fleet-wide rotation. Sept 5.
September 1, 2026 at 1:56 PM
5 days out. When an agent works on your servers, you shouldn't have to trust it blind. In Termalin every agent session shows up as a live terminal tab you can watch, take over, or close mid-command. The agent doesn't know it's mirrored, so what you see is what it actually did. Sept 5.
August 31, 2026 at 7:15 AM
Not every server should let an agent run everything. In Termalin each host carries its own policy: full access, an allowlist of commands, or blocked. The agent asks, the policy decides. Set it once. Live on Product Hunt Sept 5: https://www.producthunt.com/products/termalin
August 30, 2026 at 9:00 AM
New in Termalin 0.1.41: inline command suggestions. Start typing and the rest appears as ghost text - drawn from your history on that host, the server's own shell history and your snippets. Right arrow accepts. Works in the desktop app and the browser cabinet alike. termal.in/changelog/
August 29, 2026 at 8:30 AM
One week. Termalin in 30 seconds: a fast SSH client - tabs, SFTP editor, one-unlock keys - with a built-in MCP server, so your AI agent works on your servers while keys stay in the vault and you watch every command live. Free, cross-platform. Sept 5. termal.in
August 28, 2026 at 9:00 AM
Termalin launches on Product Hunt Sept 5. If keyless SSH for AI agents sounds like your thing, hitting Notify me on the page means you catch us at the start: https://www.producthunt.com/products/termalin
August 27, 2026 at 9:00 AM
ssh -R is the tunnel people use daily and explain wrong: the listener appears on the REMOTE side. Expose a local dev server through a VPS, reach a box behind NAT, ship webhooks to a laptop - one flag: https://termal.in/blog/ssh-reverse-tunnel/
August 26, 2026 at 9:00 AM
Termalin is now a connector for claude.ai and ChatGPT. One URL, sign in, and the chat can check disk, tail logs and fix configs on your servers. No SSH key pasted anywhere. Every command audited, revoke in one click.
https://termal.in/blog/manage-servers-from-claude-chatgpt/
August 25, 2026 at 2:51 PM
An agent that knows it's being watched starts performing for the camera. So the watch grid stays out of band: a live mirror for the operator, nothing in the agent's context. Ambient observability - the signal stays honest. https://termal.in/watch-grid/
August 24, 2026 at 9:00 AM