DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to send a task from your phone to your computer with Nano Muse

Start a message with an @ device name on the phone so the desktop app does the work there.

Authorization notice. Nano Muse is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Who it is forA person whose files, apps or browser sit on a computer, but who wants to start the task from a phone in hand.

The problemApps and windows on a computer are out of reach from a phone, so the task waits until you sit down.

The outcomeA task running on the desktop app that you started from the phone, with approvals arriving back on the phone in your hand.

What you need first

  • An Android 8.0+ arm64 phone, an iPhone or iPad (TestFlight beta), or a Windows, macOS or Linux x64 computer
  • An account: sign in with an e-mail or a mainland-China phone number, or use your own model key
  • For self-hosting: a server you control and Docker for the web app; git to fetch the repository

Steps

  1. Install Nano Muse Desktop for your system from the v1.0.5 release page, for example the macOS 12+ .dmg or the Windows 10+ .exe.
  2. Sign in on the desktop with the same account you use on the phone.
  3. On the phone, start the message with @Mac followed by the task, the form the README shows.
  4. Answer any stop that appears on the phone before the desktop goes ahead with a delete, send or payment.

Prompt for your agent

In the nano-muse/nanoMuse repository, install nanoMuse Desktop v1.0.5 on <computer> and sign in with the account used on <phone>. Send one harmless test task from the phone starting with @Mac, and verify the desktop reports the task as started.

Caveat. The README shows @Mac as the example and does not spell out the handle for a Windows or Linux computer, so check the device name in the app.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page