📖 Journal

Before there was HarewireBot, there was simply Harewire.

This isn't actually the first Harewire website. And HarewireBot isn't the first Harewire either.

The story started back in 2024, with a Discord bot made for the Nousagi Gang.

🐇 Where the name came from

Our group is called Nousagi Gang. The Japanese word nousagi (野兎) refers to a wild rabbit, so the rabbit theme was already there.

Then came the name Harewire.

Hare was a little nod toward the rabbit connection. Wire represented another part of our group: the games we played together, especially cyberpunk-inspired, text-based MMORPGs where connections, networks, and digital worlds were a big part of the experience.

Put them together and we got Harewire — a rabbit with a connection to our little digital world.

🤖 Built with BotGhost

The first Harewire was built using BotGhost, a platform I genuinely enjoyed using.

What made it fun was how much could be customized. Commands, responses, behavior, and all the little details that made a Discord bot feel like our bot could be configured without having to build the entire thing from scratch.

For a while, that was enough. Harewire existed, worked, and had a place in our Discord server.

⚠️ The year Harewire almost disappeared

Then, in 2025, BotGhost ran into an issue involving Discord.

For a moment, it looked like BotGhost's operations might be forced to stop. Naturally, that made me wonder what would happen to Harewire.

I remember thinking that I might lose the bot I had made.

Fortunately, the situation didn't end that way. BotGhost continued operating, and Harewire could keep running.

And honestly?

I was glad.

I've always liked BotGhost. It isn't perfect, but I still appreciate what it made possible for me.

💡 What if I built Harewire myself?

Eventually, though, another thought started taking shape.

I wanted to learn to make a Discord bot myself.

Not because Harewire had failed. Not because I stopped liking BotGhost.

I simply wanted to understand what was happening behind the scenes.

What if I could build the bot's systems myself? What if I could decide exactly how commands worked? What if I could add features whenever I came up with an idea, without depending on a premium subscription or the limits of another platform?

That was the beginning of HarewireBot.

🐇 Why HarewireBot?

There was one thing I didn't want to do.

I didn't want to call it Harewire 2.0.

And I didn't want Harewire V2, either.

The new project isn't simply the old bot rebuilt with newer technology. It has a different purpose.

So I added one word:

HarewireBot is the continuation of the idea, but also a new project in its own right.

Now I'm learning TypeScript, Cloudflare Workers, Hono, Discord's Interactions API, command architecture, permissions, deployment, testing, and everything else that comes with building a bot from the ground up.

And because I'm building the system myself, there's a new kind of freedom:

If I can build it, I can add it.

🚀 HarewireBot begins

HarewireBot started small.

A Discord interaction endpoint. A Cloudflare Worker. A single /ping command.

Then came a command system. Routing. Registration. Options. Permissions. /say. Releases. Testing. More phases.

And now we're here.

v0.3.0.

Phase 4 is complete, Phase 5 is beginning, and there is still a ridiculous amount left to build.

🌐 And now, the website

The first Harewire website was simple. It mostly existed to explain what the bot was and document its commands and their uses.

This website is different.

It's not just a manual. It's a development hub.

It has a roadmap, releases, changelog, development status, and now this journal — because I realized that the story behind the project is worth documenting too.

In a way, this is Harewire's website 2.0 as much as HarewireBot is a new chapter of the bot itself.

🐇 So... what's next?

I don't completely know yet.

And that's probably one of the best parts.

Harewire started as something I made for a group of friends. Years later, it's become a project where I'm learning how to build something of my own.

Maybe HarewireBot will become a powerful server utility. Maybe it will become something completely different.

For now, I'm happy building it one phase at a time.