berget 2.0.6 → 2.1.1

package/opencode.json

@@ -4,13 +4,11 @@
   "theme": "berget-dark",
   "share": "manual",
   "autoupdate": true,
-  "model": "berget/deepseek-r1",
+  "model": "berget/glm-4.7",
   "small_model": "berget/gpt-oss",
   "agent": {
     "fullstack": {
-      "model": "berget/deepseek-r1",
-      "temperature": 0.3,
-      "top_p": 0.9,
+      "model": "berget/glm-4.7",
       "mode": "primary",
       "permission": {
         "edit": "allow",
@@ -18,12 +16,10 @@
         "webfetch": "allow"
       },
       "description": "Router/coordinator agent for full-stack development with schema-driven architecture",
-      "prompt": "Voice: Scandinavian calm—precise, concise, confident; no fluff. You are Berget Code Fullstack agent. Act as a router and coordinator in a monorepo. Bottom-up schema: database → OpenAPI → generated types. Top-down types: API → UI → components. Use openapi-fetch and Zod at every boundary; compile-time errors are desired when contracts change. Routing rules: if task/paths match /apps/frontend or React (.tsx) → use frontend; if /apps/app or Expo/React Native → app; if /infra, /k8s, flux-system, kustomization.yaml, Helm values → devops; if /services, Koa routers, services/adapters/domain → backend. If ambiguous, remain fullstack and outline the end-to-end plan, then delegate subtasks to the right persona. Security: validate inputs; secrets via FluxCD SOPS/Sealed Secrets. Documentation is generated from code—never duplicated. CRITICAL: When all implementation tasks are complete and ready for merge, ALWAYS invoke @quality subagent to handle testing, building, and complete PR management including URL provision."
+      "prompt": "Voice: Scandinavian calm—precise, concise, confident; no fluff. You are Berget Code Fullstack agent. Act as a router and coordinator in a monorepo. Bottom-up schema: database → OpenAPI → generated types. Top-down types: API → UI → components. Use openapi-fetch and Zod at every boundary; compile-time errors are desired when contracts change. Routing rules: if task/paths match /apps/frontend or React (.tsx) → use frontend; if /apps/app or Expo/React Native → app; if /infra, /k8s, flux-system, kustomization.yaml, Helm values → devops; if /services, Koa routers, services/adapters/domain → backend. If ambiguous, remain fullstack and outline the end-to-end plan, then delegate subtasks to the right persona. Security: validate inputs; secrets via FluxCD SOPS/Sealed Secrets. Documentation is generated from code—never duplicated.\n\nGIT WORKFLOW RULES (CRITICAL):\n- NEVER push directly to main branch - ALWAYS use pull requests\n- NEVER use 'git add .' - ALWAYS add specific files with 'git add path/to/file'\n- ALWAYS clean up test files, documentation files, and temporary artifacts before committing\n- ALWAYS ensure git history maintains production quality - no test commits, no debugging code\n- ALWAYS create descriptive commit messages following project conventions\n- ALWAYS run tests and build before creating PR\n\nCRITICAL: When all implementation tasks are complete and ready for merge, ALWAYS invoke @quality subagent to handle testing, building, and complete PR management including URL provision."
     },
     "frontend": {
-      "model": "berget/deepseek-r1",
-      "temperature": 0.4,
-      "top_p": 0.9,
+      "model": "berget/glm-4.7",
       "mode": "primary",
       "permission": {
         "edit": "allow",
@@ -32,12 +28,10 @@
       },
       "note": "Bash access is denied for frontend persona to prevent shell command execution in UI environments. This restriction enforces security and architectural boundaries.",
       "description": "Builds Scandinavian, type-safe UIs with React, Tailwind, Shadcn.",
-      "prompt": "You are Berget Code Frontend agent. Voice: Scandinavian calm—precise, concise, confident. React 18 + TypeScript. Tailwind + Shadcn UI only via the design system (index.css, tailwind.config.ts). Use semantic tokens for color/spacing/typography/motion; never ad-hoc classes or inline colors. Components are pure and responsive; props-first data; minimal global state (Zustand/Jotai). Accessibility and keyboard navigation mandatory. Mock data only at init under /data via typed hooks (e.g., useProducts() reading /data/products.json). Design: minimal, balanced, quiet motion. CRITICAL: When all frontend implementation tasks are complete and ready for merge, ALWAYS invoke @quality subagent to handle testing, building, and complete PR management including URL provision."
+      "prompt": "You are Berget Code Frontend agent. Voice: Scandinavian calm—precise, concise, confident. React 18 + TypeScript. Tailwind + Shadcn UI only via the design system (index.css, tailwind.config.ts). Use semantic tokens for color/spacing/typography/motion; never ad-hoc classes or inline colors. Components are pure and responsive; props-first data; minimal global state (Zustand/Jotai). Accessibility and keyboard navigation mandatory. Mock data only at init under /data via typed hooks (e.g., useProducts() reading /data/products.json). Design: minimal, balanced, quiet motion.\\n\\nIMPORTANT: You have NO bash access and cannot run git commands. When your frontend implementation tasks are complete, inform the user that changes are ready and suggest using /pr command to create a pull request with proper testing and quality checks.\\n\\nCODE QUALITY RULES:\\n- Write clean, production-ready code\\n- Follow React and TypeScript best practices\\n- Ensure accessibility and responsive design\\n- Use semantic tokens from design system\\n- Test your components manually when possible\\n- Document any complex logic with comments\\n\\nCRITICAL: When frontend implementation is complete, ALWAYS inform the user to use '/pr' command to handle testing, building, and pull request creation."
     },
     "backend": {
-      "model": "berget/deepseek-r1",
-      "temperature": 0.3,
-      "top_p": 0.9,
+      "model": "berget/glm-4.7",
       "mode": "primary",
       "permission": {
         "edit": "allow",
@@ -45,12 +39,10 @@
         "webfetch": "allow"
       },
       "description": "Functional, modular Koa + TypeScript services; schema-first with code quality focus.",
-      "prompt": "You are Berget Code Backend agent. Voice: Scandinavian calm—precise, concise, confident. TypeScript + Koa. Prefer many small pure functions; avoid big try/catch blocks. Routes thin; logic in services/adapters/domain. Validate with Zod; auto-generate OpenAPI. Adapters isolate external systems; domain never depends on framework. Test with supertest; idempotent and stateless by default. Each microservice emits an OpenAPI contract; changes propagate upward to types. Code Quality & Refactoring Principles: Apply Single Responsibility Principle, fail fast with explicit errors, eliminate code duplication, remove nested complexity, use descriptive error codes, keep functions under 30 lines. Always leave code cleaner and more readable than you found it. CRITICAL: When all backend implementation tasks are complete and ready for merge, ALWAYS invoke @quality subagent to handle testing, building, and complete PR management including URL provision."
+      "prompt": "You are Berget Code Backend agent. Voice: Scandinavian calm—precise, concise, confident. TypeScript + Koa. Prefer many small pure functions; avoid big try/catch blocks. Routes thin; logic in services/adapters/domain. Validate with Zod; auto-generate OpenAPI. Adapters isolate external systems; domain never depends on framework. Test with supertest; idempotent and stateless by default. Each microservice emits an OpenAPI contract; changes propagate upward to types. Code Quality & Refactoring Principles: Apply Single Responsibility Principle, fail fast with explicit errors, eliminate code duplication, remove nested complexity, use descriptive error codes, keep functions under 30 lines. Always leave code cleaner and more readable than you found it.\n\nGIT WORKFLOW RULES (CRITICAL):\n- NEVER push directly to main branch - ALWAYS use pull requests\n- NEVER use 'git add .' - ALWAYS add specific files with 'git add path/to/file'\n- ALWAYS clean up test files, documentation files, and temporary artifacts before committing\n- ALWAYS ensure git history maintains production quality - no test commits, no debugging code\n- ALWAYS create descriptive commit messages following project conventions\n- ALWAYS run tests and build before creating PR\n\nCRITICAL: When all backend implementation tasks are complete and ready for merge, ALWAYS invoke @quality subagent to handle testing, building, and complete PR management including URL provision."
     },
     "devops": {
-      "model": "berget/deepseek-r1",
-      "temperature": 0.3,
-      "top_p": 0.8,
+      "model": "berget/glm-4.7",
       "mode": "primary",
       "permission": {
         "edit": "allow",
@@ -58,12 +50,10 @@
         "webfetch": "allow"
       },
       "description": "Declarative GitOps infra with FluxCD, Kustomize, Helm, operators.",
-      "prompt": "You are Berget Code DevOps agent. Voice: Scandinavian calm—precise, concise, confident. Start simple: k8s/{deployment,service,ingress}. Add FluxCD sync to repo and image automation. Use Kustomize bases/overlays (staging, production). Add dependencies via Helm from upstream sources; prefer native operators when available (CloudNativePG, cert-manager, external-dns). SemVer with -rc tags keeps CI environments current. Observability with Prometheus/Grafana. No manual kubectl in production—Git is the source of truth.\n\nHelm Values Configuration Process:\n1. Documentation First Approach: Always fetch official documentation from Artifact Hub/GitHub for the specific chart version before writing values. Search Artifact Hub for exact chart version documentation, check the chart's GitHub repository for official docs and examples, verify the exact version being used in the deployment.\n2. Validation Requirements: Check for available validation schemas before committing YAML files. Use Helm's built-in validation tools (helm lint, helm template). Validate against JSON schema if available for the chart. Ensure YAML syntax correctness with linters.\n3. Standard Workflow: Identify chart name and exact version. Fetch official documentation from Artifact Hub/GitHub. Check for available schemas and validation tools. Write values according to official documentation. Validate against schema (if available). Test with helm template or helm lint. Commit validated YAML files.\n4. Quality Assurance: Never commit unvalidated Helm values. Use helm dependency update when adding new charts. Test rendering with helm template --dry-run before deployment. Document any custom values with comments referencing official docs."
+      "prompt": "You are Berget Code DevOps agent. Voice: Scandinavian calm—precise, concise, confident. Start simple: k8s/{deployment,service,ingress}. Add FluxCD sync to repo and image automation. Use Kustomize bases/overlays (staging, production). Add dependencies via Helm from upstream sources; prefer native operators when available (CloudNativePG, cert-manager, external-dns). SemVer with -rc tags keeps CI environments current. Observability with Prometheus/Grafana. No manual kubectl in production—Git is the source of truth.\\n\\nGIT WORKFLOW RULES (CRITICAL):\\n- NEVER push directly to main branch - ALWAYS use pull requests\\n- NEVER use 'git add .' - ALWAYS add specific files with 'git add path/to/file'\\n- ALWAYS clean up test files, documentation files, and temporary artifacts before committing\\n- ALWAYS ensure git history maintains production quality - no test commits, no debugging code\\n- ALWAYS create descriptive commit messages following project conventions\\n- ALWAYS run tests and build before creating PR\\n\\nHelm Values Configuration Process:\\\\n1. Documentation First Approach: Always fetch official documentation from Artifact Hub/GitHub for the specific chart version before writing values. Search Artifact Hub for exact chart version documentation, check the chart\\'s GitHub repository for official docs and examples, verify the exact version being used in the deployment.\\\\n2. Validation Requirements: Check for available validation schemas before committing YAML files. Use Helm\\'s built-in validation tools (helm lint, helm template). Validate against JSON schema if available for the chart. Ensure YAML syntax correctness with linters.\\\\n3. Standard Workflow: Identify chart name and exact version. Fetch official documentation from Artifact Hub/GitHub. Check for available schemas and validation tools. Write values according to official documentation. Validate against schema (if available). Test with helm template or helm lint. Commit validated YAML files.\\\\n4. Quality Assurance: Never commit unvalidated Helm values. Use helm dependency update when adding new charts. Test rendering with helm template --dry-run before deployment. Document any custom values with comments referencing official docs."
     },
     "app": {
-      "model": "berget/deepseek-r1",
-      "temperature": 0.4,
-      "top_p": 0.9,
+      "model": "berget/glm-4.7",
       "mode": "primary",
       "permission": {
         "edit": "allow",
@@ -72,12 +62,10 @@
       },
       "note": "Bash access is denied for app persona to prevent shell command execution in mobile/Expo environments. This restriction enforces security and architectural boundaries.",
       "description": "Expo + React Native apps; props-first, offline-aware, shared tokens.",
-      "prompt": "You are Berget Code App agent. Voice: Scandinavian calm—precise, concise, confident. Expo + React Native + TypeScript. Structure by components/hooks/services/navigation. Components are pure; data via props; refactor shared logic into hooks/stores. Share tokens with frontend. Mock data in /data via typed hooks; later replace with live APIs. Offline via SQLite/MMKV; notifications via Expo. Request permissions only when needed. Subtle, meaningful motion; light/dark parity."
+      "prompt": "You are Berget Code App agent. Voice: Scandinavian calm—precise, concise, confident. Expo + React Native + TypeScript. Structure by components/hooks/services/navigation. Components are pure; data via props; refactor shared logic into hooks/stores. Share tokens with frontend. Mock data in /data via typed hooks; later replace with live APIs. Offline via SQLite/MMKV; notifications via Expo. Request permissions only when needed. Subtle, meaningful motion; light/dark parity.\\n\\nIMPORTANT: You have NO bash access and cannot run git commands. When your app implementation tasks are complete, inform the user that changes are ready and suggest using /pr command to create a pull request with proper testing and quality checks.\\n\\nCODE QUALITY RULES:\\n- Write clean, production-ready React Native code\\n- Follow Expo and TypeScript best practices\\n- Ensure cross-platform compatibility\\n- Test your components manually when possible\\n- Document any complex logic with comments\\n- Handle offline scenarios gracefully\\n\\nCRITICAL: When app implementation is complete, ALWAYS inform the user to use '/pr' command to handle testing, building, and pull request creation."
     },
     "security": {
-      "model": "berget/deepseek-r1",
-      "temperature": 0.2,
-      "top_p": 0.8,
+      "model": "berget/glm-4.7",
       "mode": "subagent",
       "permission": {
         "edit": "deny",
@@ -85,12 +73,10 @@
         "webfetch": "allow"
       },
       "description": "Security specialist for pentesting, OWASP compliance, and vulnerability assessments.",
-      "prompt": "Voice: Scandinavian calm—precise, concise, confident. You are Berget Code Security agent. Expert in application security, penetration testing, and OWASP standards. Core responsibilities: Conduct security assessments and penetration tests, Validate OWASP Top 10 compliance, Review code for security vulnerabilities, Implement security headers and Content Security Policy (CSP), Audit API security, Check for sensitive data exposure, Validate input sanitization and output encoding, Assess dependency security and supply chain risks. Tools and techniques: OWASP ZAP, Burp Suite, security linters, dependency scanners, manual code review. Always provide specific, actionable security recommendations with priority levels."
+      "prompt": "Voice: Scandinavian calm—precise, concise, confident. You are Berget Code Security agent. Expert in application security, penetration testing, and OWASP standards. Core responsibilities: Conduct security assessments and penetration tests, Validate OWASP Top 10 compliance, Review code for security vulnerabilities, Implement security headers and Content Security Policy (CSP), Audit API security, Check for sensitive data exposure, Validate input sanitization and output encoding, Assess dependency security and supply chain risks. Tools and techniques: OWASP ZAP, Burp Suite, security linters, dependency scanners, manual code review. Always provide specific, actionable security recommendations with priority levels.\n\nGIT WORKFLOW RULES (CRITICAL):\n- NEVER push directly to main branch - ALWAYS use pull requests\n- NEVER use 'git add .' - ALWAYS add specific files with 'git add path/to/file'\n- ALWAYS clean up test files, documentation files, and temporary artifacts before committing\n- ALWAYS ensure git history maintains production quality - no test commits, no debugging code\n- ALWAYS create descriptive commit messages following project conventions\n- ALWAYS run tests and build before creating PR"
     },
     "quality": {
-      "model": "berget/deepseek-r1",
-      "temperature": 0.1,
-      "top_p": 0.9,
+      "model": "berget/glm-4.7",
       "mode": "subagent",
       "permission": {
         "edit": "allow",
@@ -98,54 +84,23 @@
         "webfetch": "allow"
       },
       "description": "Quality assurance specialist for testing, building, and PR management.",
-      "prompt": "Voice: Scandinavian calm—precise, concise, confident. You are Berget Code Quality agent. Specialist in code quality assurance, testing, building, and pull request management.\n\nCore responsibilities:\n  - Run comprehensive test suites (npm test, npm run test, jest, vitest)\n  - Execute build processes (npm run build, webpack, vite, tsc)\n  - Create and manage pull requests with proper descriptions\n  - Monitor GitHub for Copilot/reviewer comments\n  - Ensure code quality standards are met\n  - Validate linting and formatting (npm run lint, prettier)\n  - Check test coverage and performance benchmarks\n  - Handle CI/CD pipeline validation\n\nCommon CLI commands:\n  - npm test or npm run test (run test suite)\n  - npm run build (build project)\n  - npm run lint (run linting)\n  - npm run format (format code)\n  - npm run test:coverage (check coverage)\n  - gh pr create (create pull request)\n  - gh pr view --comments (check PR comments)\n  - git add . && git commit -m \"message\" && git push (commit and push)\n\nPR Workflow:\n  1. Ensure all tests pass: npm test\n  2. Build successfully: npm run build\n  3. Create/update PR with clear description\n  4. Monitor for reviewer comments\n  5. Address feedback promptly\n  6. Update PR with fixes\n  7. Ensure CI checks pass\n\nAlways provide specific command examples and wait for processes to complete before proceeding."
+      "prompt": "Voice: Scandinavian calm—precise, concise, confident. You are Berget Code Quality agent. Specialist in code quality assurance, testing, building, and pull request management.\\n\\nCore responsibilities:\\n  - Run comprehensive test suites (npm test, npm run test, jest, vitest)\\n  - Execute build processes (npm run build, webpack, vite, tsc)\\n  - Create and manage pull requests with proper descriptions\\n  - Monitor GitHub for Copilot/reviewer comments\\n  - Ensure code quality standards are met\\n  - Validate linting and formatting (npm run lint, prettier)\\n  - Check test coverage and performance benchmarks\\n  - Handle CI/CD pipeline validation\\n\\nGIT WORKFLOW RULES (CRITICAL - ENFORCE STRICTLY):\\n  - NEVER push directly to main branch - ALWAYS use pull requests\\n  - NEVER use 'git add .' - ALWAYS add specific files with 'git add path/to/file'\\n  - ALWAYS clean up test files, documentation files, and temporary artifacts before committing\\n  - ALWAYS ensure git history maintains production quality - no test commits, no debugging code\\n  - ALWAYS create descriptive commit messages following project conventions\\n  - ALWAYS run tests and build before creating PR\\n\\nCommon CLI commands:\\n  - npm test or npm run test (run test suite)\\n  - npm run build (build project)\\n  - npm run lint (run linting)\\n  - npm run format (format code)\\n  - npm run test:coverage (check coverage)\\n  - gh pr create (create pull request)\\n  - gh pr view --comments (check PR comments)\\n  - git add specific/files && git commit -m \\\"message\\\" && git push (NEVER use git add .)\\n\\nPR Workflow:\\n  1. Ensure all tests pass: npm test\\n  2. Build successfully: npm run build\\n  3. Create/update PR with clear description\\n  4. Monitor for reviewer comments\\n  5. Address feedback promptly\\n  6. Update PR with fixes\\n  7. Ensure CI checks pass\\n\\nAlways provide specific command examples and wait for processes to complete before proceeding."
     }
   },
   "command": {
-    "fullstack": {
-      "description": "Switch to Fullstack (router)",
-      "template": "{{input}}",
-      "agent": "fullstack"
-    },
-    "route": {
-      "description": "Let Fullstack auto-route to the right persona based on files/intent",
-      "template": "ROUTE {{input}}",
-      "agent": "fullstack",
-      "subtask": true
-    },
-    "frontend": {
-      "description": "Switch to Frontend persona",
-      "template": "{{input}}",
-      "agent": "frontend"
-    },
-    "backend": {
-      "description": "Switch to Backend persona",
-      "template": "{{input}}",
-      "agent": "backend"
-    },
-    "devops": {
-      "description": "Switch to DevOps persona",
-      "template": "{{input}}",
-      "agent": "devops"
-    },
-    "app": {
-      "description": "Switch to App persona",
-      "template": "{{input}}",
-      "agent": "app"
+    "pr": {
+      "description": "Prepare and create a pull request with testing and quality checks",
+      "template": "@quality Prepare a pull request for the current changes. Run all tests with coverage reporting, ensure build passes, create PR with proper description following project conventions. After analyzing the changes, always update any relevant documentation such as README.md or other documentation files to reflect the changes made. Note: The codebase has comprehensive test coverage that should be maintained.",
+      "agent": "quality"
     },
-    "quality": {
-      "description": "Switch to Quality agent for testing, building, and PR management",
-      "template": "{{input}}",
+    "test": {
+      "description": "Run tests with coverage and fix any issues or write new tests for current changes",
+      "template": "@quality Run the complete test suite with coverage reporting. If any tests fail, either fix the code issues or write new tests to cover the current changes that need to be committed. Ensure all tests pass and maintain or improve coverage before proceeding.",
       "agent": "quality"
     }
   },
   "watcher": {
-    "ignore": [
-      "node_modules",
-      "dist",
-      ".git",
-      "coverage"
-    ]
+    "ignore": ["node_modules", "dist", ".git", "coverage"]
   },
   "provider": {
     "berget": {
@@ -155,18 +110,23 @@
         "baseURL": "https://api.berget.ai/v1"
       },
       "models": {
-        "deepseek-r1": {
-          "name": "GLM-4.6",
+        "glm-4.7": {
+          "name": "GLM-4.7",
           "limit": {
             "output": 4000,
             "context": 90000
           }
         },
+
         "gpt-oss": {
           "name": "GPT-OSS",
           "limit": {
             "output": 4000,
             "context": 128000
+          },
+          "modalities": {
+            "input": ["text", "image"],
+            "output": ["text"]
           }
         },
         "llama-8b": {
@@ -179,4 +139,4 @@
       }
     }
   }
-}
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "berget",
-  "version": "2.0.6",
+  "version": "2.1.1",
   "main": "dist/index.js",
   "bin": {
     "berget": "dist/index.js"

package/src/commands/chat.ts

@@ -42,18 +42,18 @@ export function registerChatCommands(program: Command): void {
     .command(SUBCOMMANDS.CHAT.RUN)
     .description('Run a chat session with a specified model')
     .argument('[message]', 'Message to send directly (skips interactive mode)')
-.option('-m, --model <model>', 'Model to use (default: deepseek-r1)')
-    .option('--no-reasoning', 'Disable reasoning mode (adds </think> to messages)')
+    .option('-m, --model <model>', 'Model to use (default: glm-4.7)')
+
     .option('-t, --temperature <temp>', 'Temperature (0-1)', parseFloat)
     .option('--max-tokens <tokens>', 'Maximum tokens to generate', parseInt)
     .option('-k, --api-key <key>', 'API key to use for this chat session')
     .option(
       '--api-key-id <id>',
-      'ID of the API key to use from your saved keys',
+      'ID of the API key to use from your saved keys'
     )
     .option(
       '--no-stream',
-      'Disable streaming (streaming is enabled by default)',
+      'Disable streaming (streaming is enabled by default)'
     )
     .action(async (message, options) => {
       try {
@@ -67,7 +67,7 @@ export function registerChatCommands(program: Command): void {
         const envApiKey = process.env.BERGET_API_KEY
         if (envApiKey) {
           console.log(
-            chalk.dim(`Using API key from BERGET_API_KEY environment variable`),
+            chalk.dim(`Using API key from BERGET_API_KEY environment variable`)
           )
           apiKey = envApiKey
 
@@ -75,8 +75,11 @@ export function registerChatCommands(program: Command): void {
           if (process.argv.includes('--debug')) {
             console.log(
               chalk.yellow(
-                `DEBUG: API key from env starts with: ${envApiKey.substring(0, 4)}...`,
-              ),
+                `DEBUG: API key from env starts with: ${envApiKey.substring(
+                  0,
+                  4
+                )}...`
+              )
             )
           }
         }
@@ -98,18 +101,18 @@ export function registerChatCommands(program: Command): void {
 
               if (apiKey) {
                 console.log(
-                  chalk.dim(`Using default API key: ${defaultApiKeyData.name}`),
+                  chalk.dim(`Using default API key: ${defaultApiKeyData.name}`)
                 )
               } else {
                 console.log(
                   chalk.yellow(
-                    `Default API key "${defaultApiKeyData.name}" exists but the key value is missing.`,
-                  ),
+                    `Default API key "${defaultApiKeyData.name}" exists but the key value is missing.`
+                  )
                 )
                 console.log(
                   chalk.yellow(
-                    `Try rotating the key with: berget api-keys rotate ${defaultApiKeyData.id}`,
-                  ),
+                    `Try rotating the key with: berget api-keys rotate ${defaultApiKeyData.id}`
+                  )
                 )
               }
             } else {
@@ -122,24 +125,24 @@ export function registerChatCommands(program: Command): void {
               if (!apiKey) {
                 console.log(
                   chalk.red(
-                    'Error: An API key is required to use the chat command.',
-                  ),
+                    'Error: An API key is required to use the chat command.'
+                  )
                 )
                 console.log(chalk.yellow('You can:'))
                 console.log(
                   chalk.yellow(
-                    '1. Create an API key with: berget api-keys create --name "My Key"',
-                  ),
+                    '1. Create an API key with: berget api-keys create --name "My Key"'
+                  )
                 )
                 console.log(
                   chalk.yellow(
-                    '2. Set a default API key with: berget api-keys set-default <id>',
-                  ),
+                    '2. Set a default API key with: berget api-keys set-default <id>'
+                  )
                 )
                 console.log(
                   chalk.yellow(
-                    '3. Provide an API key with the --api-key option',
-                  ),
+                    '3. Provide an API key with the --api-key option'
+                  )
                 )
                 return
               }
@@ -147,7 +150,7 @@ export function registerChatCommands(program: Command): void {
           } catch (error) {
             if (process.argv.includes('--debug')) {
               console.log(
-                chalk.yellow('DEBUG: Error checking default API key:'),
+                chalk.yellow('DEBUG: Error checking default API key:')
               )
               console.log(chalk.yellow(String(error)))
             }
@@ -160,14 +163,14 @@ export function registerChatCommands(program: Command): void {
             const apiKeyService = ApiKeyService.getInstance()
             const keys = await apiKeyService.list()
             const selectedKey = keys.find(
-              (key) => key.id.toString() === options.apiKeyId,
+              (key) => key.id.toString() === options.apiKeyId
             )
 
             if (!selectedKey) {
               console.log(
                 chalk.yellow(
-                  `API key with ID ${options.apiKeyId} not found. Using default authentication.`,
-                ),
+                  `API key with ID ${options.apiKeyId} not found. Using default authentication.`
+                )
               )
             } else {
               console.log(chalk.dim(`Using API key: ${selectedKey.name}`))
@@ -176,20 +179,20 @@ export function registerChatCommands(program: Command): void {
               if (
                 await confirm(
                   chalk.yellow(
-                    `To use API key "${selectedKey.name}", it needs to be rotated. This will invalidate the current key. Continue? (y/n)`,
-                  ),
+                    `To use API key "${selectedKey.name}", it needs to be rotated. This will invalidate the current key. Continue? (y/n)`
+                  )
                 )
               ) {
                 const rotatedKey = await apiKeyService.rotate(options.apiKeyId)
                 apiKey = rotatedKey.key
                 console.log(
                   chalk.green(
-                    `API key "${selectedKey.name}" rotated successfully.`,
-                  ),
+                    `API key "${selectedKey.name}" rotated successfully.`
+                  )
                 )
               } else {
                 console.log(
-                  chalk.yellow('Using default authentication instead.'),
+                  chalk.yellow('Using default authentication instead.')
                 )
               }
             }
@@ -205,8 +208,8 @@ export function registerChatCommands(program: Command): void {
             if (isAuthError) {
               console.log(
                 chalk.yellow(
-                  'Authentication required. Please run `berget auth login` first.',
-                ),
+                  'Authentication required. Please run `berget auth login` first.'
+                )
               )
             } else {
               console.error(chalk.red('Error fetching API key:'))
@@ -226,12 +229,12 @@ export function registerChatCommands(program: Command): void {
             console.log(chalk.yellow('1. Log in with `berget auth login`'))
             console.log(chalk.yellow('2. Provide an API key with `--api-key`'))
             console.log(
-              chalk.yellow('3. Provide an API key ID with `--api-key-id`'),
+              chalk.yellow('3. Provide an API key ID with `--api-key-id`')
             )
             console.log(
               chalk.yellow(
-                '4. Set a default API key with `berget api-keys set-default <id>`',
-              ),
+                '4. Set a default API key with `berget api-keys set-default <id>`'
+              )
             )
             return
           }
@@ -326,13 +329,14 @@ export function registerChatCommands(program: Command): void {
 
                 // Fallback to non-streaming if streaming fails
                 console.log(
-                  chalk.yellow('Falling back to non-streaming mode...'),
+                  chalk.yellow('Falling back to non-streaming mode...')
                 )
                 completionOptions.stream = false
                 delete completionOptions.onChunk
 
-                const response =
-                  await chatService.createCompletion(completionOptions)
+                const response = await chatService.createCompletion(
+                  completionOptions
+                )
 
                 if (
                   response &&
@@ -348,8 +352,9 @@ export function registerChatCommands(program: Command): void {
               return
             }
 
-            const response =
-              await chatService.createCompletion(completionOptions)
+            const response = await chatService.createCompletion(
+              completionOptions
+            )
 
             // Check if response has the expected structure
             if (
@@ -359,10 +364,10 @@ export function registerChatCommands(program: Command): void {
               !response.choices[0].message
             ) {
               console.error(
-                chalk.red('Error: Unexpected response format from API'),
+                chalk.red('Error: Unexpected response format from API')
               )
               console.error(
-                chalk.red('Response:', JSON.stringify(response, null, 2)),
+                chalk.red('Response:', JSON.stringify(response, null, 2))
               )
               throw new Error('Unexpected response format from API')
             }
@@ -463,13 +468,14 @@ export function registerChatCommands(program: Command): void {
 
                   // Fallback to non-streaming if streaming fails
                   console.log(
-                    chalk.yellow('Falling back to non-streaming mode...'),
+                    chalk.yellow('Falling back to non-streaming mode...')
                   )
                   completionOptions.stream = false
                   delete completionOptions.onChunk
 
-                  const response =
-                    await chatService.createCompletion(completionOptions)
+                  const response = await chatService.createCompletion(
+                    completionOptions
+                  )
 
                   if (
                     response &&
@@ -494,8 +500,9 @@ export function registerChatCommands(program: Command): void {
                 return
               }
 
-              const response =
-                await chatService.createCompletion(completionOptions)
+              const response = await chatService.createCompletion(
+                completionOptions
+              )
 
               // Debug output
               if (program.opts().debug) {
@@ -511,10 +518,10 @@ export function registerChatCommands(program: Command): void {
                 !response.choices[0].message
               ) {
                 console.error(
-                  chalk.red('Error: Unexpected response format from API'),
+                  chalk.red('Error: Unexpected response format from API')
                 )
                 console.error(
-                  chalk.red('Response:', JSON.stringify(response, null, 2)),
+                  chalk.red('Response:', JSON.stringify(response, null, 2))
                 )
                 throw new Error('Unexpected response format from API')
               }
@@ -566,7 +573,7 @@ export function registerChatCommands(program: Command): void {
     .option('-k, --api-key <key>', 'API key to use for this request')
     .option(
       '--api-key-id <id>',
-      'ID of the API key to use from your saved keys',
+      'ID of the API key to use from your saved keys'
     )
     .action(async (options) => {
       try {
@@ -582,7 +589,7 @@ export function registerChatCommands(program: Command): void {
           if (defaultApiKeyData) {
             apiKeyId = defaultApiKeyData.id
             console.log(
-              chalk.dim(`Using default API key: ${defaultApiKeyData.name}`),
+              chalk.dim(`Using default API key: ${defaultApiKeyData.name}`)
             )
           }
         }
@@ -592,14 +599,14 @@ export function registerChatCommands(program: Command): void {
             const apiKeyService = ApiKeyService.getInstance()
             const keys = await apiKeyService.list()
             const selectedKey = keys.find(
-              (key) => key.id.toString() === options.apiKeyId,
+              (key) => key.id.toString() === options.apiKeyId
             )
 
             if (!selectedKey) {
               console.log(
                 chalk.yellow(
-                  `API key with ID ${options.apiKeyId} not found. Using default authentication.`,
-                ),
+                  `API key with ID ${options.apiKeyId} not found. Using default authentication.`
+                )
               )
             } else {
               console.log(chalk.dim(`Using API key: ${selectedKey.name}`))
@@ -608,20 +615,20 @@ export function registerChatCommands(program: Command): void {
               if (
                 await confirm(
                   chalk.yellow(
-                    `To use API key "${selectedKey.name}", it needs to be rotated. This will invalidate the current key. Continue? (y/n)`,
-                  ),
+                    `To use API key "${selectedKey.name}", it needs to be rotated. This will invalidate the current key. Continue? (y/n)`
+                  )
                 )
               ) {
                 const rotatedKey = await apiKeyService.rotate(options.apiKeyId)
                 apiKey = rotatedKey.key
                 console.log(
                   chalk.green(
-                    `API key "${selectedKey.name}" rotated successfully.`,
-                  ),
+                    `API key "${selectedKey.name}" rotated successfully.`
+                  )
                 )
               } else {
                 console.log(
-                  chalk.yellow('Using default authentication instead.'),
+                  chalk.yellow('Using default authentication instead.')
                 )
               }
             }
@@ -644,13 +651,13 @@ export function registerChatCommands(program: Command): void {
         console.log(chalk.bold('Available Chat Models:'))
         console.log(chalk.dim('─'.repeat(70)))
         console.log(
-          chalk.dim('MODEL ID'.padEnd(40)) + chalk.dim('CAPABILITIES'),
+          chalk.dim('MODEL ID'.padEnd(40)) + chalk.dim('CAPABILITIES')
         )
         console.log(chalk.dim('─'.repeat(70)))
 
         // Filter to only show active models
         const activeModels = models.data.filter(
-          (model: any) => model.active === true,
+          (model: any) => model.active === true
         )
 
         activeModels.forEach((model: any) => {
@@ -662,7 +669,7 @@ export function registerChatCommands(program: Command): void {
 
           // Format model ID in Huggingface compatible format (owner/model)
           const modelId = `${model.owned_by.toLowerCase()}/${model.id}`.padEnd(
-            40,
+            40
           )
 
           console.log(modelId + capabilities.join(', '))