DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to test the agent in a laptop chat first with Open Instinct

Run the agent on your laptop and chat with it before you buy any phone line.

Who it is forA developer evaluating the repo who wants to see the agent work before connecting Inkbox or any phone number.

The problemSetting up phone, email and VM services takes time. You want to confirm the agent loop, memory and tools work first.

The outcomeA running local agent that answers chat messages and stores a memory from a single chat line.

What you need first

  • Node 22.19+ and pnpm 10
  • An Anthropic API key (or another Pi provider key)
  • An Inkbox admin API key from inkbox.ai for phone, email and agent-to-agent endpoints
  • A Maritime API key from maritime.sh if you deploy to a VM
  • A Stripe Link OAuth client if you want the agent to pay (review takes about 3 to 5 days)

Steps

  1. Clone and enter the repo: git clone https://github.com/mariagorskikh/open-instinct && cd open-instinct
  2. Enable tooling: nvm use && corepack enable
  3. Install and build: pnpm install && pnpm build
  4. Set your model key: export ANTHROPIC_API_KEY=sk-ant-...
  5. Create a local profile: pnpm instinct init --name "Maria" --phone +14155550100 --email [email protected] --handle maria-instinct
  6. Run pnpm instinct dev in one terminal, then pnpm instinct chat "remember that I like window seats" in another

Prompt for your agent

In the open-instinct repo at <repo path>, follow the laptop quick start from the README with a test name <name>. Expected output: a reply from `pnpm instinct chat` after `pnpm instinct dev` is running. Verify that a follow-up chat asking what you like gets an answer that mentions the saved preference.

Caveat. This path skips iMessage and the VM, so it does not show the phone or deployment behavior that the README describes as beta.

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