YesPaPa vs githtml

YesPaPa is the human-in-the-loop safety layer for AI coding agents. When an LLM agent or script tries to run a destructive command — like rm -rf, git push --force, or DROP TABLE - YesPaPa intercepts it and sends an approval request straight to your phone. How it works: - Install the YesPaPa CLI on your machine - Scan the pairing QR code with this app (or use offline mode with totp) - Dangerous commands are intercepted and held until you approve Approve with confidence: - One-tap approve or deny from a push notification - See the full command, AI crafted justification, and context before deciding - Approve with a message to guide the agent's next steps - Set Auto-Bypass (grace periods) for trusted command patterns Built on real security: - TOTP-based authentication (RFC 6238) - works offline too - Zero-trust architecture - approvals are cryptographically verified - Tamper-resistant - agents cannot bypass or uninstall their own guardrails(read the docs.yespapa.io for advanced use) - Falls back to manual TOTP codes if the server is unreachable(self hosting included!) Perfect for: - Developers using OpenClaw, Claude Code, Cursor, Copilot workflows, or other AI coding assistants - DevOps engineers running automated scripts on production systems - Teams that need human approval gates for destructive operations in CI/CD pipelines - Anyone who wants a safety net before irreversible commands execute YesPaPa works with any shell on macOS and Linux. The CLI is open-source at github.com/yespapa-cli. Docs available: https://docs.yespapa.io

Your AI docs, finally readable. githtml is the iOS reader for HTML documentation that lives inside your GitHub repos. Documentation your AI coding agent writes, the rendered output, the framework references you keep meaning to read on the train. https://www.apple.com/legal/internet-services/itunes/dev/stdeula/ Connect your GitHub, pick a repo, tap a file. That's it. — WHAT IT DOES • A clean WebKit reader that gets out of the way of your content — the doc's own typography and styling stay intact. • A bottom drawer for capturing notes on any page. Auto-saved per file, exportable as plain text or through the system share sheet. • Browse, Favorites, and Recents — all three grouped by owner so a hundred repos stay organized. • Scroll-aware navigation chrome that fades while you read and comes back the instant you scroll up. • Offline cache — once you've opened a doc, the bytes stay on your device. — WHO IT'S FOR • Developers using Claude Code, Cursor, Codex, or other coding agents that write extensive docs into their repos. • Solo builders maintaining a personal knowledge base in private repos. • Engineers reading framework docs, API references, and internal wikis on the train, on planes, or away from Wi-Fi. • Anyone who has tried to read raw Markdown in the GitHub mobile app and given up. — HOW IT WORKS 1. Sign in with GitHub. The app uses GitHub's official App flow — you pick which repos to grant access to. 2. The permission requested is "Read access to code." Nothing else. No write access, no organization data, no actions. 3. Pick an owner, then a repo, then a file. HTML files are indexed by default. — LOCAL-ONLY, ALWAYS • Your GitHub token lives in the iOS Keychain. • Your notes live in local SwiftData storage. • Your cached docs live in the local file system. • "Delete all data" wipes every byte the app has ever stored, in one tap. • There is no githtml server. The only network calls are to GitHub itself and a tiny token-exchange function that never sees your token after the exchange completes. — WHAT'S NEXT githtml is built around a tight V1: read your repos, take notes, work offline. Future versions will add more ways to navigate and search a large archive of cached docs. Email feedback to shape what ships next.