VyContext - AI Context for Silicon IP Development

VyContext brings silicon IP awareness to your AI-powered IDE — giving AI assistants structured conventions, metadata, and lifecycle insights for hardware design, directly in VS Code, Cursor, and any MCP-compatible editor. Free tier available.

Build Silicon Like Software
VyContext brings Vyges' metadata-driven conventions into your AI-assisted IDE — helping you design, verify, and reuse silicon IP with the same agility as modern software development.

Keywords: silicon, IP, verification, hardware, RTL, systemverilog, verilog, ASIC, FPGA, AI, MCP, vyges, context, chip design, semiconductor, Cursor, Copilot, Claude Code, Antigravity

🚀 Features

🤖 AI-Aware Context - Provides Vyges silicon IP conventions to AI coding assistants
📦 Modular Contexts (Atomic) - Load only what you need, when you need it
⚡ Fast & Lightweight - <100ms response, minimal memory footprint
🔄 Auto-Sync - Keeps conventions up-to-date automatically
🎯 Tier-Based Access - Basic (free), Pro, Max tiers with JWT authentication
🔒 Secure - HTTPS-only, OAuth 2.0, enterprise-ready infrastructure

💡 What is VyContext?

VyContext connects your AI-powered IDE to the Vyges MCP (Model Context Protocol) Server, which provides:

Core Conventions - Directory structure, naming, file organization
RTL Guidelines - SystemVerilog best practices, coding standards
AI Workflows - Metadata structure, lifecycle management
Synthesis Hints - Optimization guidelines, timing considerations
Verification Patterns - Testbench structure, coverage strategies

Think of it as "documentation that AI assistants understand" - helping you build silicon IP like software.

🎯 Use Cases

For Hardware Engineers

Learn hardware design faster with AI assistance
Get consistent, production-ready code suggestions
Follow industry best practices automatically

For Software Engineers Learning Hardware

Lower barrier to entry for chip design
Familiar software-like conventions
AI-guided learning path

For IP Development Teams

Standardize team workflows
Maintain consistency across projects
Integrate with VyCatalog for full IP lifecycle

📦 Installation

Works with VSCode, Cursor, Windsurf, VSCodium, and other VSCode-based IDEs

From VSCode Marketplace
```
Search: "VyContext"
Click: Install
```

From Command Line

code --install-extension vyges.vycontext
# Or for Cursor:
cursor --install-extension vyges.vycontext

Manual Installation

# Download vycontext-0.2.0.vsix
code --install-extension vycontext-0.2.0.vsix
# Or for Cursor:
cursor --install-extension vycontext-0.2.0.vsix

🤖 How the AI gets Vyges conventions

The extension fetches context from the Vyges MCP server and caches it. It then writes critical conventions into your workspace so the IDE’s AI uses them automatically (IDEs don’t read extension storage directly).

Cursor

File: .cursor/rules/vyges-vycontext.mdc
When: After each context load or refresh (and on startup if context is loaded).
Cursor loads rules from .cursor/rules/ at the start of each AI session, so the model follows Vyges conventions without @-mentions. Disable with "vycontext.writeCursorRule": false if you manage Cursor rules yourself.

VS Code (GitHub Copilot)

File: .github/copilot-instructions.md
When: Same as above (after each load/refresh).
VS Code applies .github/copilot-instructions.md to all chat requests in the workspace. If the file already exists, VyContext prepends a Vyges section so your existing instructions are kept. Disable with "vycontext.writeCopilotInstructions": false if you manage Copilot instructions yourself.

Claude Code (VS Code / Cursor / Open VSX)

File: .claude/rules/vyges-vycontext.md
When: Same as above (after each load/refresh).
Claude Code loads modular instructions from .claude/rules/ automatically, so it will use the Vyges conventions without touching your CLAUDE.md. The extension is available on Open VSX (and the VS Code Marketplace), so it works in Cursor, VSCodium, and other VS Code–based IDEs that run Claude Code. Disable with "vycontext.writeClaudeRules": false if you manage .claude/rules yourself.

Antigravity IDE

File: .agent/rules/vyges-vycontext.md
When: Same as above (after each load/refresh).
Antigravity loads workspace rules from .agent/rules/ (markdown files). VyContext writes the same conventions there so the Agent follows Vyges rules (dates, repo name, commit style, etc.). Disable with "vycontext.writeAntigravityRules": false if you manage .agent/rules yourself.

OpenClaw and other non-IDE MCP clients

Extension: The VyContext extension does not run inside OpenClaw. OpenClaw is a gateway/CLI (WhatsApp, Telegram, etc. → AI), not a VS Code–based IDE, so it never loads VS Code/Open VSX extensions.
OpenClaw support: If you need VyContext to work with OpenClaw, file a feature request via our contact form.

