Skip to content

[Feature Request] Support Multiple Provider Profiles and GitHub Copilot Integration #952

@joutvhu

Description

@joutvhu

Description

I have been using Void as an open-source alternative to Cursor, and I really appreciate the flexibility it offers. However, to make it a daily driver for professional software engineers, I believe two key features are currently missing:

  • Multiple Accounts/Profiles for a Single Provider: Currently, Void only allows one API Key per provider (e.g., Google Gemini). As a developer, I often need to switch between different accounts (e.g., a personal Google account for side projects and a corporate account for work) to manage quotas and billing separately.

  • GitHub Copilot Support: While Void is a fork of VS Code, it doesn't yet leverage GitHub Copilot as a model provider for its Agent/Chat features. Many of us have active Copilot subscriptions and would love to use it as the "brain" for Void's AI features, similar to how Roo Code or Cursor (via extensions) handles it.

Proposed Solution

1. Multiple Profiles

  • Allow users to create and name multiple "Profiles" within the settings for each provider.

  • Example: Under the Gemini tab, I could add Account_Personal and Account_Work, each with its own API Key.

  • A quick-switch toggle in the Chat/Agent sidebar to select which profile to use for the current session.

2. GitHub Copilot Integration

  • Enable GitHub Copilot as a primary AI Provider.

  • This would allow the Void Agent to use the models provided by the Copilot subscription (like GPT-4o or Claude 3.5 Sonnet) without requiring an additional direct API Key from OpenAI or Anthropic.

Why is this important?

  • Cost Management: Developers need to separate their API usage across different projects/clients.

  • Convenience: Many developers already pay for GitHub Copilot and don't want to pay double for separate API credits if they don't have to.

  • Workflow Efficiency: Switching keys manually in the settings is friction-heavy and prone to errors.

Additional Context

As a Software Engineer who frequently works with technologies like Angular, React, and Flutter, having the ability to switch context and accounts seamlessly would significantly improve my productivity within the Void IDE.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions