Who it is forAn iPhone user who already uses Lody on a computer and wants chat and session access on the go.
The problemLody has no App Store listing in the README, so the phone needs a different way to get the client.
The outcomeThe current Lody iOS beta build is installed on the iPhone through TestFlight and can connect to your Lody sessions.
What you need first
- An iPhone running iOS 26 or later
- Access to a Lody service (the README does not describe how to sign up)
- For building from source: macOS Sequoia or later, Xcode 26.5 or later with Command Line Tools, Node.js 22.13 or later, and pnpm 11.10.0
Steps
- Confirm the iPhone runs iOS 26 or later.
- Open the TestFlight link in the README on the iPhone.
- Install the current build from TestFlight.
- Open Lody iOS and sign in through the Device Flow prompt.
- Check that your existing sessions appear before relying on the app.
Prompt for your agent
Using the Innei/lody-ios repo README, list the exact steps to install the current TestFlight beta on an iPhone running iOS 26 or later. Output a numbered checklist. Verify that the output says beta builds may be unstable and may break existing sessions.
Caveat. The README says beta builds track main, update automatically, and may break existing sessions, so keep a copy of anything important from your sessions.
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