Hexanaut Github ((hot)) «2026»

He merged the PR at 3:14 AM. The CI pipeline ran. Tests passed. He deployed to the live Hexanaut ladder.

He clicked through. The contributor, @hexVector , had rewritten the scoring function. Instead of maximizing cells held, they minimized distance to supply hubs —a classic supply-chain hack turned into a combat edge.

By morning, hexanaut-ai/hex-core had 200 new stars. @hexVector revealed themselves as a former logistics AI researcher who had lost everything to a ransomware attack. The Hexanaut bot wasn't just a game—it was a proof-of-concept for decentralized defense. hexanaut github

His bot—now named HexVector-1 —didn't charge forward. It retreated . It gave up three border hexes to consolidate power. The enemy overextended, starving for resources. Then, in one devastating turn, HexVector-1 reclaimed twelve hexes in a single loop—a legal move the game engine hadn’t seen in three seasons.

And then he watched.

“Who pushed that?” “Check the GitHub.” “Someone just broke the meta.”

“Clever,” Leo whispered.

Leo smiled. He forked the repo again, added a single line to the README: And somewhere in a server farm across the ocean, HexVector-1 expanded one more hex—quietly, greedily, perfectly.