# AI use cases for Apeireth (Apeireth/Apeireth) Repo: [Apeireth/Apeireth](https://github.com/Apeireth/Apeireth) | Use cases: 3 | Page: https://dedupedai.com/use-cases/apeireth-apeireth/ Apeireth is a Rust companion app that remembers personal details on your own machine and asks for your approval before any side effect. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Run a private companion that remembers your details: https://dedupedai.com/use-cases/apeireth-apeireth/run-a-private-memory-companion/ - Hand the companion a task and approve each step: https://dedupedai.com/use-cases/apeireth-apeireth/delegate-tasks-with-approval-cards/ - Build the companion from source and audit its claims: https://dedupedai.com/use-cases/apeireth-apeireth/build-and-audit-apeireth-from-source/ ## How to run a private companion that remembers your details with Apeireth Repo: [Apeireth/Apeireth](https://github.com/Apeireth/Apeireth) | Difficulty: Beginner | Time: 15 minutes | Basis: From the README Install the desktop companion, add a provider key, and keep memories on your own machine. **Who it is for:** A person who wants a personal assistant that remembers small everyday details and keeps them on their own computer. **The problem:** Most chat tools forget what you said earlier, and you have no clear view of what they keep about you. **The outcome:** A running desktop companion that stores memories locally, which you can read, export, or wipe. ### Steps 1. Download the Windows installer from the Releases page and check the attached SHA256 value. 2. Double-click the installer and open the companion desktop icon. 3. Pick a provider, enter your key, and say something to start a conversation. 4. Open Settings and choose "Character & Memory" to review what it has kept. ### Prompt to paste into your agent ```text Using the Apeireth repo at , confirm the companion starts on and answers a test message. Expected output: a reply in the chat window. Verify that the memory section in Settings lists the test message. ``` ### Caveat The care rule face is OFF by default and needs an explicit environment variable to turn on, so do not expect scheduled care messages out of the box. Risk, credentials: Your provider key is stored in the OS keyring when available, but the file backend is plaintext and the fallback backends do no zeroization, so check where your key is saved. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/apeireth-apeireth/run-a-private-memory-companion/ ## How to hand the companion a task and approve each step with Apeireth Repo: [Apeireth/Apeireth](https://github.com/Apeireth/Apeireth) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Ask it to handle something for you, then approve or reject each side effect before it runs. **Who it is for:** A busy person who wants the companion to act on routine tasks but needs a clear yes before anything changes files, messages, or money. **The problem:** Letting an assistant act on your files or accounts without a checkpoint is risky, and you need a record of what was approved. **The outcome:** Tasks run only after your explicit approval, with one approval covering exactly one side effect. ### Steps 1. Open the companion desktop window and choose the quick action "handle something for me". 2. Describe the task in plain words and send it. 3. Read each approval card that appears and check the exact action before you approve it. 4. If a task shows Failed, review it yourself, since the README says Failed is judged only by a human and is never auto-retried. ### Prompt to paste into your agent ```text In the Apeireth repo at , check that a delegated task on pauses at an approval card before any side effect. Expected output: a pending approval with no change made yet. Verify that the target file is unchanged until you approve. ``` ### Caveat Shell execution is refused by default outside Windows, and Linux and macOS get process limits only with no file or network isolation, so keep delegated tasks to Windows unless you accept that gap. Risk, credentials: Tasks that touch messages or money run through approval cards, but you still need to confirm the account and target before you say yes. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/apeireth-apeireth/delegate-tasks-with-approval-cards/ ## How to build the companion from source and audit its claims with Apeireth Repo: [Apeireth/Apeireth](https://github.com/Apeireth/Apeireth) | Difficulty: Advanced | Time: 1 hour | Basis: From the README Compile the CLI and desktop app, then check the README's honest boundaries against the code. **Who it is for:** A developer or reviewer who wants to verify the project's claims before trusting it with personal data. **The problem:** A companion that handles private memory should be checked against its own stated limits, not taken on faith. **The outcome:** A local build of the CLI and desktop app, plus a written list of which boundaries you confirmed in code. ### Steps 1. Run `winget install Git.Git`, then follow INSTALL.md to install rustup 1.97.1 and VS Build Tools 2022. 2. Run `cargo build --release -p apeireth-cli` from the repo root. 3. Run `cd frontend/companion-desktop && pnpm install && pnpm tauri build`. 4. Search the source for `STUB_MODE`, `not_assembled`, and `/v1/ws` to confirm the WebSocket and SDK boundaries the README describes. (inferred, check the README) ### Prompt to paste into your agent ```text In the Apeireth repo at , build the apeireth-cli crate and then search for STUB_MODE and the /v1/ws route. Expected output: a successful release build and the file locations of each match. Verify that the SDK stub and the missing WebSocket route match the README's Honest boundaries section. ``` ### Caveat The README's badge counts are hand-maintained snapshots, so confirm each boundary in the code rather than trusting the numbers. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/apeireth-apeireth/build-and-audit-apeireth-from-source/