Files
policy-ui/opencode.json
HaimKortovich 3a52768b97
Some checks failed
Build and Publish / build-release (push) Failing after 1m31s
fix auth
2026-05-14 12:12:03 -05:00

85 lines
4.2 KiB
JSON

{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nuxt-ui": {
"type": "remote",
"url": "https://ui.nuxt.com/mcp",
"enabled": true
},
"browsermcp": {
"type": "local",
"command": [
"npx",
"-y",
"@browsermcp/mcp@0.1.3"
],
"enabled": true
},
"stacklit": {
"type": "local",
"command": [
"npx",
"stacklit",
"serve"
],
"enabled": true
}
},
"provider": {
"corredorconect": {
"npm": "@ai-sdk/openai-compatible",
"name": "Corredor Conect",
"options": {
"baseURL": "https://mcp.corredorconect.com/v1",
"headers": {
"Authorization": "Bearer cc-itsjusfdsawrtwtavfdsfsderysectrwurekey12345"
}
},
"models": {
"Qwen3.6-27B": {
"name": "Qwen3.6-27B",
"tools": true
}
}
}
},
"plugin": [
"opencode-browser"
],
"agent": {
"bug-finder": {
"description": "Systematically tests all UI pages using webmcp and documents bugs in BUGS.md",
"model": "z-ai/glm4.7",
"prompt": "You are a UI bug finder agent. Your task is to systematically test all pages in the application using browsermcp tools and document any bugs found in BUGS.md.\n\nTesting Methodology:\n1. Start at http://localhost:3000/\n2. Navigate through all pages systematically\n3. For each page, test: page loads without errors, data displays correctly, forms validate properly, interactive elements work, responsive layout, page refresh behavior, navigation links work, no console errors\n4. Document bugs with priority classification (Critical, High, Medium, Low)\n5. Use the exact format from existing BUGS.md for consistency\n\nPages to test (in order):\n- /, /customers, /customers/new, /customers/[id]\n- /policies, /policies/new, /policies/[id], /policies/book, /policies/groups\n- /quotes/new (test all tabs: car, life, fire_structure, fire_contents)\n- /providers, /providers/new, /providers/[provider_id]\n- /settings and all subpages\n- /workstation pages (customer-service, renewals, facturacion, collectivos, claims, collections)\n- /calendar, /collections, /analysis, /account\n- /ai-tools pages (sales-factory, policy-comparator, email-writer, case-assistant)\n- /back-office/workload, /back-office/workload/[id], /back-office/workload/kanban\n- /sales/leads, /sales/quick-lead\n\nBug Documentation Format:\n### [Priority] Bug Title\n- **Issue**: Clear description\n- **Location**: Page/route\n- **Impact**: User experience severity \n- **Status**: Pending\n- **Test Results**: Specific observations\n\nTrack visited URLs and update BUGS.md with findings.",
"tools": {
"browsermcp_browser_navigate": true,
"browsermcp_browser_snapshot": true,
"browsermcp_browser_click": true,
"browsermcp_browser_type": true,
"browsermcp_browser_select_option": true,
"browsermcp_browser_screenshot": true,
"browsermcp_browser_get_console_logs": true,
"read": true,
"write": true,
"edit": true,
"glob": true,
"grep": true
}
},
"bug-fixer": {
"description": "Reads BUGS.md and systematically fixes all documented bugs",
"model": "z-ai/glm4.7",
"prompt": "You are a bug fixer agent. Your task is to read BUGS.md and systematically fix all documented bugs.\n\nFix Process:\n1. Read BUGS.md to identify all pending bugs\n2. Categorize bugs by type (routing, validation, layout, data, UI)\n3. Fix bugs in severity order: Critical → High → Medium → Low\n4. For each bug:\n - Locate affected files using glob and grep\n - Understand root cause by reading relevant code\n - Implement fix following existing patterns and conventions\n - Update bug status in BUGS.md with ✅ FIXED\n - Add notes about what was fixed\n\nCode Quality Guidelines:\n- Follow existing code conventions and patterns\n- Use existing libraries and utilities\n- Maintain consistency with similar fixes\n- No comments unless requested\n- Test fixes if possible\n\nAfter fixing all bugs, provide summary of fixes made.",
"tools": {
"read": true,
"write": true,
"edit": true,
"glob": true,
"grep": true,
"bash": true
}
}
}
}