Documentation
Vyre IDE Documentation
Complete guide to Vyre IDE. Learn how to set up your workspace, collaborate effectively with your team, use AI workflows safely, and integrate with your existing tools.
Getting Started
Create your first workspace
Sign up for free, set up your first workspace, and connect your codebase in under 5 minutes.
Install and configure
Download Vyre IDE for your OS, connect your GitHub account, and configure AI models.
Invite your team
Add team members, set permissions, and enable controlled collaboration across your codebase.
Configure AI models
Connect OpenAI, Claude, Gemini, Mistral, or local LLMs. Manage API keys and usage budgets.
Team Collaboration
Vyre IDE is built from the ground up for team development. Enable your team to work together with zero friction.
Live pair programming
Code together with controlled sessions, shared chat, and integrated code review.
Shared sessions
Create temporary or persistent sessions for pair programming, mob programming, or knowledge transfer.
Role-based workflows
Assign roles (Owner, Editor, Viewer, AI Assistant) to control what team members can do.
Code review integration
Review pull requests directly in Vyre IDE with AI-suggested improvements and team discussions.
Async collaboration
Leave comments, suggestions, and AI-generated code for teammates across time zones.
AI Workflow Patterns
Proven patterns for using AI to accelerate development across planning, implementation, testing, debugging, and documentation.
Planning with AI
Use AI to brainstorm architecture, decompose tasks, and generate project scaffolds.
Implementation acceleration
Leverage AI for code generation, refactoring suggestions, and boilerplate reduction.
Test-driven development
Generate test suites, fixtures, and mock data. Use AI to fix failing tests faster.
Debugging & optimization
AI-assisted debugging, performance profiling suggestions, and optimization recommendations.
Documentation generation
Auto-generate API docs, README files, inline comments, and technical specifications.
Security & Privacy
Vyre IDE prioritizes code security and privacy with beta controls that keep model context, ignored files, and hosted sessions understandable.
Data encryption
Hosted endpoints use encrypted transport. Local workspace protection follows the user's OS and storage configuration.
Identity & access control
OAuth 2.0 authentication via GitHub, GitLab, or email. Fine-grained role-based access control.
Workspace isolation
Each workspace is isolated. Team members only see what they're granted access to.
AI model privacy
Only selected context should be sent to the configured model provider. Product-improvement data sharing is opt-in.
Session management
Automatic session timeouts, device fingerprinting, and suspicious login alerts.
Audit logs
Team admins can review who accessed what, when, and which AI models were used.
Integrations
Connect Vyre IDE to your favorite tools and AI models. Native support for GitHub, GitLab, and major AI providers.
GitHub
Clone repos, push/pull changes, and manage pull requests directly in Vyre IDE.
GitLab
Full GitLab integration for merge requests, CI/CD pipelines, and project management.
Gitea
Self-hosted Git support for teams using internal Git servers.
OpenAI API
Use GPT-4, GPT-3.5-turbo, and other OpenAI models for code generation.
Anthropic Claude
Access Claude Opus, Sonnet, and Haiku for advanced reasoning and code tasks.
Google Gemini
Integrate Gemini Pro for multimodal AI capabilities in your coding workflow.
Mistral
Use Mistral models for efficient, open-source AI code generation.
Ollama
Run local LLMs via Ollama for private, on-device AI code assistance.
Frequently Asked Questions
Vyre IDE has a free tier for individuals and teams. Paid plans add higher usage limits, premium model capacity, team administration, and priority support.
AI usage depends on the plan and model path you choose. Vyre also supports bring-your-own-key workflows on paid plans for teams that want to use their own provider accounts.
Private project files are not used for Vyre product training. Selected context and prompts may be sent to your configured model provider, and ignored files should stay excluded.
Core desktop editing can work locally, but collaboration, account, and hosted AI features require internet access. Local model workflows can use providers such as Ollama when configured.
Use the migration guides for Cursor, Windsurf, Zed, JetBrains, Kiro, Roo Code, and related tools. Most pilots should start with one real project before a team-wide rollout.
Need more help?
Our documentation is always growing. Check back regularly for new guides, tutorials, and best practices.