Contact
FR EN DE
Our expertise
Apps & AI
Consulting & Support
Cloud & IT Architecture
About References Careers Blog
All articles
AI & Data

What AI didn’t do for me (1/4): day one

I needed an SSH client that handles my connections properly. Three hours later, I had one. That’s when the real work began.

What AI didn’t do for me (1/4): day one

I manage a lot of servers. The existing tools do the job, but none of them did exactly what I wanted: one doesn’t remember anything properly, the others are either heavy or aging.

So I opened Claude Code and simply described what I wanted.

Three hours later: my connections organized in a tree, with folders, tags and favorites, passwords encrypted on disk, and a server availability check. Usable. Not a demo: usable.

Then it became addictive. Every day, one more idea:

  • a terminal embedded right in the window
  • a remote file explorer, with drag and drop
  • reusable commands, saved once and for all
  • sending the same command to several servers at once
  • automatic replay of a session already played
  • importing connections from competing tools
  • the whole application translated into English
  • automatic reconnection when the network drops

Each feature: one conversation, one afternoon.

Put end to end, that’s several weeks of work for a lone developer, done in a few days. And yet, those few days were not the hardest part. I’ll tell you why in the next article.


“What AI didn’t do for me” series: 1 · 2 · 3 · 4

Author CAPCOD
Ready to start?

Let's talk about your project.

Tell us what you need, we reply within 48 hours.

Get in touch