← Back to Kontasks
Multi-Model & Quick Turn Design
Initial design exploration for multi-model support, multiple sessions, and quick turns
Output
🎯 Foundational Capabilities Design
Three major features that will reshape the platform. Let's work through each systematically.
1️⃣ Multiple Sessions/Connections
Run multiple AI conversations simultaneously in the dashboard.
| Key Questions | • Tab-based UI vs split-pane? • Shared context between sessions? • Session limits (max concurrent)? • How do kontasks route to sessions? |
| Current State | Single konsole session per browser. Sessions identified by token. |
2️⃣ Multi-Model Support
Switch between AI providers per-turn or per-session.
| Providers | • Claude (current) - via Claude Code CLI • OpenAI/ChatGPT - direct API • Google Gemini - direct API • OpenWebUI - OpenAI-compatible API • "Nano Banana Pro" 🍌 - TBD |
| Architecture | • Provider abstraction layer? • Per-provider tool/capability matrix? • Credential storage (Config UI tie-in)? • Model picker UI (dropdown vs icons)? |
| Challenge | Claude Code has tools (Read, Edit, Bash). Other models = raw chat only unless we build tool layer. |
3️⃣ Quick Turn Mode
Fastest path to answer. No kontask wrapping, minimal overhead.
| Concept | • Bypass konsole entirely? • Direct API call to model • No tool access, no file ops • Response inline, not kontask |
| UX Ideas | • Keyboard shortcut (Cmd+Shift+Q)? • Different input box styling? • Prefix command ("?" or "/quick")? • Toggle button near send? |
| Trade-offs | No file access, no tool use, no kontask history. Pure Q&A. |
🔗 How These Connect
Multi-session + Multi-model = Different AI for different tasks simultaneously
Quick turn = Lightweight lane within multi-model (any model, no tools)
Config UI (existing backlog) = Where API keys are managed
Discussion Points
Before diving into implementation planning, let's clarify:
- For multi-model: Do non-Claude models need tool access, or is chat-only acceptable?
- For multi-session: Tabs vs split-pane? Mobile considerations?
- For quick turn: Should it share session context or be stateless?
- Priority order? Which to build first?
Quick Actions
Original Request
No layout configured
Details
Type
General
Status
Completed
Scope
vibetools
Tags
architecturemulti-modelplanning
Created
5 Jan 2026, 10:04 am
Updated
5 Jan 2026, 10:04 am
Timing
⏱️ 50.4s
1 tools
● TTFE 7%
● Thinking 92%
● Tools 1%
Created By
claude
Raw Data
{
"id": "30146d5a-6eec-4b94-8df1-a733d9198108",
"type": "general",
"status": "completed",
"title": "Multi-Model & Quick Turn Design",
"description": "Initial design exploration for multi-model support, multiple sessions, and quick turns",
"context": {
"output": "<div style=\"background:#1e1e1e;color:#e0e0e0;padding:20px;border-radius:8px;font-family:sans-serif;\"><h2 style=\"color:#fff;margin:0 0 16px 0;\">🎯 Foundational Capabilities Design</h2><p style=\"color:#9ca3af;margin:0 0 20px 0;\">Three major features that will reshape the platform. Let's work through each systematically.</p><div style=\"background:#2d2d2d;padding:16px;border-radius:6px;margin-bottom:16px;\"><h3 style=\"color:#e5c07b;margin:0 0 12px 0;\">1️⃣ Multiple Sessions/Connections</h3><p style=\"color:#9ca3af;margin:0 0 12px 0;\">Run multiple AI conversations simultaneously in the dashboard.</p><table style=\"width:100%;border-collapse:collapse;\"><tr style=\"border-bottom:1px solid #444;\"><td style=\"padding:8px;color:#98c379;width:120px;\">Key Questions</td><td style=\"padding:8px;color:#fff;\">• Tab-based UI vs split-pane?<br>• Shared context between sessions?<br>• Session limits (max concurrent)?<br>• How do kontasks route to sessions?</td></tr><tr><td style=\"padding:8px;color:#61afef;\">Current State</td><td style=\"padding:8px;color:#fff;\">Single konsole session per browser. Sessions identified by token.</td></tr></table></div><div style=\"background:#2d2d2d;padding:16px;border-radius:6px;margin-bottom:16px;\"><h3 style=\"color:#e5c07b;margin:0 0 12px 0;\">2️⃣ Multi-Model Support</h3><p style=\"color:#9ca3af;margin:0 0 12px 0;\">Switch between AI providers per-turn or per-session.</p><table style=\"width:100%;border-collapse:collapse;\"><tr style=\"border-bottom:1px solid #444;\"><td style=\"padding:8px;color:#98c379;width:120px;\">Providers</td><td style=\"padding:8px;color:#fff;\">• <strong>Claude</strong> (current) - via Claude Code CLI<br>• <strong>OpenAI/ChatGPT</strong> - direct API<br>• <strong>Google Gemini</strong> - direct API<br>• <strong>OpenWebUI</strong> - OpenAI-compatible API<br>• <strong>\"Nano Banana Pro\"</strong> 🍌 - TBD</td></tr><tr style=\"border-bottom:1px solid #444;\"><td style=\"padding:8px;color:#61afef;\">Architecture</td><td style=\"padding:8px;color:#fff;\">• Provider abstraction layer?<br>• Per-provider tool/capability matrix?<br>• Credential storage (Config UI tie-in)?<br>• Model picker UI (dropdown vs icons)?</td></tr><tr><td style=\"padding:8px;color:#c678dd;\">Challenge</td><td style=\"padding:8px;color:#fff;\">Claude Code has tools (Read, Edit, Bash). Other models = raw chat only unless we build tool layer.</td></tr></table></div><div style=\"background:#2d2d2d;padding:16px;border-radius:6px;margin-bottom:16px;\"><h3 style=\"color:#e5c07b;margin:0 0 12px 0;\">3️⃣ Quick Turn Mode</h3><p style=\"color:#9ca3af;margin:0 0 12px 0;\">Fastest path to answer. No kontask wrapping, minimal overhead.</p><table style=\"width:100%;border-collapse:collapse;\"><tr style=\"border-bottom:1px solid #444;\"><td style=\"padding:8px;color:#98c379;width:120px;\">Concept</td><td style=\"padding:8px;color:#fff;\">• Bypass konsole entirely?<br>• Direct API call to model<br>• No tool access, no file ops<br>• Response inline, not kontask</td></tr><tr style=\"border-bottom:1px solid #444;\"><td style=\"padding:8px;color:#61afef;\">UX Ideas</td><td style=\"padding:8px;color:#fff;\">• Keyboard shortcut (Cmd+Shift+Q)?<br>• Different input box styling?<br>• Prefix command (\"?\" or \"/quick\")?<br>• Toggle button near send?</td></tr><tr><td style=\"padding:8px;color:#c678dd;\">Trade-offs</td><td style=\"padding:8px;color:#fff;\">No file access, no tool use, no kontask history. Pure Q&A.</td></tr></table></div><div style=\"background:#1a3a2a;border:1px solid #22c55e;padding:16px;border-radius:6px;margin-bottom:16px;\"><h3 style=\"color:#22c55e;margin:0 0 12px 0;\">🔗 How These Connect</h3><p style=\"color:#9ca3af;margin:0;\"><strong>Multi-session</strong> + <strong>Multi-model</strong> = Different AI for different tasks simultaneously<br><strong>Quick turn</strong> = Lightweight lane within multi-model (any model, no tools)<br><strong>Config UI</strong> (existing backlog) = Where API keys are managed</p></div><div style=\"background:#2d2d2d;padding:12px;border-radius:6px;\"><h4 style=\"margin:0 0 8px 0;color:#fff;\">Discussion Points</h4><p style=\"color:#9ca3af;margin:0;\">Before diving into implementation planning, let's clarify:</p><ol style=\"color:#fff;margin:12px 0 0 0;padding-left:20px;line-height:1.8;\"><li>For <strong>multi-model</strong>: Do non-Claude models need tool access, or is chat-only acceptable?</li><li>For <strong>multi-session</strong>: Tabs vs split-pane? Mobile considerations?</li><li>For <strong>quick turn</strong>: Should it share session context or be stateless?</li><li>Priority order? Which to build first?</li></ol></div></div>",
"requestedAt": "2026-01-05T00:02:00.000Z",
"requestId": "ffa17200-8c46-4417-8723-51c40cf7b47e",
"choices": [
{
"label": "Clarify multi-model",
"value": "Let's focus on multi-model first - should non-Claude models have tool access or chat-only?",
"primary": true
},
{
"label": "Discuss sessions UI",
"value": "Let's discuss multi-session UI - tabs vs split-pane, mobile considerations"
},
{
"label": "Define quick turn",
"value": "Let's define quick turn mode in detail - UX, scope, stateless vs context-aware"
},
{
"label": "Set priorities",
"value": "Help me prioritize - which of these three should we build first and why?"
}
],
"turnTiming": {
"totalMs": 50390,
"ttfeMs": 3619,
"thinkingMs": 46414,
"toolExecutionMs": 356,
"toolCallCount": 1,
"thinkingPct": 92,
"toolsPct": 1,
"ttfePct": 7
}
},
"createdBy": "claude",
"createdAt": "2026-01-05T00:04:40.853Z",
"updatedAt": "2026-01-05T00:04:46.822Z",
"requestId": "ffa17200-8c46-4417-8723-51c40cf7b47e",
"scope": "vibetools",
"tags": [
"architecture",
"multi-model",
"planning"
],
"targetUser": "claude"
}