KO
|
EN
gitlite — search
Search
#javascript
#python
#hacktoberfest
#react
#ai
#typescript
#llm
#go
#golang
#android
#machine-learning
#rust
#deep-learning
#linux
doit
★ 15
Open GitHub ↗
doit — AI task agent (iOS + Supabase + runner)
Download README (.md)
Explore Similar Repositories
pi-deepseek-cache
:
Optimize DeepSeek prefix cache hit rates — reduce API input costs by 95%+ in multi-turn coding sessions
boss-zhipin-helper
:
一个 Chrome 扩展，辅助 BOSS 直聘求职流程。支持 AI 生成打招呼语和回复消息、岗位管理、简历解析、数据面板等功能。数据纯本地存储。
claude-code-termux
:
Run Claude Code natively on Termux/Android (aarch64) — launcher package that downloads + ELF-patches Anthropic's linux-arm64 build
SejongUnivMobile
:
비공식 세종대학교 통합 모바일 앱.
AK3
:
Xiaomi Kernels with KernelSU & SUSFS
// repository documentation
Was this content helpful?
★ 0
(0 ratings)
Select Rating:
★
★
★
★
★
Submit Feedback
Recent Feedback
×
Download README
Do you want to download the
README.md
file for
doit
?
Download (.md)
# doit An iOS GUI for [Hermes Agent](https://hermes-agent.nousresearch.com/docs/). Create a todo, hand it to an agent, and watch the work stream back into the app in real time. ## Ways To Use Doit Doit is being shaped around several operating models: | Path | Status | Who it is for | | --- | --- | --- | | Hosted Doit / managed Hermes | Works today | Users who want a batteries-included app experience with the managed backend | | Bring your own Hermes connector | Developer preview | Users who want the app as a GUI over Hermes on their own VPS, home server, or Tailscale node | | Fork and self-host | Works for technical operators | Developers who want their own Supabase/control plane, runner, Hermes setup, and app build | | Direct Hermes endpoint | Future/advanced | Users with a secure remote Hermes endpoint | See [`docs/hosted-doit.md`](docs/hosted-doit.md), [`docs/byo-connector.md`](docs/byo-connector.md), and [`docs/self-host.md`](docs/self-host.md). ## Trust Model Hosted Doit is **user-isolated and privacy-minimized, but not end-to-end encrypted**. The hosted runner must process task content to execute work, but routine operator tooling uses aggregate and pseudonymous operational data by default instead of exposing task prompts tied to user identity. BYO connector mode moves Hermes execution and profile files to user-owned infrastructure. Full self-hosting gives the strongest data control because you own both the control plane and execution unit. See [`docs/security-model.md`](docs/security-model.md). ## Architecture ``` iOS (SwiftUI, Sign in with Apple) | v Supabase (managed) ............... Auth + Postgres + Realtime + Edge Function ^ | Runner / connector ............... watches Supabase -> drives Hermes -> sends APNs | v Hermes Gateway ................... one profile per user, isolated memory + OAuth | v Composio Connect (MCP) ........... managed OAuth for Gmail, Calendar, Slack, ... ``` - In hosted mode, one operator VM runs the runner and many Hermes profiles. Each user gets a Hermes **profile** with its own API server port, memory, and OAuth connections, running as a `hermes@<profile>` systemd template instance. - The **runner** is the only custom backend; it's outbound-only (no public port). It runs a bounded worker pool (multiple todos at once, across and within users) and an automated provisioner: new users redeem an **invite code** in the app and their agent is built end-to-end with no manual steps. - In BYO mode, the runner/connector plus Hermes execution unit move onto user-owned infrastructure while the first MVP keeps the iOS realtime contract through hosted Supabase sync. - Real-world actions (sending email, etc.) go through **Composio Connect** so we never build OAuth or store tokens ourselves. See [`docs/architecture.md`](docs/architecture.md) for the full architecture overview. ## Layout ``` doit/ |-- ios/ SwiftUI app (Xcode project) |-- runner/ Python worker: Supabase -> Hermes /v1/runs -> APNs |-- hermes/ Deploy config + setup runbook (NOT Hermes source) |-- supabase/ SQL migrations + Edge Functions ``` ## Quickstart Decision Tree - **I want the batteries-included path**: use the app out of the box with the managed backend. See [`docs/hosted-doit.md`](docs/hosted-doit.md). - **I want to run the whole stack myself**: configure iOS, Supabase, runner, and Hermes. See [`docs/self-host.md`](docs/self-host.md). - **I want the app to control my existing Hermes**: read [`docs/byo-connector.md`](docs/byo-connector.md). This path is a developer preview for hosted-sync BYO. It includes the in-app pairing flow, connector command, and links to [Hermes Agent docs](https://hermes-agent.nousresearch.com/docs/) for gateway-side troubleshooting. - **I want to contribute code**: start with [`CONTRIBUTING.md`](CONTRIBUTING.md) and [`docs/task-realtime.md`](docs/task-realtime.md). ## Required Accounts For Self-Hosting | Service | Purpose | | --- | --- | | Apple Developer | Sign in with Apple and APNs push | | Supabase | Auth, DB, Realtime, Storage, Edge Functions | | Cloud VM provider | Hosted runner + Hermes profiles | | Nous Portal / OpenRouter | LLM access for Hermes runs | | Composio | OAuth integrations such as Gmail, Calendar, Slack | | Browserbase | Managed browser sessions for Hermes and browse.sh skills | ## Configuration The iOS app reads Supabase, waitlist, signing team, and bundle identifiers from `ios/doit/Config/Base.xcconfig`, which optionally includes the ignored `ios/doit/Config/Local.xcconfig`. To self-host or run a fork: ```bash cp ios/doit/Config/Local.example.xcconfig ios/doit/Config/Local.xcconfig ``` Then fill in your own Supabase and Apple values. The batteries-included hosted build uses a private local/CI config with the managed Doit values; those values are not meant to be committed to the public repo. See [`docs/configuration.md`](docs/configuration.md) for `.xcconfig`, `.env`, Supabase, APNs, and secret-handling details. ## Documentation | Document | Purpose | | --- | --- | | [`docs/architecture.md`](docs/architecture.md) | Control plane vs execution unit | | [`docs/configuration.md`](docs/configuration.md) | App config, env files, and secrets | | [`docs/security-model.md`](docs/security-model.md) | Hosted/BYO/self-host privacy model | | [`docs/hosted-doit.md`](docs/hosted-doit.md) | Managed app and hosted backend path | | [`docs/byo-connector.md`](docs/byo-connector.md) | BYO Hermes connector path and limits | | [`docs/self-host.md`](docs/self-host.md) | Full fork/self-host setup outline | | [`docs/task-realtime.md`](docs/task-realtime.md) | iOS realtime contract | | [`docs/apns.md`](docs/apns.md) | Push notification setup | | [`docs/local-admin-dashboard.md`](docs/local-admin-dashboard.md) | Operator admin dashboard | ## Security And Contributing Report vulnerabilities privately; see [`SECURITY.md`](SECURITY.md). Before contributing, read [`CONTRIBUTING.md`](CONTRIBUTING.md). This project is licensed under the MIT License; see [`LICENSE`](LICENSE). ## Realtime contract (READ THIS BEFORE TOUCHING THE iOS LIST OR DETAIL VIEW) How a task ends up on screen after the agent does work is documented in [`docs/task-realtime.md`](docs/task-realtime.md). The short version: - The runner writes Postgres rows. - Supabase Realtime publishes those changes to the iOS client. - `TodoRealtimeHub` (in `ios/doit/doit/Supabase/TodoRealtimeHub.swift`) pulls the row id out of the payload and hands it to `TodoStore`. - `TodoStore` (in `ios/doit/doit/Stores/TodoStore.swift`) is the single app-scoped owner of task / cron / interaction / artifact state. Views observe it; views do NOT keep their own `@State` copies. - APNs is a backup channel for when the app isn't running. It is not the primary path for in-app updates. If you (or another agent) are about to add `@State private var todos: [Todo]` to a view, or a `Timer` that refetches the list every few seconds, stop and re-read the doc — that pattern is exactly what the store exists to prevent and it is the reason the list previously stopped updating after the prep pass.
