DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to save Agent summaries to a chosen phone folder with Muse Lite

Authorize a phone folder, then have the Agent save and re-read Markdown or other text files there.

Who it is forA user who wants AI-written notes or reports stored in a normal phone folder where other apps can see them.

The problemFiles written by the Agent stay in the app's private workspace unless they are exported somewhere visible.

The outcomeMarkdown summaries appear in a folder you picked, and the Agent can list and read them later.

What you need first

  • Windows x86-64 PC with Python 3.13 for the provided build script
  • Internet access for the first build to download Briefcase, the Android SDK, Gradle, and Maven dependencies
  • Android 11+ arm64 device or emulator
  • An OpenAI-compatible HTTPS provider base URL, model ID, and API key

Steps

  1. Open Settings > 文档保存目录 > 选择手机文件夹, pick a subfolder such as Documents/MuseLite, and confirm Use this folder or Allow.
  2. Tap 保存测试文档 to confirm a Markdown file appears in the selected folder.
  3. Ask the Agent in chat to save a summary with a file name, for example "把这份总结保存到手机目录，文件名为 总结.md".
  4. Ask the Agent to list the folder contents, for example "列出我设置目录里的文件", and check that the new file appears.
  5. If access is revoked, select the folder again in Settings; use 断开保存目录 to remove authorization without deleting exported files.

Prompt for your agent

Using the yxq953/MuseLite app on an Android 11+ device, ask the Agent to save a summary of <source text> as <file name>.md in the authorized document folder. Expected output: the document_save result showing the saved path. Verify that the file appears in the folder you selected in Settings.

Caveat. Android may refuse the storage root, Download root, or Android/data as the folder, so pick a subfolder and expect some providers to show only a folder name.

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