Who it is forA developer who has a screenshot, photo or PDF on the phone that an agent needs to read.
The problemGetting a file from a phone to the machine running the agent usually means emailing or cloud syncing it first.
The outcomeThe file reaches the workspace and its path appears in the draft, so the agent can open it.
What you need first
- A macOS or Linux computer that stays awake and online
- A current mobile browser on the phone or tablet
- Herdr 0.8 or newer (the installer adds it if missing)
- An AI agent installed and signed in on the computer, if you want to use one
Steps
- Open the agent session on the phone.
- Choose the upload option and pick a photo, PDF or other file.
- Wait for the upload to finish over the P2P connection.
- Check that the workspace path is inserted into the draft.
- Send the message to the agent.
Prompt for your agent
In the arronKler/pairfob repo, open README.md and quote the sentence that describes how files are handed to the agent. Output that quote and the list of file types the README names. Verify the quote matches the README exactly.
Caveat. The README does not state file size limits, so test with a small file first if the file is large.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: 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