MIT CLI · Free forever·● Active devs using forgein today
new AI session
Monday
S
I work on a Next.js 15 app. We use Drizzle ORM, never use // TODO comments...
WednesdayAGAIN?
S
I work on a Next.js 15 app. We use Drizzle ORM, never use // TODO comments... [same block]
Friday · New MachineREALLY??
S
I work on a Next.js 15 app. We use Drizzle ORM, never use // TODO comments... [same block, again]
Times you've typed this this month alone
1
▸ forgein eliminates this
How it works
Set up once. Works forever.
01
Install the CLI
One curl command. Works on any machine, any OS. No config files to hand-edit.
curl -fsSL app.forgein.ai/cli/install | bash
02
Write your context once
Your stack, your conventions, your preferences — in plain Markdown. forgein stores it and keeps it in sync.
forgein mem add "We use TypeScript strict mode, pnpm, and Drizzle ORM"
03
Every AI session starts warm
Switch machines, switch AI tools, start a new chat — your context is always already there.
# No more "Let me explain our setup..." ever again
What's actually costing you
You're doing AI's job for it. Every single day.
This isn't a Claude problem. This isn't a ChatGPT problem. It's a universal problem — every AI, every machine, every restart.
Monday — session #1
1
context paste
S
I work on a Next.js 15 monorepo. We use Drizzle ORM, TypeScript strict, pnpm workspaces. Never use `any`... [287 chars]
AI
Got it — I know your stack. How can I help?
1 of 3
🔁
Repeating yourself
Same context block, different session. AI resets every time. You don't.
›auto-injected at session start
🖥
Starting over on new machines
Switch machines and your AI goes cold. Rebuild from scratch on a deadline.
›one command pulls your full context
⌨️
Typing too much
Three paragraphs of setup before you can ask a single question.
›zero setup per session — context loads itself
🔗
Context locked to one tool
Your Claude setup is perfect. ChatGPT knows nothing. Copilot knows nothing. Each tool starts cold.
›one context works in all 7 tools simultaneously
🗂
Managing your own memory
12 open tabs. Which one had the architecture decision? You're the filing system.
›context lives in organized files, not chat history
See what you've been repeating
Paste your context. See what's worth remembering.
Every session you retype the same stack, conventions, and constraints. forgein extracts what's permanent and files it away — so you never have to say it again.
● What you paste every session
I work on a React + TypeScript project. We use pnpm workspaces, Vite, and Zustand for state management. React Query for all data fetching — never fetch in components directly.
Always prefer functional components and hooks, never class components. Avoid useEffect for data fetching. Use explicit types everywhere, no any.
We deploy on Vercel. Branch naming: feat/, fix/, chore/.
This sprint we're building the settings page (PR #234 is in review). The deadline is this Friday. We shipped the auth refactor last week.
✓ What forgein saves forever
UNIVERSAL — all projects
React + TypeScript, pnpm workspaces, Vite
Zustand for state · React Query for data — never fetch in components
Functional components + hooks only, no class components
No useEffect for data fetching · Explicit types, no any
Generate .cursorrules and .windsurfrules directly from your forgein context. No script required — open Contexts in the dashboard, click the adapter button, paste the output into your repo root.
File adapters export a snapshot you paste into each tool. The forgein MCP server goes further — Cursor, Claude Desktop, Windsurf, and Zed connect directly at api.forgein.ai/api/adapters/mcp. Update a memory file and every tool session sees it immediately. No re-export, no paste.
~/.cursor/mcp.json
// add forgein to your MCP client
{
"mcpServers": {
"forgein": {
"url": "https://api.forgein.ai/api/adapters/mcp",
"headers": {
"Authorization":
"Bearer fg_..."
}
}
}
}
⚡
Always live
Resources and prompts are fetched at session time — not exported once and left to go stale.
⬡
Auto-discoverable
/.well-known/mcp publishes the server URL and auth config. Compatible tools connect without manual setup.
Invite a colleague. You both get Home context free.
Home context is normally part of the Pro plan — a separate AI memory for side projects and personal use. Invite one person who signs up, and you both unlock it for free, forever.