AMResume
Back to featured work

Active engineering · public source

MegasMoves

Your always-on SI agent for all your devices.

PythonMCPC++WinUISwiftGTKKotlinChrome Extension

Overview

MegasMoves is an Amretra Dynamics multi-device software automation project. Its public source documents a Python runtime, typed MCP operator interfaces, native Windows/macOS/Linux components, Android/Kotlin, and browser connectors. My engineering work centers on integration boundaries, execution state, permissions, and verification.

Problem

Agents need well-defined access to tools and devices, with explicit permissions and verified outcomes instead of unrestricted control or optimistic UI action acknowledgements.

Architecture

Typed MCP operator tools mediate a local Python runtime and native platform bridges. Dedicated browser automation and an opt-in Chrome tab connector use different access boundaries.

My engineering work

I independently build and integrate runtime, action/task state, browser/device boundaries, and product surfaces. The linked public repository shows implemented components and documented engineering direction.

Design tradeoffs

Permissions should be narrow, device bridges platform-specific, and action results observed rather than assumed. Those decisions make connected-device automation more auditable.

Verification and limitations

Public source and setup documents provide technical evidence. Platform parity, live customers, revenue, and full production readiness are not claimed unless separately demonstrated.

System architecture

How the components connect

  1. 01

    MCP client

  2. 02

    Typed operator interface

  3. 03

    Local Python runtime

  4. 04

    Native / browser bridge

  5. 05

    Scoped device operation

Architecture is derived from the project's public documentation. It is a conceptual flow, not a live system diagram.

Engineering decision

Separate typed capability contracts from platform-specific bridges so an agent's request is checked before local execution.

Failure mode

Permissions, stale context, or a click without an observed result can make automation unsafe or misleading.

How to examine the evidence

Inspect published runtime, native-app, browser-connector, and permission-boundary source. Deployment and platform parity require separate live testing.

Public architecture and setup

An actively developed SI-agent platform, not a verified finished cross-platform commercial release.