AIMEE beside a dark developer workbench with code, test, package, and documentation screens

Developer tools you can inspect before you trust.

AIMEE DevTools brings build control, asset research, protocol experiments, and diagnostics into one local-first toolkit. The public tester is a simulation: no Steam login, no live Game Coordinator, no injection, and no game modification.

Open offline demo
Offline by defaultNo Steam authenticationNo live GC connectionNo VAC-sensitive behaviorSynthetic demo data

What the toolkit covers

Each surface has a narrow job, visible input, and exportable output.

01

Build orchestration

Run repeatable local build, package, and verification tasks from one visible queue.

02

Asset research

Inspect user-owned local files and generate structured, reviewable reports without touching a running game.

03

Protocol laboratory

Decode documented message shapes and replay synthetic fixtures in an isolated sandbox.

04

Service diagnostics

Exercise local APIs, queues, databases, and WebSocket paths with scrubbed example data.

One path from source to evidence

The public documentation follows the same sequence as the tools: choose a local input, validate it, run a bounded task, inspect the evidence, and export a sanitized report.

Read the technical architecture →
  1. 01Select a local fixture or synthetic scenario.
  2. 02Validate paths, formats, versions, and safety boundaries.
  3. 03Execute the isolated worker with no account connection.
  4. 04Review the log, diff, and generated report before export.
AIMEE DevTools

Open source, documented, and unofficial.

The source is available for review and contribution. References to Valve, Steam, Counter-Strike 2, SteamKit, protobuf, or Game Coordinator protocols describe compatibility research and community tooling only. Valve and Steam do not sponsor or endorse this project.

Try every public surface without connecting an account.

The browser tester uses synthetic records and makes no outbound game-service requests.

Open offline demo