Content (all four): Mandatory rules for dates (use date command, never guess from files), repository name (use git rev-parse --show-toplevel), Git commit message style, and deprecation of .vyges-ai-context.json. Antigravity rules are limited to 12,000 characters per file; VyContext keeps the written content within that limit.

Deprecation: `.vyges-ai-context.json` (use VyContext only)

The file .vyges-ai-context.json was an early prototype. We now use only the VyContext extension and MCP service for AI context. Do not use or create .vyges-ai-context.json in any repository.

Removing the old file on your Mac

To stop the old file from being used and rely only on VyContext:

Find any .vyges-ai-context.json on your machine (repos, home, or devcontainer):
```
find ~/shiva/github/vyges ~ -name '.vyges-ai-context.json' 2>/dev/null
```
Also check: ~/vyges, ~/.vyges, and inside any repo under your workspace.
Delete each file you find (after confirming it’s the old prototype, not something else):
```
rm -f /path/to/.vyges-ai-context.json
```
If it’s in a Git repo, commit the removal: git rm .vyges-ai-context.json then commit.
Ensure VyContext is the only source of context:
- Install the VyContext extension if you haven’t (VS Code: code --install-extension vyges.vycontext; Cursor: cursor --install-extension vyges.vycontext).
- Open a Vyges workspace (e.g. a repo with vyges-metadata.json), run VyContext: Refresh Context from the Command Palette so the extension writes .cursor/rules/vyges-vycontext.mdc (Cursor) and/or .github/copilot-instructions.md (VS Code Copilot).
- Don’t add rules or context that reference .vyges-ai-context.json.
Vybox-Lite / devcontainers: If your devcontainer or Vybox-Lite image still downloads .vyges-ai-context.json (e.g. in the Dockerfile), update that image to stop fetching it and rely on the VyContext extension inside the container instead.

After this, only VyContext (extension + MCP) will provide Vyges AI context.

⚙️ Configuration

VyContext works out-of-the-box with sensible defaults. Optional settings:

{
  "vycontext.cacheEnabled": true,                                 // Local caching
  "vycontext.autoUpdate": true,                                   // Auto-refresh
  "vycontext.writeCursorRule": true,                              // Write .cursor/rules/vyges-vycontext.mdc (Cursor)
  "vycontext.writeCopilotInstructions": true,                     // Write .github/copilot-instructions.md (VS Code Copilot)
  "vycontext.writeClaudeRules": true,                             // Write .claude/rules/vyges-vycontext.md (Claude Code)
  "vycontext.updateInterval": 86400,                              // Update interval (24 hours)
  "vycontext.debugMode": false,                                   // Enable debug logging
  "vycontext.useAtomicContexts": false                            // Use atomic context loading (experimental)
}

All Configuration Options

Setting	Default	Description
`cacheEnabled`	`true`	Cache context locally. Disable if you want to always fetch fresh context from the server.
`autoUpdate`	`true`	Auto-refresh context files on startup and at regular intervals. Disable if you prefer manual updates only.
`updateInterval`	`86400`	Update interval in seconds (default: 24 hours). Minimum is 3600 (1 hour).
`debugMode`	`false`	Enable debug logging. Check the Output panel (View > Output) and select 'VyContext' from the dropdown.
`writeCursorRule`	`true`	Write `.cursor/rules/vyges-vycontext.mdc` so Cursor's AI loads Vyges conventions. Set to `false` if you manage Cursor rules yourself.
`writeCopilotInstructions`	`true`	Write `.github/copilot-instructions.md` so VS Code + GitHub Copilot apply Vyges conventions to chat. If the file exists, a Vyges section is prepended. Set to `false` if you manage it yourself.
`writeClaudeRules`	`true`	Write `.claude/rules/vyges-vycontext.md` so Claude Code (VS Code / Cursor / Open VSX) loads Vyges conventions as modular instructions. Set to `false` if you manage `.claude/rules` yourself.
`useAtomicContexts`	`false`	Use atomic context loading (experimental). Loads multiple small context files instead of one large file.
`notifications`	`{...}`	Notification preferences for different events (onLogin, onLogout, onRefresh, onError, etc.)

Note: MCP server URL and authentication settings are automatically configured and not user-configurable. Service tier is auto-detected from your login.

🎮 Commands

Access via Command Palette (Cmd+Shift+P or Ctrl+Shift+P):

Vyges: Login - Authenticate with your Vyges account (opens profile.services.vyges.com)
Vyges: Logout - Sign out and return to unauthenticated mode
Vyges: Show Status - View extension status and authentication
Vyges: Refresh Context - Manually refresh context
Vyges: Set as Primary - Make VyContext the primary MCP provider

💡 First time? Register your free account at profile.services.vyges.com before using Login command.

📚 Context Tiers

Tier	Includes	Access
Basic	Core conventions, RTL guidelines, AI workflows	Free (registration required)
Pro	Basic + Synthesis, verification, catalog integration	Subscription
Max	Pro + Security, standards, full IP lifecycle	Enterprise

