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

How to edit the planner and actor prompts for a custom workflow with Esp32 Iphone Agent

Change the plain-text prompts in the repo and rebuild the app to tune how the agent behaves.

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

Who it is forA developer who finds the agent misreads a certain app or keeps taking the wrong step, and wants to tune its instructions directly.

The problemA generic agent prompt may not fit a specific app, so the agent repeats the same mistake.

The outcomeUpdated planner and actor prompts bundled into a rebuilt app that behaves more closely to the target workflow.

What you need first

  • An ESP32-S3 board, tested with a Seeed Studio XIAO ESP32S3 (plain version, 8 MB PSRAM)
  • An iPhone on iOS 18 or later with cellular data
  • An OpenAI-compatible vision model endpoint and API key
  • A Mac with Xcode, needed once to flash the board and build the app

Steps

  1. Clone the repo and open the prompts/ folder.
  2. Edit the planner and actor prompt text for the workflow you need.
  3. Run open ios/IPhoneAgent.xcodeproj and rebuild the IPhoneAgent scheme.
  4. Install the rebuilt app on the iPhone and run the same goal again.
  5. Compare the new run in Runs against the old one to confirm the change.

Prompt for your agent

Using the repo onehumanbeing/esp32-iphone-agent, read the planner and actor prompts in prompts/ and propose one edit for <target app or workflow>. Expected output: the changed prompt text as a diff. Verify that the edit keeps the existing action names so the app still parses the model reply.

Caveat. The README says prompts are bundled with the app and rebuilt, but it does not describe how the app parses replies, so test each edit on a real run.

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