Introducing Magic Device 0.0.2
Know when it is safe to run the heavy job.
Whether the device is on mains power, whether the viewer is away and whether the macOS window is fullscreen. One import, no setup, no Runner edits.
One import. Three signals.
Run the heavy job only when nobody will notice. Magic Device reads mains power, viewer idle and window fullscreen behind one small API.
-
Mains power
Learn more about Mains powerchargingis true on mains power, read throughbattery_plus. A platform without an implementation answersfalse. -
Viewer idle
macOS and Windows read the system input clock and report away after two minutes without input. Everywhere else it follows the app lifecycle.
Learn more about Viewer idle -
Window fullscreen
Follow the macOS window as it changes and flip it with one
Learn more about Window fullscreentoggle()call. -
Honest on every platform
A native read where one exists, a clear fallback where it does not. Its only native code is a macOS plugin.
Learn more about Honest on every platform -
Idle until you start it
Nothing is collected until
Learn more about Idle until you start itstart(): an instance that never starts holds no channel, no timer and no lifecycle observer. -
Test without a device
Every
Learn more about Test without a deviceDevicePowerread except the app lifecycle is a constructor parameter, so a test needs no mocking library.
Your agent speaks Magic Device.
The Magic Device skill teaches your coding assistant when to gate background work and how to wire DevicePower and WindowFullscreen before the first line. One command wires it up.
run in your project other editors
works with
And checks the docs.
Skills teach the API. The MCP server at mcp.anilcancakir.com/magic_device gives your agent live docs lookup while it edits, so it never guesses a signature.
-
Streamable HTTP
One endpoint, every client.
-
search-docs
Live query against the source.
-
Public, no auth
Read-only, free to use.
# streamable http, the default
# or stdio, for clients without http
Public, no auth.