Who it is forA developer who wants to check an agent's pending edits from a phone before approving or asking for changes.
The problemReviewing an agent's changes usually requires a laptop, and feedback on a diff is slow to relay.
The outcomeYou browse files, read git status and diffs on the phone, and send line comments back to the agent in the same session.
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 workspace for the agent session in the Pairfob app.
- Browse files and open git status.
- Open a diff and select the lines you want to comment on.
- Write the comment and send it to the agent.
- Check the agent's reply in Chat mode.
Prompt for your agent
In the arronKler/pairfob repo, use README.md to identify which review features the phone app supports for git status, diffs and comments. Report that list as your output. Verify each item is stated in the 'What you can do from the phone' section.
Caveat. The README describes the review features at a high level, so confirm the exact diff behavior in the app or the docs at Pairfob.com/doc before relying on it.
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