forgein — AI Context Manager
Stop re-explaining yourself to every AI tool.
forgein is a context layer for developers. You define your tech stack, conventions, and project context once — and forgein syncs it everywhere: GitHub Copilot, Cursor, Windsurf, Claude Code, and ChatGPT.
This VS Code extension is the fastest way to keep Copilot (and every other AI you use) in sync with what you're actually working on.
What it does
- Fetches your active forgein context from app.forgein.ai
- Writes it to
.github/copilot-instructions.md — the file GitHub Copilot reads automatically
- Optionally also writes
.cursorrules and .windsurfrules for Cursor and Windsurf
- Shows your active context in the VS Code status bar
- Auto-syncs every time you open a workspace (configurable)
Works with
| Tool |
How |
| GitHub Copilot |
.github/copilot-instructions.md |
| Cursor |
.cursorrules |
| Windsurf |
.windsurfrules |
| Claude Code |
via forgein ctx CLI (separate install) |
| ChatGPT |
context export from dashboard |
Quick start
1. Install the extension
Search for forgein in the VS Code Extensions panel, or install from the command line:
code --install-extension forgeinai.forgein
2. Set your API token
Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run:
Forgein: Set API Token
Get your token at app.forgein.ai/settings. Tokens look like fg_....
3. Sync your context
Run Forgein: Sync Context from the Command Palette, or click the forgein status bar item at the bottom of VS Code. Your context files will be written immediately.
Commands
| Command |
Description |
Forgein: Sync Context |
Fetch and write context files to the current workspace |
Forgein: Set API Token |
Store your forgein API token securely |
Forgein: Switch Context |
Pick a different forgein context |
Forgein: Open Dashboard |
Open app.forgein.ai in your browser |
Settings
| Setting |
Type |
Default |
Description |
forgein.autoSync |
boolean |
true |
Sync automatically when a workspace opens |
forgein.writeRules |
boolean |
true |
Also write .cursorrules and .windsurfrules |
forgein.projectPath |
string |
"" |
Override the project path sent to the API (defaults to workspace folder name) |
Files written
When you sync, forgein writes these files to your workspace root:
.github/
copilot-instructions.md ← GitHub Copilot reads this automatically
.cursorrules ← Cursor reads this automatically
.windsurfrules ← Windsurf reads this automatically
These files are generated from your forgein context, which you manage at app.forgein.ai. Add them to .gitignore if you don't want to commit them, or commit them to share context with your team.
Status bar
The forgein status bar item appears at the bottom right of VS Code:
| State |
Meaning |
$(key) forgein: set token |
No API token — click to set one |
$(sync~spin) forgein |
Syncing in progress |
$(check) forgein: MyContext · 42 files |
Synced — click to re-sync |
$(warning) forgein: sync failed |
Error — click to retry |
Privacy
- Your API token is stored in VS Code's SecretStorage (OS keychain), never in plain text
- Context files are written locally to your workspace — nothing is sent to forgein from your editor except the project path
- forgein never reads your source code
Feedback & support
