OpenInstinct
A self-hosted iMessage assistant that operates websites while keeping passwords and payment approvals under user control.
- Source repo
- Merit-Systems/OpenInstinct
- Stars
- ★ 495
- Last updated
- 18d ago
- License
- MIT
- Primary language
- TypeScript
- FA score
- 60/100 · Some gaps
At a glance
- How it runs
- Works with
- Universal · cross-platform
- Cost
- Needs a paid subscription or licence
- Setup effort
- High · needs real infrastructure
- You'll need
- Typical use
- An individual who wants to request a movie booking over iMessage and have a browser reach checkout with the theater, showtime, seat, and total.
- Not a fit if
- Teams requiring production-ready software
- Deployers unwilling to pay for Vercel Pro
- Users who require fully offline operation
- Website
- openinstinct.sh ↗ set on GitHub
- Maintenance
- Commits in the last 30 dayslast commit 2026-11-02+0.6 ★/day over 7 days
- Source review
- 60/100 · Some gaps
What does this agent do, and when should you use it?
OpenInstinct is a personal assistant accessed through iMessage and a signed-in web workspace, with Kernel cloud browsers handling tasks such as ticket booking and shopping. Its encrypted vault and browser autofill let the browser use saved credentials without placing those passwords in the model context. Neon Postgres stores application data and workstreams, while private Vercel Blob storage holds generated keys, persistent memory, and browser images; model traffic goes through Vercel AI Gateway. The primary deployment runs in the user's own Vercel Pro account and connects Linq, Kernel, Neon, and Blob, with optional Google Workspace and Link wallet integrations. The project says it can use any model and documents requirements for non-Vercel hosting, although the guided architecture remains closely tied to Vercel services. The README explicitly says the software is not intended for production use, making it a better fit for technical adopters evaluating an experimental personal automation stack.
A request arrives from iMessage or the authenticated web workspace, after which OpenInstinct uses Eve to coordinate the agent and a Kernel cloud browser to navigate sites, fill forms, and advance transactions. Linq supplies the iMessage line, outbound messaging, and the /eve/v1/linq inbound webhook. Vault values are encrypted before database storage, and browser autofill keeps saved passwords out of the model's context. Before each production agent turn, per-user memory is recalled from private Vercel Blob storage; database workstreams preserve goals, decisions, observations, and unfinished steps across conversations. An optional user-scoped Google OAuth grant supports Gmail, Calendar, and read-only Contacts, with Vercel Connect storing and refreshing tokens. The optional @stripe/link-integrations-eve path can initiate Link wallet approvals, but every spend request still requires user approval in Link and wallet access is unavailable to scheduled workers.
- An individual who wants to request a movie booking over iMessage and have a browser reach checkout with the theater, showtime, seat, and total.
- A self-hoster who wants an assistant to sign into websites without exposing stored passwords to the model context.
- A user who needs goals, decisions, and unfinished personal tasks recalled across separate conversations.
- A Google Workspace user willing to grant OAuth access for Gmail, Calendar, and contact lookup from one assistant.
- A US or Canadian consumer who wants an agent to prepare purchases while retaining per-transaction approval through Link.
- A developer studying how iMessage, cloud browsers, persistent memory, and an encrypted vault can form a personal agent.
Key setup facts
Pulled from the install and usage notes below. The project README has the current values.
- Install / run
pnpm install --frozen-lockfile
- Environment variables
KERNEL_API_KEYAI_GATEWAY_API_KEYBETTER_AUTH_SECRETBETTER_AUTH_URLSECRET_ENCRYPTION_KEYDATABASE_URL- Config files
.env.local.env.examplecompose.yaml- Runtime
- Node.js 24
- Install notes cover
- Docker
How do you install or deploy this agent?
The recommended route is the repository's Deploy with Vercel button using a Vercel Pro team. The guided deployment connects Kernel, Neon, private Vercel Blob storage, Linq, and Vercel AI Gateway. After deployment, complete the one-time Phone Numbers verification in the Linq connector's Vercel Connect settings, open the deployed application, and sign in with a phone number. Link wallet and Google Workspace require separate setup.
Local development requires Node.js 24, pnpm 11.24.0, a running Docker Compose installation, Kernel credentials, and either an AI Gateway API key or an OIDC token from a linked Vercel project:
git clone https://github.com/Merit-Systems/OpenInstinct.git
cd OpenInstinct
pnpm install --frozen-lockfileFor fully manual configuration, copy the environment template and set KERNEL_API_KEY and AI_GATEWAY_API_KEY in .env.local:
cp .env.example .env.local
# Set KERNEL_API_KEY and AI_GATEWAY_API_KEY in .env.local.Start the local stack with:
pnpm devThis starts PostgreSQL from compose.yaml, applies committed migrations, and launches the application. Use pnpm dev:app when intentionally using an externally managed database. A non-Vercel production host must also explicitly provide BETTER_AUTH_SECRET, BETTER_AUTH_URL, SECRET_ENCRYPTION_KEY, DATABASE_URL, DATABASE_URL_UNPOOLED for migrations, and BLOB_READ_WRITE_TOKEN for private Blob storage.
How do you use this agent?
After deployment, complete Linq phone verification, open the web application, and sign in with the verified phone number. Tasks can then be sent to the Linq iMessage number; the optional LINQ_PHONE_NUMBER setting adds a click-to-message shortcut in the workspace. Browser work runs through the background workflow and can draw on persistent memory and workstreams to continue goals and unfinished steps.
To enable Google Workspace, configure a Google Cloud consent screen, enable the Gmail API, Google Calendar API, and People API, create OAuth web credentials, and register https://connect.vercel.com/callback as a redirect URI. Create the connector using top-level clientId and clientSecret fields, set GOOGLE_CONNECTOR_UID, and redeploy. Purchasing additionally requires a registered Stripe Link Agent Wallet application and the LINK_CLIENT_ID, LINK_CLIENT_SECRET, STRIPE_PUBLISHABLE_KEY, and BETTER_AUTH_URL settings. Connect the wallet from the application's Link wallet page; the connection alone does not approve spending, and each purchase must be approved in Link.
What are this agent's strengths and limitations?
- Browser autofill uses saved credentials without putting them in model context, while vault values are encrypted before reaching the database.
- It combines iMessage, a web workspace, cloud-browser execution, persistent memory, and scheduled work in one self-hosted assistant.
- The project can use any model and documents the secrets, database connections, and Blob token needed outside Vercel.
- Vercel Connect stores and refreshes Google tokens, while OpenInstinct retains only the stable user identity needed to request them.
- Link requires approval for each spend request; connecting a wallet does not itself authorize a purchase.
- The project explicitly states that it is not intended for production use.
- The recommended deployment requires Vercel Pro because the minute-by-minute scheduled check exceeds Hobby cron limits.
- The base architecture depends on Kernel, Neon, Linq, Vercel AI Gateway, and private Blob storage, creating a multi-service setup and failure surface.
- Google Workspace requires a separately configured Google Cloud OAuth application; testing grants expire after seven days, and wider distribution may require verification and a security assessment.
- Deleting the private Blob store loses the automatically generated encryption key, while key rotation requires re-encrypting existing vault values.
- Active Eve sessions are deployment-version sensitive: an Eve 0.69 session cannot be moved onto this repository's Eve 0.66.3 deployment.
How does this agent compare with similar options?
Key facts side by side with the most closely related agents.
| Agent | Source review | Form / cost | Stars | Updated | Language | Full support on |
|---|---|---|---|---|---|---|
| OpenInstinct This agent | 60 · Some gaps | Self-hosted servicePaid | ★ 495 | 18d ago | TypeScript | — |
| Iva Personal Assistant | 72 · Some gaps | Chat botFree + model costs | ★ 301 | 1d ago | TypeScript | ChatGPT · Codex |
| MindsHub Cowork | 45 · Major gaps | Web appFreemium | ★ 40k | 28d ago | Makefile | — |
| Rakazo AI Teammates | 80 · Good | Self-hosted serviceFree + model costs | ★ 9.3k | today | TypeScript | — |
How does FollowAgents rate this agent?
Why each dimension lost points
Tests and the README support several concrete safeguards: Google access is user-scoped with restricted Gmail scopes, vault secrets are encrypted before reaching the database and browser autofill keeps passwords out of model context, and each Link spend requires approval in Link. Points were deducted because Gmail and Calendar writes have no extra Eve tool approval and can cause external effects; wallet tool results may contain payment credentials, while the documentation only instructs skills not to repeat them in chat. Dependency evidence is limited to a version manifest and frozen-lockfile CI, with no vulnerability review shown. The code is readable for review, but publisher identity, maintainers, and update responsibility are not verified.
The README, package scripts, and workflow are broadly consistent about Node/pnpm, migrations, deployment, and local startup; supplied tests cover Google clients, duplicate requests, and user scoping. Points were deducted because deployment depends on several hosted services and a release-candidate Eve version, with some features disabled for compatibility; the sample tests do not establish runtime reliability. Linq setup and delivery failures have specific messages, but the packet does not cover all failure paths.
The README describes iMessage assistance, browser tasks, optional Google Workspace and wallet scenarios, and some boundaries for interactive turns, scheduled work, and environments. Points were deducted because audience and scenario coverage is mostly feature description, without a fuller boundary policy or user segmentation. Deployment, local development, and external-database paths are concrete, but Vercel Pro and services such as Kernel, Linq, and Neon constrain environment fit.
The README gives detailed deployment, credential, migration, local-development, and connector instructions, and documents the production-use warning, disabled purchases, legacy-session migration, and OAuth limitations; the MIT license text is complete. Points were deducted because names vary between Local Vault Assistant and OpenInstinct, the package version is 0.0.0, and no regular changelog is shown. Maintenance responsibility is only partly visible from the license copyright name and repository content; maintainers and support channels are not specified. AGENTS.md is contributor and code-change guidance, not product documentation for this score.
The product goal is clear, and browser tasks, iMessage interaction, and password autofill could provide practical value; the README also states deployment costs, the Pro requirement, and service limits. Points were deducted because hosting and service dependencies add cost and upkeep, and the README explicitly says the software is not intended for production. The packet does not establish that benefits outweigh this burden for typical users.
Implementation excerpts, tests, and the README corroborate some important safety and capability claims, including user scoping, Google scopes, migrations, and service configuration; the documentation also states several conditional limitations. Points were deducted because the packet is a sample that omits all skills and primary Agent instructions, leaving many product claims without direct traceability. This is a static assessment and does not execute code or independently verify claims.
- The README says the software is not intended for production; deployment also depends on Vercel Pro and several external services.
- Email sending and calendar events with attendees can run on user request without extra tool approval; grant Google Workspace access carefully.
- Wallet tool results may contain payment credentials. Purchases are currently disabled, but the README describes restoring a compatible extension to re-enable them.
FAQ
What does it cost to operate?
Are passwords or encryption keys exposed to the model?
What permissions does the Google integration receive?
gmail.modify rather than the permanent-delete mail.google.com scope. User-requested email and calendar operations run without an additional Eve tool approval.Can the agent spend money without approval?
Can it run outside Vercel?
Is OpenInstinct open source?
Is OpenInstinct still maintained?
Who makes OpenInstinct?
What is OpenInstinct's official website?
Thanks — we use this to improve the page.