Engineering note · 001

PROJECT

NightwatchA headless CS2 client.

A full Counter-Strike 2 client, built to join real servers without launching the game.

NOVEMBER 2, 2026 · BUILT SOLO BY JAEGER33211
CS2COMMENDS / INTERNAL PROJECT
NO GAME INSTALL
NO GPU · NO WINDOW
0CS2 install files
~300 MBRAM per client*
Multiclient orchestration
1developer · built solo

No CS2 installation or game assets are loaded; the client uses its own code, protocol definitions and supporting runtime components. * Approximate RAM budget for a full, connected client with chat and live player parsing; not a controlled benchmark. This is separate from sending commends, which uses a much lighter worker and considerably less RAM.

Not another Steam bot

Plenty of tools can log into Steam, add friends or send lobby invites. That's the easy part, and it's been done for years. Actually stepping onto a CS2 game server — through Valve's relay network, speaking the game's own network protocol, fully connected and staying in — is a different league. Until now, that took the real game client running on a real PC.

We wanted to see if it could be done without one. It turns out it can.

What it can do today

Join real serversCommunity and official-style servers, the same way the game does it — not a fake "online" status.
Stay connectedIt doesn't just knock on the door. It sits in the server like a player would, for as long as it needs to.
Read the roomIt sees in-game chat and knows who else is on the server, live.
Run as a fleetMultiple clients can be coordinated, supervised and recovered automatically.
Keep up with updatesWhen Valve patches CS2, we patch too — usually the same day.
Run anywhereNo game install, no GPU, no screen. A background service is all it needs.

The road here

The first "hello"

The first time a server answered at all, we celebrated like we'd won a major. It disconnected a second later.

Staying in

Getting a connection that didn't drop took far longer than getting the first one. Most of the work lives here.

Seeing the server

Then came chat and the player list — the moment it stopped feeling like a test and started feeling like a real client.

From one to a fleet

One client is a proof of concept. Coordinating multiple clients reliably is what turns an experiment into a service.

NO GAME INSTALL · NO GPU · JUST CS2

How long did it take?

Months of work, a lot of late nights and many rounds of "why is it disconnecting now". There's no public documentation for this and no open-source shortcut — every piece was built, tested and tuned by us. We're honestly a little proud of it.

What I learned

  • Patience beats cleverness. Most breakthroughs came from carefully checking the same thing one more time, not from a genius idea.
  • "Works once" is 10% of the job. Reliability, recovery and keeping up with updates are the other 90%.
  • Built solo. I designed, implemented, tested and integrated the headless client myself. It uses standard tools where useful, but the client work was a one-person effort.

Why it matters for you

It's the same philosophy behind everything at CS2Commends: our own tech, our own servers, no middlemen. Owning the whole stack means faster delivery, fewer things that can break and quicker fixes when Valve ships an update — so your order keeps moving while others wait for someone else to fix their tools.

What's next

It isn't optimized yet, so the numbers above will only get better. We'll keep making it lighter and faster, and we have a few more ideas we're not ready to talk about. Stay tuned on Discord.

FAQ

Is this a cheat?

No. It doesn't play the game, aim or give anyone an advantage in a match. It's a network client — it connects, stays connected and understands what's happening on the server.

Will it be open-sourced?

No. This one stays in the lab. 😉

Can I buy or license it?

Not at the moment. It powers our own services.

Does it break when CS2 updates?

Sometimes, briefly — just like any software that talks to a live game. We watch for updates and usually ship a fix the same day.

See commend packages