About

My name is Giovambattista Fazioli, an Italian Lead Developer. I started coding in 1983 and have experience in design, graphics, and assembly language. I worked with various systems like Commodore and processors such as Z-80 and 8086. Later, I worked as a program developer in a telecommunication company using languages like C/C++, PHP, and Visual Basic. After 7 years, I became a freelance developer. Currently, I am the Lead Developer at Namecheap, specializing in ReactJS, TypeScript, and NextJS.

Badges

Buddy System
Buddy System
Thought Leader
Thought Leader
Tastemaker
Tastemaker
Veteran
Veteran
View all badges

Maker History

  • Lancetta
    LancettaKnow when to push your coding agents, and when to ease off
    Oct 2026
  • FinderGit
    FinderGitEvery Git repo on your Mac: browse, commit, review, clean
  • GlanceCard
    GlanceCardDaily GitHub cards for your READMEs, in nine looks
    Oct 2026
  • WP Bones
    WP BonesWordPress plugins with Laravel-like bones
  • Netfox
    NetfoxA native local macOS network monitor
    May 2026

Forums

🧹 Lancetta 0.62.0 — what your coding agents leave behind

Lancetta 0.62.0 is out Maintenance now cleans up after your coding agents, and reads Claude Code's settings the way Claude Code does.

1. Storage

Codex installs that stopped halfway, old server releases, empty git folders, files ChatGPT copied out, build caches of ended sessions, Chrome's clones: each with what it frees and why it can go. Nothing a running program holds is offered, and it all goes to the Trash.

FinderGit 0.54.0 — Agents cleans up after your coding agents

Hi,

FinderGit 0.54.0 is about the Agents dashboard. It already reads what your coding agents load before they start; now it also finds what they leave behind on disk, helps with a skill listing that has grown past its room, and reads Claude Code's settings, and your organization's policy, the way Claude Code itself does.

What the agents leave behind

What did your agent do that you only found out about later?

Not the dramatic stuff that gets blocked. The quiet things you only notice an hour or a week later

Mine was two agent sessions working in the same repo. One of them went to clean up its own background process by matching the name and killed the other session's run too. No error anywhere. I just found a half finished job later and had to figure out why

View more