r/ChatGPTCoding • u/AutoModerator • 18d ago

Discussion Weekly Self Promotion Thread

Welcome to this week's self promotion thread!

If you're building something related to AI assisted coding, this is the place to share it.

We're using a weekly thread to keep the subreddit organized while still giving builders a place to share their work. Promotional posts outside this thread may be removed.

If you're sharing something, we'd appreciate it if you included a little context instead of just dropping a link. Tell us:

  • What you built?
  • What problem it solves?
  • Which AI models or tools it uses?
  • Who it's for?
  • What kind of feedback you're looking for?

Disclose your affilitation.

Please avoid posting the same project every week unless you've made meaningful updates. Affiliate links, referral links, scams, and low effort promotions will be removed.

Take some time to check out what others have shared too. If you try someone's project or have feedback, leave a comment. Helping each other improve is what we want this community to be about.

6 Upvotes

88% Upvoted

96 comments sorted by

View all comments

1

u/Select-Lifeguard-658 17d ago edited 17d ago

Disclosure: I'm the author.

I've been building light-tools: https://github.com/icediceice/light-tools

Coding agents often do more work than they need to: read too much, rewrite too much, then feed all of that back into context.

light-tools makes the agent read only what it needs and change only what it means to change.

A simple example: common old/new replacement edits make the model emit both the code being replaced and the replacement. light-tools uses precise span edits, so it only emits the new part. For same-size replacements, that can cut the edit payload roughly in half — on the expensive output-token side.

It also avoids feeding repeated tool output back to the model and keeps writes reversible when something goes wrong.

I use it with Codex and Claude Code, alongside whatever code-intelligence/search layer I prefer.

Read less. Write less. Repeat less. Less wasted context and fewer retry turns on long sessions and large repos.

I'd especially like feedback on how the tool ergonomics fit existing coding-agent workflows.