Functional prototype · Evidence confidence: High
MacroMouse
A pro-grade macro recording, humanisation, layering and export studio for programmable mice and desktop automation.
01 · Purpose
The problem
Advanced mouse and keyboard automation is fragmented across vendor tools and scripting formats.
02 · Experience
How it works
Users sign in, record or construct macro sequences in a studio, refine timing and behaviour, then export to targets such as AutoHotkey, Python, Logitech G HUB and Razer Synapse.
- Power users
- Gamers
- Automation users
- React 19
- TanStack Start
- TypeScript
- Electron
- Supabase dependencies
03 · Functional evidence
What actually exists
- TanStack application with authentication hooks
- Studio-oriented routing exists
- Export targets are represented in the live UI
- Desktop/Electron packaging scripts exist
- Desktop packaging architecture is present but was not executed during this census
- Broader device/vendor compatibility
- Whether every target exporter currently produces vendor-valid files
04 · Development
What remains
- Desktop packaging architecture is present but was not executed during this census
- Broader device/vendor compatibility
- Whether every target exporter currently produces vendor-valid files
05 · Commercial
Business model
Commercial model not verified from inspected code.
06 · Intellectual property
IP position
Original workflow and export architecture; no verified registration found.
This archive records what the available project evidence says. It does not infer legal registration, patent grant, trademark ownership or regulatory status where that has not been verified.
07 · Assessment
Strengths and limitations
Strengths
- Clear utility
- Cross-vendor positioning
- Desktop packaging path
Limitations / risks
- Hardware/vendor validation still requires runtime testing
08 · Evidence
What this record is grounded in
- GitHub repository: simonmowatt1-sudo/macro-weaver-x
- Repository README / project brief where available
- Implemented home route where available
A published URL means the project metadata records a deployment address. It is not represented as runtime-tested unless a separate verification pass confirms that deployment.
09 · Genealogy
Connections
RF Studio
Both expose hardware/control workflows through custom software interfaces.
Archive principle
Unknowns stay unknown until evidence changes them.Back to Project Galaxy