**Context**: Integration and verification of various AI CLI tools as AISBF providers
**Goal**: Expand AISBF's provider ecosystem by supporting popular CLI tools and verifying compatibility with existing services
## Planned Features
---
## 🔥 HIGH PRIORITY (Implement Soon)
### 1. Gemini CLI Integration
**Estimated Effort**: 2-3 days
**Expected Benefit**: Direct access to Google's Gemini models via official CLI
**ROI**: ⭐⭐⭐⭐ High
**Description**: Integrate Google's official Gemini CLI tool as a provider type in AISBF, allowing users to leverage their Gemini CLI credentials and configurations.
**Tasks**:
-[] Research Gemini CLI authentication and API structure
-[] Create `GeminiCLIProviderHandler` class in `aisbf/providers.py`
-[] Implement CLI command execution and response parsing
-[] Add configuration schema to `config/providers.json`
-[] Test with various Gemini models (Flash, Pro, Ultra)
-[] Add streaming support
-[] Update documentation with setup instructions
-[] Add dashboard UI support for Gemini CLI configuration
**Configuration Example**:
```json
{
"gemini-cli":{
"id":"gemini-cli",
"name":"Gemini CLI",
"type":"gemini-cli",
"api_key_required":false,
"gemini_cli_config":{
"cli_path":"/usr/local/bin/gemini",
"config_file":"~/.config/gemini/config.json"
}
}
}
```
---
### 2. Qwen CLI Integration
**Estimated Effort**: 2-3 days
**Expected Benefit**: Access to Alibaba's Qwen models via CLI
**ROI**: ⭐⭐⭐⭐ High
**Description**: Integrate Qwen CLI tool as a provider type, enabling access to Qwen's language models through their official command-line interface.
**Tasks**:
-[] Research Qwen CLI authentication and API structure
-[] Create `QwenCLIProviderHandler` class in `aisbf/providers.py`
-[] Implement CLI command execution and response parsing
-[] Add configuration schema to `config/providers.json`
-[] Test with available Qwen models
-[] Add streaming support if available
-[] Update documentation with setup instructions
-[] Add dashboard UI support for Qwen CLI configuration
**Description**: Integrate GitHub Copilot CLI as a provider type, allowing users to access Copilot's models through their GitHub authentication.
**Tasks**:
-[] Research GitHub Copilot CLI authentication flow
-[] Create `CopilotCLIProviderHandler` class in `aisbf/providers.py`
-[] Implement GitHub OAuth integration if needed
-[] Implement CLI command execution and response parsing
-[] Add configuration schema to `config/providers.json`
-[] Test with Copilot models
-[] Add streaming support
-[] Handle GitHub authentication tokens
-[] Update documentation with setup instructions
-[] Add dashboard UI support for Copilot CLI configuration
**Configuration Example**:
```json
{
"copilot-cli":{
"id":"copilot-cli",
"name":"GitHub Copilot CLI",
"type":"copilot-cli",
"api_key_required":false,
"copilot_cli_config":{
"cli_path":"/usr/local/bin/github-copilot-cli",
"auth_token":"ghp_xxxxxxxxxxxxx"
}
}
}
```
---
## 🔶 MEDIUM PRIORITY
### 4. Bolt.new Verification
**Estimated Effort**: 1-2 days
**Expected Benefit**: Verify compatibility with Bolt.new service
**ROI**: ⭐⭐⭐ Medium
**Description**: Verify that AISBF can work with Bolt.new (StackBlitz's AI-powered full-stack web development tool) and document any integration requirements.
**Tasks**:
-[] Research Bolt.new API structure and authentication
-[] Test existing AISBF providers with Bolt.new
-[] Identify any compatibility issues
-[] Document integration steps
-[] Create example configurations
-[] Test with various Bolt.new features
-[] Update documentation with Bolt.new integration guide
---
### 5. DeepSeek Verification
**Estimated Effort**: 1-2 days
**Expected Benefit**: Verify compatibility with DeepSeek API
**ROI**: ⭐⭐⭐ Medium
**Description**: Verify that AISBF's existing OpenAI-compatible provider handler works correctly with DeepSeek's API, or create a dedicated handler if needed.
**Tasks**:
-[] Research DeepSeek API structure and authentication
-[] Test with existing OpenAI provider handler
-[] Identify any API differences or incompatibilities
-[] Create dedicated `DeepSeekProviderHandler` if needed
-[] Add configuration example to `config/providers.json`
-[] Test with various DeepSeek models
-[] Document any special requirements or limitations
-[] Update documentation with DeepSeek integration guide
**Configuration Example**:
```json
{
"deepseek":{
"id":"deepseek",
"name":"DeepSeek",
"endpoint":"https://api.deepseek.com/v1",
"type":"openai",
"api_key_required":true,
"api_key":"YOUR_DEEPSEEK_API_KEY"
}
}
```
---
### 6. Rovo Dev CLI Verification
**Estimated Effort**: 1-2 days
**Expected Benefit**: Verify compatibility with Atlassian Rovo Dev CLI
**ROI**: ⭐⭐⭐ Medium
**Description**: Verify that AISBF can integrate with Atlassian's Rovo Dev CLI tool and document the integration process.
**Tasks**:
-[] Research Rovo Dev CLI authentication and API structure
-[] Test existing AISBF providers with Rovo Dev CLI
-[] Identify integration requirements
-[] Create dedicated handler if needed
-[] Add configuration schema
-[] Test with Rovo Dev features
-[] Document integration steps
-[] Update documentation with Rovo Dev CLI guide
---
## 📋 Implementation Notes
### General CLI Integration Pattern
When integrating CLI tools, follow this pattern:
1.**Authentication**: Determine how the CLI tool handles authentication (config files, environment variables, OAuth tokens)
2.**Command Execution**: Use Python's `subprocess` module to execute CLI commands
3.**Response Parsing**: Parse CLI output (JSON, plain text, etc.) into AISBF's standard format
4.**Error Handling**: Handle CLI errors, timeouts, and authentication failures
5.**Streaming**: Implement streaming if the CLI tool supports it (parse output line-by-line)
logger.info(f"Email verification status changed for user {user_id}, logging out session")
request.session.clear()
returnRedirectResponse(url=url_for(request,"/dashboard/login")+"?error=Your email verification status has changed. Please log in again.",status_code=303)
exceptExceptionase:
logger.error(f"Error checking email verification status for user {user_id}: {e}")
# Only check email_verified if verification is required
context={"request":request,"error":"Username can only contain letters, numbers, underscores, hyphens, and dots","config":config.aisbfifconfigandconfig.aisbfelse{}}
)
# Validate username length
iflen(username)<3orlen(username)>50:
returntemplates.TemplateResponse(
request=request,
name="dashboard/signup.html",
context={"request":request,"error":"Username must be between 3 and 50 characters","config":config.aisbfifconfigandconfig.aisbfelse{}}
)
# Validate passwords match
ifpassword!=confirm_password:
returntemplates.TemplateResponse(
request=request,
name="dashboard/signup.html",
context={"request":request,"error":"Passwords do not match"}
context={"request":request,"error":"Passwords do not match","config":config.aisbfifconfigandconfig.aisbfelse{}}
context={"request":request,"error":"This username is already taken. Please choose a different one.","config":config.aisbfifconfigandconfig.aisbfelse{}}
logger.error(f"Failed to send verification email: {e}")
returntemplates.TemplateResponse(
request=request,
name="dashboard/signup.html",
context={"request":request,"message":"Account already exists but not verified. A new verification email has been sent.","config":config.aisbfifconfigandconfig.aisbfelse{}}
)
returntemplates.TemplateResponse(
request=request,
name="dashboard/signup.html",
context={"request":request,"message":"Account already exists but not verified. A new verification email has been sent."}
logger.error(f"Failed to send verification email: {e}")
# Still create user but inform them about email issue
returntemplates.TemplateResponse(
request=request,
name="dashboard/signup.html",
context={"request":request,"message":"Account created successfully! However, there was an issue sending the verification email. Please contact an administrator."}
context={"request":request,"message":"Account created successfully! However, there was an issue sending the verification email. Please contact an administrator.","config":config.aisbfifconfigandconfig.aisbfelse{}}
