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

How to run a private AI coworker on your own laptop with Open Bot

Start Open Bot locally with Docker and Bun, then chat with a General Assistant that runs on your machine.

Credentials. The OPENAI_API_KEY you enter is stored in your local .env file, so keep that file out of version control.

Who it is forA developer or IT lead evaluating an internal AI assistant who wants to see it run on a laptop before any company rollout.

The problemHosted AI assistants keep data and tool access outside your control, which makes it hard to test how an agent behaves on your own systems.

The outcomeA working Open Bot stack on your machine with the General Assistant answering in the /bot route, running on infrastructure you control.

What you need first

  • Docker, for PostgreSQL and the shipped Bots
  • Bun 1.3 or later
  • A CopilotKit account to run `npx --yes copilotkit@latest login`, or a self-hosted Intelligence deployment
  • An OpenAI API key for the proof-of-concept Bot

Steps

  1. Run cp .env.example .env and then bun install in the cloned repository.
  2. Run npx --yes copilotkit@latest login and npx --yes copilotkit@latest project select, then run bun scripts/setup-learning.ts.
  3. Open .env and set OPENAI_API_KEY, keeping the managed Intelligence URLs from .env.example.
  4. Run bash scripts/start.sh and wait for the health checks to pass.
  5. Open the app on port 3010 and go to /bot, then ask it to open news.ycombinator.com and report the top story.

Prompt for your agent

In the OpenBot repository at <repo-path>, follow the Quick start in README.md to start the stack, then send the message 'Open news.ycombinator.com and tell me the top story' to the /bot route. Report the story title it returns and confirm that the start script printed a passing health check for the API on port 3001.

Caveat. The README says it is alpha software written for a laptop and that `.env.example` sets OPENBOT_SINGLE_USER=true, which admits every request as one administrator until sign-in is configured.

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