Who it is forA developer or sales ops lead who wants to see how the CRM and its agent behave before deploying anything.
The problemReading about an agent-first CRM does not show how the records, tabs and pipeline look in use.
The outcomeThe app runs on localhost:3000 with a believable pipeline loaded, and the API runs on localhost:3001.
What you need first
- Bun and Docker installed
- A Google or Microsoft OAuth client, or your own identity provider set up later under Settings → SSO
- A value for BETTER_AUTH_SECRET and an ALLOWED_SIGN_IN domain or address
- Optional: a Context API key for company brand data and LinkedIn lookups, and a PERPLEXITY_API_KEY for web research
Steps
- Run
git clone https://github.com/trycompai/crm.git && cd crm - Run
cp .env.example .env, then set BETTER_AUTH_SECRET, ALLOWED_SIGN_IN and at least one of Google or Microsoft sign-in values - Run
bun install - Run
docker compose up -d, thenbun run db:deployandbun run db:seed - Run
bun run devand open http://localhost:3000
Prompt for your agent
Clone the trycompai/crm repo, copy .env.example to .env, set BETTER_AUTH_SECRET and ALLOWED_SIGN_IN, then run bun install, docker compose up -d, bun run db:deploy, bun run db:seed and bun run dev. Report the URL that serves the app. Verify that http://localhost:3001 responds before you finish.
Caveat. Sign-in needs a Google or Microsoft OAuth client, and the README warns that the Google client should be set up in pairs or not at all.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: 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