- Added 'x-ai/grok-4' alias to xai/grok-4 model configuration
- Added OpenRouter x-ai model pricing support in constants generation
- Resolves LiteLLM 'LLM Provider NOT provided' errors in billing system
- Ensures proper token cost calculation for all Grok model variations
https://morphllm.com/api-keys
when setting up, user should be able to choose to go to morphllm to get a key; or provide open router apikey (if not already in the previous step)
this is the correct endpoint : """Python
Copy
Ask AI
from openai import OpenAI
client = OpenAI(
api_key="your-morph-api-key",
base_url="https://api.morphllm.com/v1"
)"""
- Replace simple marker check with precise character-by-character comparison
- Skip newlines during marker matching from end to start
- Add echo detection to prevent false positives when command just started
- Optimize English comments for better code readability
- Introduced a new function to determine if phone verification is mandatory based on an environment variable.
- Updated the logic in the authentication assurance level check to reflect the new phone verification requirement for new users.
- Enhanced logging to provide clearer insights into phone verification status during authentication checks.
This update improves the flexibility of phone verification requirements based on deployment configurations.
- Updated phone verification API to support SMS-based 2FA, allowing users to enroll and verify their phone numbers.
- Introduced new components for background AAL checking and status display, improving user experience during authentication.
- Removed the deprecated PhoneVerificationGuard component and integrated its functionality into the new AALChecker and BackgroundAALChecker components.
- Updated React Query hooks for managing phone verification and AAL states, ensuring efficient data handling and cache management.
- Enhanced frontend layout to accommodate new verification flows and improve overall responsiveness.
This update strengthens account security by enforcing phone verification for new users and streamlining the MFA process.
- Added phone verification endpoints for TOTP-based multi-factor authentication in the backend.
- Created frontend components for phone input and OTP verification.
- Integrated phone verification guard to ensure users complete verification before accessing the app.
- Updated API routes and React Query hooks for managing phone verification status and actions.
This feature enhances account security by requiring users to verify their phone numbers.