📝 Register for free → https://profile.services.vyges.com
🏠 VyContext Product Page → https://vyges.com/products/vycontext/
📖 Full Documentation → Vyges Documentation

🏗️ Architecture & Performance

VSCode Extension (You)
   ↓ OAuth 2.0 + JWT Authentication
   ↓ HTTPS (Encrypted)
agent.services.vyges.com (MCP Server)
   ↓ Tier-Based Context Delivery
Modular Context Files
   • Core conventions
   • RTL guidelines
   • AI workflows
   • Synthesis hints
   • Verification patterns

Metric	Value
Load Time	<100 ms (cached: <10ms)
Memory Usage	~10 MB
Server Response	<100ms
Connection	HTTPS-only, SSL

Benefits:

✅ Smaller than monolithic context files
✅ Faster loading with smart caching
✅ Better AI memory retention
✅ Tier-based access control

🚀 Getting Started

Register for Free Account

Visit: https://profile.services.vyges.com
Create your free account (required for all tiers, including Basic)

Install Extension

VSCode → Extensions → Search "VyContext"

Login to Extension

Cmd+Shift+P → "Vyges: Login"
Authenticate with your account

Start Coding

Your AI assistant now has Vyges context!

🔍 Try it now — Register free at profile.services.vyges.com, install VyContext, and bring Vyges context into your AI assistant within minutes. No credit card required.

💻 Examples

Using with AI Assistants

When you ask your AI assistant:

"Using Vyges conventions, create a SystemVerilog module for an AXI interface"

VyContext provides:

Vyges directory structure
Naming conventions
Module template
Documentation requirements
Metadata structure

Result: Production-ready, standardized code.

Project Structure

VyContext helps AI generate:

my_ip/
├── rtl/               # RTL source code
│   └── my_module.sv
├── tb/                # Testbenches
│   └── my_module_tb.sv
├── docs/              # Documentation
│   └── my_module.md
└── metadata.json      # IP metadata

🔐 Security & Privacy

HTTPS Only - All communication encrypted with SSL/TLS
OAuth 2.0 + JWT - Secure authentication via AWS Cognito
No Source Upload - VyContext never uploads your source code or proprietary design data
Local Caching - Context stored locally in encrypted storage
Privacy-Focused - Minimal data collection for service improvement only
Enterprise-Grade - Production infrastructure with 99.9% uptime SLA

🤝 IDE Compatibility

Supports VSCode, Cursor, Windsurf, VSCodium, and other VSCode-based IDEs

Works seamlessly with:

VSCode - Microsoft's code editor
Cursor - AI-first code editor
Windsurf - Codeium's AI IDE
VSCodium - Open source VSCode
GitHub Copilot - AI pair programmer
Claude Code - Anthropic's coding assistant
Any MCP-compatible tool - Standard protocol

📖 Documentation

Website: https://vyges.com
VyContext Product Page: https://vyges.com/products/vycontext/
Docs: https://vyges.com/docs
Community: https://github.com/vyges/community

🐛 Issues & Support

Troubleshooting

Login Issues in Your IDE?

If you experience authentication problems:

First Try: Use "Vyges: Logout" then "Vyges: Login" again
Still Having Issues? File a support request: https://vyges.com/contact/ or https://github.com/vyges/community/issues

OAuth Authentication Flow:

VyContext uses OAuth 2.0 with PKCE (Proof Key for Code Exchange) for secure authentication:

Click "Vyges: Login" in your IDE
Browser Opens - Authenticate with your Vyges account at https://profile.services.vyges.com
Automatic Redirect - The browser redirects back to your IDE with an authorization code
Token Exchange - VyContext automatically exchanges the code for JWT tokens
Secure Storage - Tokens are stored securely in your IDE's encrypted storage

Note: If the OAuth flow fails, try logging out and logging in again. The extension uses a custom URI scheme (cursor:// or vscode://) for the OAuth callback, which requires proper IDE configuration.

Most common fixes:

✅ Ensure you're registered at https://profile.services.vyges.com (required for all tiers)
✅ Check your IDE allows external browser authentication
✅ Disable VPN/proxy that might block OAuth redirects
✅ Try a different browser (Chrome, Firefox, Safari, Edge)

Community Support

Issues: https://github.com/vyges/community/issues
Discussions: https://github.com/vyges/community/discussions
Contact: https://vyges.com/contact/

📜 License

This software is proprietary and confidential. Unauthorized copying, distribution, or use of this software, via any medium, is strictly prohibited.

🌟 About Vyges

Vyges is building tools to make silicon IP development as accessible as software development.

Build silicon like software → Standardized context + Reusable IP conventions

Publisher: Vyges — Metadata-driven infrastructure for reusable silicon IP.

Made with ❤️ by Vyges

Visual Studio Marketplace | Open VSX Registry | GitHub | Website

VyContext - Vyges AI Context Provider

Vyges