---
title: "Sushanth Kamabathula (@sushanthk) | Hashnode"
description: "Notes on code, chess, mistakes, and the tools I build with. Read the latest articles by Sushanth Kamabathula on Hashnode."
url: "https://hashnode.com/@sushanthk"
---

@sushanthk

# Sushanth Kamabathula

@sushanthk · Joined August 2026

Notes on code, chess, mistakes, and the tools I build with.

[Website](https://kansochess.app/)

### [My REST Client Formatter Returned 404 for Every Version](https://blundersnbuilds.hashnode.dev/my-rest-client-formatter-returned-404-for-every-version?utm_source=hashnode&utm_medium=feed)

I wanted VS Code's REST Client inside Zed. One piece of the setup was dead upstream, and the part that worked was a five-line task.

2 min read · [blundersnbuilds.hashnode.dev](https://blundersnbuilds.hashnode.dev/my-rest-client-formatter-returned-404-for-every-version?utm_source=hashnode&utm_medium=feed)

[Nov 10](https://hashnode.com/posts/my-rest-client-formatter-returned-404-for-every-version/6af2a7e1e3bc83fa55c0e0b0)

### [I Retired VS Code and Wrote Down Everything Zed Can't Do](https://blundersnbuilds.hashnode.dev/i-retired-vs-code-and-wrote-down-everything-zed-can-t-do?utm_source=hashnode&utm_medium=feed)

Porting a VS Code setup to Zed took an afternoon. Listing what had no equivalent was the part that told me something.

2 min read · [blundersnbuilds.hashnode.dev](https://blundersnbuilds.hashnode.dev/i-retired-vs-code-and-wrote-down-everything-zed-can-t-do?utm_source=hashnode&utm_medium=feed)

[Nov 10](https://hashnode.com/posts/i-retired-vs-code-and-wrote-down-everything-zed-can-t-do/6af2a79fe274de5a6759d3bc)

### [Headroom Isn't Coming Back a Fourth Time](https://blundersnbuilds.hashnode.dev/headroom-isn-t-coming-back-a-fourth-time?utm_source=hashnode&utm_medium=feed)

Compressing chat messages to save tokens sounded clever until it started blowing up my prompt cache and mangling diffs.

3 min read · [blundersnbuilds.hashnode.dev](https://blundersnbuilds.hashnode.dev/headroom-isn-t-coming-back-a-fourth-time?utm_source=hashnode&utm_medium=feed)

[Nov 9](https://hashnode.com/posts/headroom-isn-t-coming-back-a-fourth-time/6af1573daf44fe0391f912c4)

### [Headroom Came Back a Third Time, With a New Name](https://blundersnbuilds.hashnode.dev/headroom-came-back-a-third-time-with-a-new-name?utm_source=hashnode&utm_medium=feed)

A day after I said the compression proxy wasn't coming back, it came back as a six-line zsh function.

2 min read · [blundersnbuilds.hashnode.dev](https://blundersnbuilds.hashnode.dev/headroom-came-back-a-third-time-with-a-new-name?utm_source=hashnode&utm_medium=feed)

[Oct 9](https://hashnode.com/posts/headroom-came-back-a-third-time-with-a-new-name/6ac85af8318a1674212bc966)

### [My Sidebar Couldn't See Agents That Started Before It Did](https://blundersnbuilds.hashnode.dev/my-sidebar-couldn-t-see-agents-that-started-before-it-did?utm_source=hashnode&utm_medium=feed)

workmux only tracks agents that register themselves. So I wrote a script that goes looking for the rest.

3 min read · [blundersnbuilds.hashnode.dev](https://blundersnbuilds.hashnode.dev/my-sidebar-couldn-t-see-agents-that-started-before-it-did?utm_source=hashnode&utm_medium=feed)

[Oct 8](https://hashnode.com/posts/my-sidebar-couldn-t-see-agents-that-started-before-it-did/6ac734bd81b701afb3600736)
