In Tombstone, Val Kilmer’s Doc Holliday delivers a line that hangs in the air like gun smoke:

“I’m your huckleberry.”

It’s not a boast. It’s not a catchphrase. It’s a statement of intent.
If this job needs doing, I’m the one who’ll do it.

According to Southern vernacular, a huckleberry was someone just right for the job. The person you call on when it’s time to get something done. Not flashy. Not loud. Just reliable, precise, and quietly confident. If there’s work worth doing, your huckleberry will be there. Coat off. Sleeves rolled. Toothpick optional.

That’s the energy we wanted for our VS Code assistant.

If you’ve ever played The Oregon Trail, you know the vibe. You set off full of optimism, the wagon’s creaking, the oxen are cooperative, and spirits are high. Then reality sets in. The river’s too deep, someone’s caught dysentery, and the map you printed turns out to be wishful thinking.

Shipping a VS Code extension, especially one powered by AI, feels a lot like that.
You start with a plan and a promise. But the road? It’s longer.
The ruts are deeper.
And yes, someone’s always asking: “Are we there yet?”

Back in the dusty streets of modern coding, there's a new gunslinger in town: VS Code v1.100. And no, it's not just another shiny feature or cosmetic tweak, this one packs real firepower: named prompt files.

For the Huckleberry agent crowd, the folks who keep their tasks sharp, tools clean, and AI sidekicks at the ready, this is a genuine shift in the landscape.

What Makes This a Big Deal?​

Picture this: a busy day in the code corral. Bugs need wrangling, tests are bucking out of control, and documentation's flapping wild like a saloon door in the wind.

With the new prompt files feature, you can now summon task-specific prompts by name, right inside your VS Code chat. Drop your .prompt files into the .github/prompts directory, and when the moment calls, just type /your-prompt-name into the chat. That's all it takes, your custom instructions roll out like a sheriff's decree.

No more repeating the same explanations or reinventing the wheel. It's like carrying a custom-engraved six-shooter, ready to draw at a moment's notice.

"I'm your huckleberry."

Doc Holliday said it with a smirk and a six‑gun in Tombstone. Lately, every campfire gossip column in dev‑town swears that Cursor is the last quick‑draw coder standing, the sheriff nobody can out‑gun. Scroll LinkedIn and you’ll find breathless threads claiming Cursor’s edge is “unbeatable”, that Copilot might as well hand over its badge.

But while the headlines holler, GitHub Copilot has been oiling its six‑shooter in the back room and filing the sights. Today, Copilot saunters through the saloon doors ready to stare Cursor down. The shoot‑out is close, the tumbleweed is rolling, and the only real question is whether your code can keep running when the Wi‑Fi wagon loses a wheel.

GitHub Copilot’s April 2025 roundup plugged most of the gaps that once made Cursor the flashier gunslinger in the IDE corral. The update brought:

• One‑click Smart Actions that rewrite code in place.
• A side‑by‑side diff viewer for AI edits.
• Deep repo indexing backed by Nx’s brand‑new Model Context Protocol server.
• Agent mode that lines up terminal commands and waits for your nod.
• Enterprise privacy controls that keep company secrets locked in the safe.

Cursor still packs a Ghost (offline) mode and a slicker diff pane, yet the distance between the two tools has shrunk to the width of a guitar pick. So holster your editor of choice and let’s see who’s fastest on the draw.

Who's really pulling the strings in the season of AI?

The Season of AI​

They're saying it's the season of AI. Big voices in tech declare that within three months, six, twelve, AI will be writing all the code, automating the work, replacing developers at the keyboard.

Me? I'm not so sure.

"I'm your huckleberry."

It's a great line for a duel. But it's an even better metaphor for working with a large language model.

The coding frontier’s changing fast, friends. New gunslingers like Cursor and Windsurf are kicking up dust. These AI-powered editors are designed from the ground up to make coding feel more like vibing than grinding. Forget dry interfaces and manual tinkering. These new tools promise to read your intent, anticipate your next move, and flow with you like a rhythm section locking in on a groove.

Picture a dusty street at high noon. Your new AI agent swaggers out of the saloon, promising to draw boilerplate quicker than Wyatt Earp can spin a six‑shooter. Two minutes later it claims seven times eight is fifty‑four and insists that Array.prototype.last() shipped in 2015. The tumbleweed pauses, the piano stops, and someone mutters, "This town isn't big enough for hallucinations and the truth."

Projects sprawl quicker than a runaway cattle stampede, and release trains keep missing the station. Huckleberry harnesses Copilot Chat into a diligent foreman, slicing specs into bite-sized tickets so your team can scale from small posse to full tech rodeo without dropping the reins.

The rise of AI-assisted coding tools like GitHub Copilot and VS Code's agent mode has changed the way we build software. Tasks that once needed hours of careful work can now be stitched together in minutes. This shift has given rise to what some call "vibe coding", rapidly assembling apps by mixing AI-generated code with design templates.

It is fast. It is impressive. But it is not without its problems.