{ "canonical_name": "BloopAI/vibe-kanban", "compilation_id": "pack_24f63f95fc404d98b2d0aac765186ee3", "created_at": "2026-05-18T03:50:33.071971+00:00", "created_by": "project-pack-compiler", "feedback": { "carrier_selection_notes": [ "viable_asset_types=skill, recipe, host_instruction, eval, preflight", "recommended_asset_types=skill, recipe, host_instruction, eval, preflight" ], "evidence_delta": { "confirmed_claims": [ "identity_anchor_present", "capability_and_host_targets_present", "install_path_declared_or_better" ], "missing_required_fields": [], "must_verify_forwarded": [ "Run or inspect `npx vibe-kanban` in an isolated environment.", "Confirm the project exposes the claimed capability to at least one target host." ], "quickstart_execution_scope": "allowlisted_sandbox_smoke", "sandbox_command": "npx vibe-kanban", "sandbox_container_image": "node:22-slim", "sandbox_execution_backend": "docker", "sandbox_planner_decision": "deterministic_isolated_install", "sandbox_validation_id": "sbx_c0d7630df4264e98816d8d56019fbd34" }, "feedback_event_type": "project_pack_compilation_feedback", "learning_candidate_reasons": [], "template_gaps": [] }, "identity": { "canonical_id": "project_3ffa08e5da1fd1dc6348dc421a823725", "canonical_name": "BloopAI/vibe-kanban", "homepage_url": null, "license": "unknown", "repo_url": "https://github.com/BloopAI/vibe-kanban", "slug": "vibe-kanban", "source_packet_id": "phit_a62bf31afd2d4d5481df34e40418bc24", "source_validation_id": "dval_e55369cc1fa641a2b59247e944d86e7c" }, "merchandising": { "best_for": "需要软件开发与交付能力，并使用 claude的用户", "github_forks": 2721, "github_stars": 26187, "one_liner_en": "Get 10X more out of Claude Code, Codex or any coding agent", "one_liner_zh": "Get 10X more out of Claude Code, Codex or any coding agent", "primary_category": { "category_id": "software-development", "confidence": "high", "name_en": "Software Development", "name_zh": "软件开发与交付", "reason": "matched_keywords:code, coding, git" }, "target_user": "使用 claude, claude_code 等宿主 AI 的用户", "title_en": "vibe-kanban", "title_zh": "vibe-kanban 能力包", "visible_tags": [ { "label_en": "Browser Agents", "label_zh": "浏览器 Agent", "source": "repo_evidence_project_characteristics", "tag_id": "product_domain-browser-agents", "type": "product_domain" }, { "label_en": "Web Task Automation", "label_zh": "网页任务自动化", "source": "repo_evidence_project_characteristics", "tag_id": "user_job-web-task-automation", "type": "user_job" }, { "label_en": "Browser Automation", "label_zh": "浏览器自动化", "source": "repo_evidence_project_characteristics", "tag_id": "core_capability-browser-automation", "type": "core_capability" }, { "label_en": "Node-based Workflow", "label_zh": "节点式流程编排", "source": "repo_evidence_project_characteristics", "tag_id": "workflow_pattern-node-based-workflow", "type": "workflow_pattern" }, { "label_en": "Evaluation Suite", "label_zh": "评测体系", "source": "repo_evidence_project_characteristics", "tag_id": "selection_signal-evaluation-suite", "type": "selection_signal" } ] }, "packet_id": "phit_a62bf31afd2d4d5481df34e40418bc24", "page_model": { "artifacts": { "artifact_slug": "vibe-kanban", "files": [ "PROJECT_PACK.json", "QUICK_START.md", "PROMPT_PREVIEW.md", "HUMAN_MANUAL.md", "AI_CONTEXT_PACK.md", "BOUNDARY_RISK_CARD.md", "PITFALL_LOG.md", "REPO_INSPECTION.json", "REPO_INSPECTION.md", "CAPABILITY_CONTRACT.json", "EVIDENCE_INDEX.json", "CLAIM_GRAPH.json" ], "required_files": [ "PROJECT_PACK.json", "QUICK_START.md", "PROMPT_PREVIEW.md", "HUMAN_MANUAL.md", "AI_CONTEXT_PACK.md", "BOUNDARY_RISK_CARD.md", "PITFALL_LOG.md", "REPO_INSPECTION.json" ] }, "detail": { "capability_source": "Project Hit Packet + DownstreamValidationResult", "commands": [ { "command": "npx vibe-kanban", "label": "Node.js / npx · 官方安装入口", "source": "https://github.com/BloopAI/vibe-kanban#readme", "verified": true } ], "display_tags": [ "浏览器 Agent", "网页任务自动化", "浏览器自动化", "节点式流程编排", "评测体系" ], "eyebrow": "软件开发与交付", "glance": [ { "body": "判断自己是不是目标用户。", "label": "最适合谁", "value": "需要软件开发与交付能力，并使用 claude的用户" }, { "body": "先理解能力边界，再决定是否继续。", "label": "核心价值", "value": "Get 10X more out of Claude Code, Codex or any coding agent" }, { "body": "未完成验证前保持审慎。", "label": "继续前", "value": "publish to Doramagic.ai project surfaces" } ], "guardrail_source": "Boundary & Risk Card", "guardrails": [ { "body": "Prompt Preview 只展示流程，不证明项目已安装或运行。", "label": "Check 1", "value": "不要把试用当真实运行" }, { "body": "claude, claude_code", "label": "Check 2", "value": "确认宿主兼容" }, { "body": "publish to Doramagic.ai project surfaces", "label": "Check 3", "value": "先隔离验证" } ], "mode": "skill, recipe, host_instruction, eval, preflight", "pitfall_log": { "items": [ { "body": "GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Deployment(Other(Migration failed: error returned from database: (code: 1) no such column: ep.session_id))", "category": "安装坑", "evidence": [ "community_evidence:github | cevd_b34b2ea1b35a4dc2a4a0eb0681bdb883 | https://github.com/BloopAI/vibe-kanban/issues/2972 | 来源讨论提到 windows 相关条件，需在安装/试用前复核。" ], "severity": "high", "suggested_check": "来源问题仍为 open，Pack Agent 需要复核是否仍影响当前版本。", "title": "来源证据：Deployment(Other(Migration failed: error returned from database: (code: 1) no such column: ep.session_id))", "user_impact": "可能影响升级、迁移或版本选择。" }, { "body": "GitHub 社区证据显示该项目存在一个配置相关的待验证问题：Support for self-hosted projects and better export", "category": "配置坑", "evidence": [ "community_evidence:github | cevd_19d27caa9e34416a9f282869f76624b0 | https://github.com/BloopAI/vibe-kanban/issues/3396 | 来源类型 github_issue 暴露的待验证使用条件。" ], "severity": "high", "suggested_check": "来源问题仍为 open，Pack Agent 需要复核是否仍影响当前版本。", "title": "来源证据：Support for self-hosted projects and better export", "user_impact": "可能阻塞安装或首次运行。" }, { "body": "GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：[Proposal] JIRA Integration for Vibe Kanban", "category": "安全/权限坑", "evidence": [ "community_evidence:github | cevd_ab38fe97c4574e2da01ddedd71a4fbac | https://github.com/BloopAI/vibe-kanban/issues/2424 | 来源类型 github_issue 暴露的待验证使用条件。" ], "severity": "high", "suggested_check": "来源问题仍为 open，Pack Agent 需要复核是否仍影响当前版本。", "title": "来源证据：[Proposal] JIRA Integration for Vibe Kanban", "user_impact": "可能影响授权、密钥配置或安全边界。" }, { "body": "GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Pre-release v0.1.40-20260401153532", "category": "安装坑", "evidence": [ "community_evidence:github | cevd_f4b99d437a4f4fd4989d2b3ef036553b | https://github.com/BloopAI/vibe-kanban/releases/tag/v0.1.40-20260401153532 | 来源讨论提到 docker 相关条件，需在安装/试用前复核。" ], "severity": "medium", "suggested_check": "来源显示可能已有修复、规避或版本变化，说明书中必须标注适用版本。", "title": "来源证据：Pre-release v0.1.40-20260401153532", "user_impact": "可能阻塞安装或首次运行。" }, { "body": "GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Release v0.1.36", "category": "安装坑", "evidence": [ "community_evidence:github | cevd_527645be4e3f438e81757ef265a70d79 | https://github.com/BloopAI/vibe-kanban/releases/tag/v0.1.36-20260323174633 | 来源讨论提到 npm 相关条件，需在安装/试用前复核。" ], "severity": "medium", "suggested_check": "来源显示可能已有修复、规避或版本变化，说明书中必须标注适用版本。", "title": "来源证据：Release v0.1.36", "user_impact": "可能阻塞安装或首次运行。" }, { "body": "GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Release v0.1.43", "category": "安装坑", "evidence": [ "community_evidence:github | cevd_53704dc7171446fe86b2017f72212ddc | https://github.com/BloopAI/vibe-kanban/releases/tag/v0.1.43-20260417125614 | 来源讨论提到 node 相关条件，需在安装/试用前复核。" ], "severity": "medium", "suggested_check": "来源显示可能已有修复、规避或版本变化，说明书中必须标注适用版本。", "title": "来源证据：Release v0.1.43", "user_impact": "可能增加新用户试用和生产接入成本。" }, { "body": "项目面向 Claude/Cursor/Codex/Gemini/OpenCode 等宿主，或安装命令涉及用户配置目录。", "category": "配置坑", "evidence": [ "capability.host_targets | github_repo:1002125012 | https://github.com/BloopAI/vibe-kanban | host_targets=claude, claude_code" ], "severity": "medium", "suggested_check": "列出会写入的配置文件、目录和卸载/回滚步骤。", "title": "可能修改宿主 AI 配置", "user_impact": "安装可能改变本机 AI 工具行为，用户需要知道写入位置和回滚方法。" }, { "body": "README/documentation is current enough for a first validation pass.", "category": "能力坑", "evidence": [ "capability.assumptions | github_repo:1002125012 | https://github.com/BloopAI/vibe-kanban | README/documentation is current enough for a first validation pass." ], "severity": "medium", "suggested_check": "将假设转成下游验证清单。", "title": "能力判断依赖假设", "user_impact": "假设不成立时，用户拿不到承诺的能力。" }, { "body": "GitHub 社区证据显示该项目存在一个运行相关的待验证问题：Pre-release v0.1.39-20260331145823", "category": "运行坑", "evidence": [ "community_evidence:github | cevd_c005a56959634369929ce33eddbdc103 | https://github.com/BloopAI/vibe-kanban/releases/tag/v0.1.39-20260331145823 | 来源讨论提到 windows 相关条件，需在安装/试用前复核。" ], "severity": "medium", "suggested_check": "来源显示可能已有修复、规避或版本变化，说明书中必须标注适用版本。", "title": "来源证据：Pre-release v0.1.39-20260331145823", "user_impact": "可能阻塞安装或首次运行。" }, { "body": "GitHub 社区证据显示该项目存在一个维护/版本相关的待验证问题：[Request] Support RDS for self hosting in AWS", "category": "维护坑", "evidence": [ "community_evidence:github | cevd_f613b792c20942519560c0a286a82005 | https://github.com/BloopAI/vibe-kanban/issues/3405 | 来源类型 github_issue 暴露的待验证使用条件。" ], "severity": "medium", "suggested_check": "来源问题仍为 open，Pack Agent 需要复核是否仍影响当前版本。", "title": "来源证据：[Request] Support RDS for self hosting in AWS", "user_impact": "可能影响升级、迁移或版本选择。" }, { "body": "未记录 last_activity_observed。", "category": "维护坑", "evidence": [ "evidence.maintainer_signals | github_repo:1002125012 | https://github.com/BloopAI/vibe-kanban | last_activity_observed missing" ], "severity": "medium", "suggested_check": "补 GitHub 最近 commit、release、issue/PR 响应信号。", "title": "维护活跃度未知", "user_impact": "新项目、停更项目和活跃项目会被混在一起，推荐信任度下降。" }, { "body": "no_demo", "category": "安全/权限坑", "evidence": [ "downstream_validation.risk_items | github_repo:1002125012 | https://github.com/BloopAI/vibe-kanban | no_demo; severity=medium" ], "severity": "medium", "suggested_check": "进入安全/权限治理复核队列。", "title": "下游验证发现风险项", "user_impact": "下游已经要求复核，不能在页面中弱化。" }, { "body": "No sandbox install has been executed yet; downstream must verify before user use.", "category": "安全/权限坑", "evidence": [ "risks.safety_notes | github_repo:1002125012 | https://github.com/BloopAI/vibe-kanban | No sandbox install has been executed yet; downstream must verify before user use." ], "severity": "medium", "suggested_check": "转成明确权限清单和安全审查提示。", "title": "存在安全注意事项", "user_impact": "用户安装前需要知道权限边界和敏感操作。" }, { "body": "no_demo", "category": "安全/权限坑", "evidence": [ "risks.scoring_risks | github_repo:1002125012 | https://github.com/BloopAI/vibe-kanban | no_demo; severity=medium" ], "severity": "medium", "suggested_check": "把风险写入边界卡，并确认是否需要人工复核。", "title": "存在评分风险", "user_impact": "风险会影响是否适合普通用户安装。" }, { "body": "GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：Issue: Unclear Git + Bitbucket Setup for Vibe-Kanban (OpenCode) in Docker", "category": "安全/权限坑", "evidence": [ "community_evidence:github | cevd_7d289a7b68ee4299ae4a5e54b0e64e35 | https://github.com/BloopAI/vibe-kanban/issues/3410 | 来源讨论提到 docker 相关条件，需在安装/试用前复核。" ], "severity": "medium", "suggested_check": "来源问题仍为 open，Pack Agent 需要复核是否仍影响当前版本。", "title": "来源证据：Issue: Unclear Git + Bitbucket Setup for Vibe-Kanban (OpenCode) in Docker", "user_impact": "可能影响升级、迁移或版本选择。" }, { "body": "GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：Pre-release v0.1.37-20260327101540", "category": "安全/权限坑", "evidence": [ "community_evidence:github | cevd_d648fba4c94b4791ac2e7683f6cb1361 | https://github.com/BloopAI/vibe-kanban/releases/tag/v0.1.37-20260327101540 | 来源讨论提到 macos 相关条件，需在安装/试用前复核。" ], "severity": "medium", "suggested_check": "来源显示可能已有修复、规避或版本变化，说明书中必须标注适用版本。", "title": "来源证据：Pre-release v0.1.37-20260327101540", "user_impact": "可能影响授权、密钥配置或安全边界。" } ], "source": "ProjectPitfallLog + ProjectHitPacket + validation + community signals", "summary": "发现 19 个潜在踩坑项，其中 3 个为 high/blocking；最高优先级：安装坑 - 来源证据：Deployment(Other(Migration failed: error returned from database: (code: 1) no such column: ep.session_id))。", "title": "踩坑日志" }, "snapshot": { "contributors": 62, "forks": 2721, "license": "unknown", "note": "站点快照，非实时质量证明；用于开工前背景判断。", "stars": 26187 }, "source_url": "https://github.com/BloopAI/vibe-kanban", "steps": [ { "body": "不安装项目，先体验能力节奏。", "code": "preview", "title": "先试 Prompt" }, { "body": "理解输入、输出、失败模式和边界。", "code": "manual", "title": "读说明书" }, { "body": "把上下文交给宿主 AI 继续工作。", "code": "context", "title": "带给 AI" }, { "body": "进入主力环境前先完成安装入口与风险边界验证。", "code": "verify", "title": "沙箱验证" } ], "subtitle": "Get 10X more out of Claude Code, Codex or any coding agent", "title": "vibe-kanban 能力包", "trial_prompt": "# vibe-kanban - Prompt Preview\n\n> Copy the prompt below into your AI host before installing anything.\n> Its purpose is to let you safely feel the project's workflow, not to claim the project has already run.\n\n## Copy this prompt\n\n```text\nYou are using an independent Doramagic capability pack for BloopAI/vibe-kanban.\n\nProject:\n- Name: vibe-kanban\n- Repository: https://github.com/BloopAI/vibe-kanban\n- Summary: Get 10X more out of Claude Code, Codex or any coding agent\n- Host target: claude, claude_code\n\nGoal:\nHelp me evaluate this project for the following task without installing it yet: Get 10X more out of Claude Code, Codex or any coding agent\n\nBefore taking action:\n1. Restate my task, success standard, and boundary.\n2. Identify whether the next step requires tools, browser access, network access, filesystem access, credentials, package installation, or host configuration.\n3. Use only the Doramagic Project Pack, the upstream repository, and the source-linked evidence listed below.\n4. If a real command, install step, API call, file write, or host integration is required, mark it as \"requires post-install verification\" and ask for approval first.\n5. If evidence is missing, say \"evidence is missing\" instead of filling the gap.\n\nPreviewable capabilities:\n- Capability 1: Get 10X more out of Claude Code, Codex or any coding agent\n\nCapabilities that require post-install verification:\n- Capability 1: Use the source-backed project context to guide one small, checkable workflow step.\n\nCore service flow:\n1. page-project-introduction: Project Introduction. Produce one small intermediate artifact and wait for confirmation.\n2. page-key-concepts: Key Concepts. Produce one small intermediate artifact and wait for confirmation.\n3. page-development-setup: Development Setup. Produce one small intermediate artifact and wait for confirmation.\n4. page-backend-architecture: Backend Architecture. Produce one small intermediate artifact and wait for confirmation.\n5. page-frontend-architecture: Frontend Architecture. Produce one small intermediate artifact and wait for confirmation.\n\nSource-backed evidence to keep in mind:\n- https://github.com/BloopAI/vibe-kanban\n- https://github.com/BloopAI/vibe-kanban#readme\n- README.md\n- CLAUDE.md\n- AGENTS.md\n- crates/db/src/models/project.rs\n- crates/db/src/models/workspace.rs\n- crates/db/src/models/session.rs\n- crates/db/src/models/task.rs\n- crates/db/src/models/scratch.rs\n\nFirst response rules:\n1. Start Step 1 only.\n2. Explain the one service action you will perform first.\n3. Ask exactly three questions about my target workflow, success standard, and sandbox boundary.\n4. Stop and wait for my answers.\n\nStep 1 follow-up protocol:\n- After I answer the first three questions, stay in Step 1.\n- Produce six parts only: clarified task, success standard, boundary conditions, two or three options, tradeoffs for each option, and one recommendation.\n- End by asking whether I confirm the recommendation.\n- Do not move to Step 2 until I explicitly confirm.\n\nConversation rules:\n- Advance one step at a time and wait for confirmation after each small artifact.\n- Write outputs as recommendations or planned checks, not as completed execution.\n- Do not claim tests passed, files changed, commands ran, APIs were called, or the project was installed.\n- If the user asks for execution, first provide the sandbox setup, expected output, rollback, and approval checkpoint.\n```\n", "voices": [ { "body": "来源平台：github。github/github_issue: Support for self-hosted projects and better export（https://github.com/BloopAI/vibe-kanban/issues/3396）；github/github_issue: Deployment(Other(Migration failed: error returned from database: (code: （https://github.com/BloopAI/vibe-kanban/issues/2972）；github/github_issue: Issue: Unclear Git + Bitbucket Setup for Vibe-Kanban (OpenCode) in Docke（https://github.com/BloopAI/vibe-kanban/issues/3410）；github/github_issue: [Proposal] JIRA Integration for Vibe Kanban（https://github.com/BloopAI/vibe-kanban/issues/2424）；github/github_issue: Git repository is wiped after deleting Vibe Kanban workspace（https://github.com/BloopAI/vibe-kanban/issues/3406）；github/github_issue: [Request] Support RDS for self hosting in AWS（https://github.com/BloopAI/vibe-kanban/issues/3405）；github/github_release: Release v0.1.43（https://github.com/BloopAI/vibe-kanban/releases/tag/v0.1.43-20260417125614）；github/github_release: Pre-release v0.1.41-20260403182044（https://github.com/BloopAI/vibe-kanban/releases/tag/v0.1.41-20260403182044）；github/github_release: Pre-release v0.1.40-20260401153532（https://github.com/BloopAI/vibe-kanban/releases/tag/v0.1.40-20260401153532）；github/github_release: Pre-release v0.1.39-20260331145823（https://github.com/BloopAI/vibe-kanban/releases/tag/v0.1.39-20260331145823）；github/github_release: remote-v0.1.26（https://github.com/BloopAI/vibe-kanban/releases/tag/remote-v0.1.26）；github/github_release: Pre-release v0.1.37-20260327101540（https://github.com/BloopAI/vibe-kanban/releases/tag/v0.1.37-20260327101540）。这些是项目级外部声音，不作为单独质量证明。", "items": [ { "kind": "github_issue", "source": "github", "title": "Support for self-hosted projects and better export", "url": "https://github.com/BloopAI/vibe-kanban/issues/3396" }, { "kind": "github_issue", "source": "github", "title": "Deployment(Other(Migration failed: error returned from database: (code: ", "url": "https://github.com/BloopAI/vibe-kanban/issues/2972" }, { "kind": "github_issue", "source": "github", "title": "Issue: Unclear Git + Bitbucket Setup for Vibe-Kanban (OpenCode) in Docke", "url": "https://github.com/BloopAI/vibe-kanban/issues/3410" }, { "kind": "github_issue", "source": "github", "title": "[Proposal] JIRA Integration for Vibe Kanban", "url": "https://github.com/BloopAI/vibe-kanban/issues/2424" }, { "kind": "github_issue", "source": "github", "title": "Git repository is wiped after deleting Vibe Kanban workspace", "url": "https://github.com/BloopAI/vibe-kanban/issues/3406" }, { "kind": "github_issue", "source": "github", "title": "[Request] Support RDS for self hosting in AWS", "url": "https://github.com/BloopAI/vibe-kanban/issues/3405" }, { "kind": "github_release", "source": "github", "title": "Release v0.1.43", "url": "https://github.com/BloopAI/vibe-kanban/releases/tag/v0.1.43-20260417125614" }, { "kind": "github_release", "source": "github", "title": "Pre-release v0.1.41-20260403182044", "url": "https://github.com/BloopAI/vibe-kanban/releases/tag/v0.1.41-20260403182044" }, { "kind": "github_release", "source": "github", "title": "Pre-release v0.1.40-20260401153532", "url": "https://github.com/BloopAI/vibe-kanban/releases/tag/v0.1.40-20260401153532" }, { "kind": "github_release", "source": "github", "title": "Pre-release v0.1.39-20260331145823", "url": "https://github.com/BloopAI/vibe-kanban/releases/tag/v0.1.39-20260331145823" }, { "kind": "github_release", "source": "github", "title": "remote-v0.1.26", "url": "https://github.com/BloopAI/vibe-kanban/releases/tag/remote-v0.1.26" }, { "kind": "github_release", "source": "github", "title": "Pre-release v0.1.37-20260327101540", "url": "https://github.com/BloopAI/vibe-kanban/releases/tag/v0.1.37-20260327101540" } ], "status": "已收录 12 条来源", "title": "社区讨论" } ] }, "homepage_card": { "category": "软件开发与交付", "desc": "Get 10X more out of Claude Code, Codex or any coding agent", "effort": "安装已验证", "forks": 2721, "icon": "code", "name": "vibe-kanban 能力包", "risk": "可发布", "slug": "vibe-kanban", "stars": 26187, "tags": [ "浏览器 Agent", "网页任务自动化", "浏览器自动化", "节点式流程编排", "评测体系" ], "thumb": "gray", "type": "Skill Pack" }, "manual": { "markdown": "# https://github.com/BloopAI/vibe-kanban 项目说明书\n\n生成时间：2026-05-18 03:48:47 UTC\n\n## 目录\n\n- [Project Introduction](#page-project-introduction)\n- [Key Concepts](#page-key-concepts)\n- [Development Setup](#page-development-setup)\n- [Backend Architecture](#page-backend-architecture)\n- [Frontend Architecture](#page-frontend-architecture)\n- [Crate Reference](#page-crate-reference)\n- [Coding Agent Executors](#page-executors)\n- [MCP Server Integration](#page-mcp-integration)\n- [Relay and Remote Access](#page-relay-remote-access)\n- [Database and Data Models](#page-database-models)\n- [Deployment and Infrastructure](#page-deployment-infrastructure)\n\n\n\n## Project Introduction\n\n### 相关页面\n\n相关主题：[Key Concepts](#page-key-concepts), [Development Setup](#page-development-setup)\n\n
\n相关源码文件\n\n以下源码文件用于生成本页说明：\n\n- [README.md](https://github.com/BloopAI/vibe-kanban/blob/main/README.md)\n- [packages/web-core/src/shared/keyboard/useWorkspaceShortcuts.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/keyboard/useWorkspaceShortcuts.ts)\n- [packages/web-core/src/shared/stores/useUiPreferencesStore.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/stores/useUiPreferencesStore.ts)\n- [packages/ui/src/components/CommandBar.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/ui/src/components/CommandBar.tsx)\n- [packages/web-core/src/shared/components/WorkspacesSidebar.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/components/WorkspacesSidebar.tsx)\n- [crates/server/src/routes/oauth.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/server/src/routes/oauth.rs)\n
\n\n# Project Introduction\n\nVibe Kanban is a specialized project planning and agent execution platform designed for software engineering teams that leverage AI coding agents. The project provides an integrated environment where teams can plan work using kanban issues and execute coding tasks through dedicated workspaces that give AI agents controlled access to code branches, terminals, and development servers.\n\n## Purpose and Scope\n\nThe primary purpose of Vibe Kanban is to address the workflow inefficiency that emerges when software engineers spend significant time planning and reviewing AI coding agent activities. By providing a structured kanban interface combined with agent execution capabilities, the platform enables teams to:\n\n- Plan and prioritize work through visual kanban boards\n- Execute coding tasks through multiple supported AI agents\n- Review AI-generated changes with inline commenting capabilities\n- Preview applications directly within the development environment\n- Create and merge pull requests without context switching\n\n资料来源：[README.md](https://github.com/BloopAI/vibe-kanban/blob/main/README.md)\n\n## Supported AI Agents\n\nVibe Kanban integrates with a wide variety of coding agents, allowing teams to choose the most appropriate tool for their needs. The platform supports the following agents:\n\n| Agent | Description |\n|-------|-------------|\n| Claude Code | Anthropic's CLI agent |\n| Codex | OpenAI's coding agent |\n| Gemini CLI | Google's CLI agent |\n| GitHub Copilot | GitHub's AI pair programmer |\n| Amp | Alternative agent |\n| Cursor | Cursor AI IDE agent |\n| OpenCode | Open source agent |\n| Droid | Android development agent |\n| CCR | Custom agent integration |\n| Qwen Code | Alibaba's coding agent |\n\n资料来源：[README.md](https://github.com/BloopAI/vibe-kanban/blob/main/README.md)\n\n## Architecture Overview\n\nVibe Kanban follows a monorepo architecture with multiple packages organized for different concerns.\n\n```mermaid\ngraph TD\n subgraph \"packages/\"\n WC[\"web-core
(packages/web-core)\"]\n UI[\"ui
(packages/ui)\"]\n REM[\"remote-web
(packages/remote-web)\"]\n end\n \n subgraph \"crates/\"\n SERVER[\"server
(crates/server)\"]\n end\n \n WC <--> SERVER\n UI <--> WC\n REM --> SERVER\n```\n\n### Core Packages\n\nThe web application is built using multiple TypeScript packages:\n\n- **packages/web-core**: Contains shared hooks, stores, dialogs, and components that form the business logic layer\n- **packages/ui**: Reusable UI components including CommandBar, WorkspaceSidebar, and various input components\n- **packages/remote-web**: Pages and layouts for the remote/web deployment scenarios\n\nThe backend is implemented in Rust using Actix-web, providing OAuth authentication and API endpoints.\n\n资料来源：[packages/web-core/src/shared/keyboard/useWorkspaceShortcuts.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/keyboard/useWorkspaceShortcuts.ts)\n\n## Key Features\n\n### Kanban Issue Management\n\nThe kanban board provides a visual interface for creating, prioritizing, and assigning issues. Teams can organize work privately or collaboratively, with issues flowing through customizable status columns.\n\n### Workspace Execution\n\nWorkspaces provide isolated environments for AI agents to execute tasks. Each workspace includes:\n\n- A dedicated git branch for the task\n- Terminal access for command execution\n- Integrated dev server for live preview\n- Diff viewing and inline commenting\n\n```mermaid\ngraph LR\n A[Kanban Issue] --> B[Create Workspace]\n B --> C[Agent Executes on Branch]\n C --> D[Review Diffs]\n D --> E[Inline Comments]\n E --> F[Create PR]\n F --> G[Merge]\n```\n\n资料来源：[packages/ui/src/components/WorkspacesSidebar.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/ui/src/components/WorkspacesSidebar.tsx)\n\n### Command Bar Navigation\n\nThe application features a comprehensive command palette (activated via `Cmd+K`) that provides quick access to all major functionality:\n\n- Repository and branch selection\n- Status and priority filtering\n- Issue navigation and creation\n- Workspace management\n\n```typescript\n// Keyboard shortcut mappings from useWorkspaceShortcuts.ts\nconst SHORTCUTS = {\n 'v>p': 'Toggle Preview Mode',\n 'v>s': 'Toggle Left Sidebar', \n 'v>h': 'Toggle Left Main Panel',\n 'x>p': 'Git Create PR',\n 'x>m': 'Git Merge',\n 'x>r': 'Git Rebase',\n 'x>u': 'Git Push',\n 't>d': 'Toggle Dev Server',\n 'r>s': 'Run Setup Script',\n 'r>c': 'Run Cleanup Script'\n};\n```\n\n资料来源：[packages/web-core/src/shared/keyboard/useWorkspaceShortcuts.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/keyboard/useWorkspaceShortcuts.ts)\n\n### Attachment and Comment System\n\nIssues support rich commenting with file attachments. The system handles upload progression, confirmation states, and attachment metadata tracking.\n\n```typescript\n// Attachment state transitions\ntype AttachmentStatus = 'uploading' | 'confirming' | 'completed';\n\ninterface LocalAttachmentMetadata {\n path: string;\n pending_status: AttachmentStatus;\n upload_progress: number;\n}\n```\n\n资料来源：[packages/web-core/src/shared/hooks/useAzureAttachments.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/hooks/useAzureAttachments.ts)\n\n### Pending Approval Workflow\n\nWhen agents require human authorization for sensitive operations, the system displays a pending approval entry that allows users to approve or deny requests with explanatory messages.\n\n```mermaid\nstateDiagram-v2\n [*] --> AgentRequestsAction\n AgentRequestsAction --> PendingApproval\n PendingApproval --> Approved: User Approves\n PendingApproval --> Denied: User Denies\n Approved --> [*]\n Denied --> AgentResubmits: Agent Adjusts\n AgentResubmits --> PendingApproval\n```\n\n资料来源：[packages/web-core/src/shared/components/NormalizedConversation/PendingApprovalEntry.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/components/NormalizedConversation/PendingApprovalEntry.tsx)\n\n## UI State Management\n\nThe application maintains comprehensive UI state through Zustand stores, handling layout modes, panel visibility, and workspace-specific configurations.\n\n```typescript\n// Core UI preferences from useUiPreferencesStore.ts\ninterface UiPreferencesState {\n layoutMode: 'workspaces' | 'kanban' | 'accordion';\n isLeftSidebarVisible: boolean;\n isRightSidebarVisible: boolean;\n isTerminalVisible: boolean;\n paneSizes: Record;\n workspacePanelStates: Record;\n}\n```\n\n资料来源：[packages/web-core/src/shared/stores/useUiPreferencesStore.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/stores/useUiPreferencesStore.ts)\n\n## OAuth Authentication\n\nThe server implements OAuth authentication flows for secure user sessions, returning HTML responses for browser-based authentication callbacks.\n\n```rust\n// Simplified OAuth response structure\nstruct OAuthCallback {\n message: String, // Success or error message\n app_icon: Vec, // Base64 encoded application icon\n}\n```\n\n资料来源：[crates/server/src/routes/oauth.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/server/src/routes/oauth.rs)\n\n## Git Operations\n\nThe platform integrates comprehensive Git functionality directly into the workspace workflow:\n\n| Operation | Shortcut | Description |\n|-----------|----------|-------------|\n| Create Pull Request | `x>p` | Generate PR with AI-written descriptions |\n| Merge | `x>m` | Merge approved pull requests |\n| Rebase | `x>r` | Rebase branch onto target |\n| Push | `x>u` | Push changes to remote |\n| Force Push | (Dialog) | Force push with warning confirmation |\n\nForce push operations require explicit user confirmation through a dedicated dialog due to the destructive nature of the operation.\n\n资料来源：[packages/web-core/src/shared/dialogs/command-bar/ForcePushDialog.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/dialogs/command-bar/ForcePushDialog.tsx)\n\n## Conflict Resolution\n\nWhen Git operations encounter conflicts, the application provides a dedicated dialog to help users resolve them, displaying conflicted files and offering options to create new sessions or continue with existing ones.\n\n```typescript\ninterface ResolveConflictsDialogProps {\n conflictedFiles: string[];\n profiles?: ExecutorProfile[];\n hasExistingSession: boolean;\n createNewSession: boolean;\n onCreateNewSessionChange: (value: boolean) => void;\n}\n```\n\n资料来源：[packages/web-core/src/shared/dialogs/tasks/ResolveConflictsDialog.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/dialogs/tasks/ResolveConflictsDialog.tsx)\n\n## Development Workflow Summary\n\n```mermaid\ngraph TD\n A[Plan Issue on Kanban] --> B[Create Workspace]\n B --> C[Select Agent]\n C --> D[Agent Executes Tasks]\n D --> E{Requires Approval?}\n E -->|Yes| F[User Reviews & Approves/Denies]\n F --> G[Agent Continues]\n E -->|No| G\n G --> H[Review Diffs & Comments]\n H --> I[Create Pull Request]\n I --> J[Merge to Main]\n J --> K[Archive Workspace]\n```\n\nThe platform streamlines the entire development lifecycle from initial planning through final merge, keeping all stakeholders in a single interface throughout the process.\n\n---\n\n\n\n## Key Concepts\n\n### 相关页面\n\n相关主题：[Project Introduction](#page-project-introduction), [Database and Data Models](#page-database-models)\n\n
\n相关源码文件\n\n以下源码文件用于生成本页说明：\n\n- [packages/web-core/src/shared/stores/useUiPreferencesStore.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/stores/useUiPreferencesStore.ts)\n- [packages/ui/src/components/WorkspacesSidebar.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/ui/src/components/WorkspacesSidebar.tsx)\n- [packages/web-core/src/shared/components/tasks/TaskDetails/ProcessesTab.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/components/tasks/TaskDetails/ProcessesTab.tsx)\n- [packages/ui/src/components/IssueCommentsSection.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/ui/src/components/IssueCommentsSection.tsx)\n- [packages/web-core/src/shared/keyboard/useWorkspaceShortcuts.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/keyboard/useWorkspaceShortcuts.ts)\n- [packages/web-core/src/shared/dialogs/command-bar/WorkspaceSelectionDialog.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/dialogs/command-bar/WorkspaceSelectionDialog.tsx)\n
\n\n# Key Concepts\n\nVibe Kanban is a development workflow management tool designed for software engineering teams that work with AI coding agents. The application combines kanban-based issue planning with workspace-based agent execution, enabling engineers to plan, delegate, and review AI-assisted coding work within a unified interface.\n\n## Core Architecture Overview\n\nThe system is built around several interconnected concepts that work together to manage the lifecycle of AI-assisted development tasks.\n\n```mermaid\ngraph TD\n A[Organizations] --> B[Projects]\n B --> C[Kanban Issues]\n B --> D[Workspaces]\n C -->|Assign to| D\n D --> E[Sessions]\n D --> F[Scratches]\n E --> G[Processes]\n G --> H[Git Operations]\n E --> I[Attachments]\n D --> J[Dev Server]\n```\n\n## Projects\n\nProjects serve as the top-level organizational unit in Vibe Kanban. Each project contains its own kanban board and associated workspaces.\n\n### Project Properties\n\n| Property | Type | Description |\n|----------|------|-------------|\n| `id` | string | Unique identifier |\n| `name` | string | Display name |\n| `color` | string | Hex color for UI identification |\n| `updated_at` | timestamp | Last modification time |\n\nProjects are organized under organizations and contain all related kanban issues and workspaces. 资料来源：[packages/remote-web/src/pages/HomePage.tsx:60-80]()\n\n### Project Card Component\n\nThe `ProjectCard` component renders project items in the home page grid layout, displaying project name and providing navigation to individual project views. 资料来源：[packages/remote-web/src/pages/HomePage.tsx:80-100]()\n\n## Workspaces\n\nWorkspaces are the execution environment where coding agents operate. Each workspace provides an isolated branch, terminal access, and a dev server for a single coding agent.\n\n### Workspace Lifecycle\n\n```mermaid\nstateDiagram-v2\n [*] --> Active: Created\n Active --> Running: Agent starts\n Running --> Active: Agent pauses\n Active --> Archived: User archives\n Running --> Completed: Task finished\n Archived --> Active: User restores\n Completed --> [*]\n Active --> [*]\n```\n\n### Workspace Properties\n\n| Property | Type | Description |\n|----------|------|-------------|\n| `id` | string | Unique workspace identifier |\n| `name` | string | Display name |\n| `branch` | string | Git branch name |\n| `filesChanged` | number | Count of modified files |\n| `linesAdded` | number | Lines of code added |\n| `linesRemoved` | number | Lines of code removed |\n| `isRunning` | boolean | Agent currently executing |\n| `isPinned` | boolean | Pinned for quick access |\n| `isArchived` | boolean | Archived state |\n| `hasPendingApproval` | boolean | Awaiting human approval |\n| `hasRunningDevServer` | boolean | Dev server active |\n| `hasUnseenActivity` | boolean | New activity since last view |\n| `latestProcessCompletedAt` | timestamp | Last process completion |\n| `latestProcessStatus` | string | Status of latest process |\n| `prStatus` | string | Pull request status |\n\n资料来源：[packages/ui/src/components/WorkspacesSidebar.tsx:20-40]()\n\n### Workspace Panel State Management\n\nThe UI preferences store manages workspace panel visibility states, allowing users to toggle the left main panel and persist these preferences. 资料来源：[packages/web-core/src/shared/stores/useUiPreferencesStore.ts:30-50]()\n\n## Sessions\n\nSessions represent individual agent execution instances within a workspace. Each time a coding agent runs, it creates a new session that captures the execution context.\n\n### Session Attributes\n\nSessions track the complete execution context including:\n\n- **Profile Configuration**: The AI model and agent settings used\n- **Context Window**: Available memory and context for the agent\n- **Execution History**: Commands executed and outputs generated\n- **Process Chain**: Sequential processes that ran during the session\n\n资料来源：[packages/web-core/src/shared/components/tasks/TaskDetails/ProcessesTab.tsx:20-60]()\n\n### Process Tracking\n\nEach session contains multiple processes that represent discrete units of work:\n\n```mermaid\ngraph LR\n A[Process Start] --> B[Running]\n B --> C[User Approval Point]\n C -->|Approved| B\n C -->|Rejected| D[Stopped]\n B --> E[Completed]\n D --> E\n```\n\nThe process tab displays:\n\n- Process status (running, completed, stopped)\n- Started timestamp\n- Completed timestamp\n- Copy logs functionality\n\n资料来源：[packages/web-core/src/shared/components/tasks/TaskDetails/ProcessesTab.tsx:60-100]()\n\n## Kanban Issues\n\nKanban issues are the planning units in Vibe Kanban. They can be created, prioritized, and assigned to workspaces for execution.\n\n### Issue Comments\n\nThe `IssueCommentsSection` component handles all comment-related functionality for issues:\n\n```typescript\ninterface IssueCommentsSectionProps {\n comments: IssueCommentData[];\n commentInput: string;\n editingCommentId: string | null;\n editingValue: string;\n reactionsByCommentId: Map;\n localAttachments?: LocalAttachmentMetadata[];\n // ... additional handlers\n}\n```\n\n资料来源：[packages/ui/src/components/IssueCommentsSection.tsx:1-30]()\n\n### Comment Features\n\n| Feature | Description |\n|---------|-------------|\n| Add Comment | Submit new comments on issues |\n| Edit Comment | Modify existing comments |\n| Delete Comment | Remove comments |\n| Reactions | Add emoji reactions to comments |\n| Reply | Quote and reply to specific comments |\n| Attachments | Upload files to comments |\n\n### Issue Priority and Status\n\nIssues support priority levels and status tracking, accessible through the command bar. Priority labels include urgency indicators, while status values track issue progression through workflow states. 资料来源：[packages/ui/src/components/CommandBar.tsx:80-100]()\n\n## Scratches\n\nScratches are temporary execution spaces that allow quick experimentation or notes without creating a full workspace. They share the workspace execution environment but are not persisted in the same way.\n\n## Git Operations\n\nVibe Kanban integrates Git operations directly into the workspace workflow:\n\n| Operation | Shortcut | Description |\n|-----------|----------|-------------|\n| Create PR | `x>p` | Create pull request |\n| Merge | `x>m` | Merge current branch |\n| Rebase | `x>r` | Rebase onto target branch |\n| Push | `x>u` | Push changes |\n| Force Push | Dialog | Force push with confirmation |\n\n资料来源：[packages/web-core/src/shared/keyboard/useWorkspaceShortcuts.ts:1-20]()\n\n### Conflict Resolution\n\nWhen conflicts occur during Git operations, the `ResolveConflictsDialog` handles conflict detection and resolution workflows, allowing users to select agents and profiles for creating new resolution sessions. 资料来源：[packages/web-core/src/shared/dialogs/tasks/ResolveConflictsDialog.tsx:50-80]()\n\n## UI Layout and Navigation\n\n### Layout Modes\n\nVibe Kanban supports two primary layout modes:\n\n| Mode | Description |\n|------|-------------|\n| `kanban` | Kanban board view for issue planning |\n| `workspaces` | Workspace-focused view for agent execution |\n\nThe layout mode can be toggled via the UI preferences store. 资料来源：[packages/web-core/src/shared/stores/useUiPreferencesStore.ts:20-30]()\n\n### Keyboard Shortcuts\n\nComprehensive keyboard shortcuts enable efficient workflow management:\n\n| Category | Shortcut | Action |\n|----------|----------|--------|\n| View | `v>p` | Toggle preview mode |\n| View | `v>s` | Toggle left sidebar |\n| View | `v>h` | Toggle left main panel |\n| Git | `x>p` | Create PR |\n| Git | `x>m` | Merge |\n| Git | `x>r` | Rebase |\n| Git | `x>u` | Push |\n| Copy | `y>p` | Copy workspace path |\n| Copy | `y>l` | Copy raw logs |\n| Terminal | `t>d` | Toggle dev server |\n| Terminal | `t>w` | Toggle wrap lines |\n| Scripts | `r>s` | Run setup script |\n| Scripts | `r>c` | Run cleanup script |\n\n资料来源：[packages/web-core/src/shared/keyboard/useWorkspaceShortcuts.ts:1-30]()\n\n### Sidebar Components\n\nThe `WorkspacesSidebar` provides the main navigation interface with sections for:\n\n- Active workspaces\n- Draft workspaces (in creation)\n- Archived workspaces\n- Needs attention section (with raised hand indicator)\n\nWorkspaces can be filtered and sorted, with visual indicators for running agents, pending approvals, and unseen activity. 资料来源：[packages/ui/src/components/WorkspacesSidebar.tsx:10-50]()\n\n## Command Bar\n\nThe command bar (`CommandBar`) provides quick access to all application actions through a searchable interface:\n\n### Command Item Types\n\n| Type | Search Label Format |\n|------|---------------------|\n| `page` | `{pageId} {label}` |\n| `repo` | `{repoId} {displayName}` |\n| `branch` | `{branchName}` |\n| `status` | `{statusId} {statusName}` |\n| `priority` | `{priorityId} {priorityName}` |\n| `issue` | `{issueId} {simpleId} {title}` |\n| `createSubIssue` | `create new issue` |\n\n资料来源：[packages/ui/src/components/CommandBar.tsx:100-130]()\n\n### Workspace Selection\n\nThe `WorkspaceSelectionDialog` enables linking kanban issues to workspaces, displaying available workspaces with their branch information and archive status. 资料来源：[packages/web-core/src/shared/dialogs/command-bar/WorkspaceSelectionDialog.tsx:30-60]()\n\n## Data Flow Architecture\n\n```mermaid\ngraph TD\n subgraph Frontend\n A[React Components] --> B[Zustand Stores]\n B --> C[API Client]\n end\n \n subgraph Backend\n C --> D[Rust Server]\n D --> E[Database]\n D --> F[OAuth Handler]\n end\n \n B -->|Optimistic Updates| A\n C -->|REST API| D\n D -->|CRUD| E\n```\n\n## File Tree Persistence\n\nThe UI preferences store persists file tree collapsed paths per workspace using a keyed storage system:\n\n```typescript\nconst key = workspaceId ? `file-tree:${workspaceId}` : '';\nconst paths = useUiPreferencesStore((s) => s.collapsedPaths[key] ?? []);\n```\n\nThis ensures that file tree expansion states are preserved across sessions and workspace switches. 资料来源：[packages/web-core/src/shared/stores/useUiPreferencesStore.ts:70-100]()\n\n## Integration Points\n\n### OAuth Flow\n\nThe Rust server handles OAuth authentication flows, returning branded HTML pages for authentication completion. 资料来源：[crates/server/src/routes/oauth.rs:1-30]()\n\n### GitHub CLI Setup\n\nThe `GhCliSetupDialog` guides users through GitHub CLI installation and authentication, with help instructions for common error variants. 资料来源：[packages/web-core/src/shared/dialogs/auth/GhCliSetupDialog.tsx:1-50]()\n\n## Related Documentation\n\n- [Installation Guide](./installation.md)\n- [Getting Started](./getting-started.md)\n- [API Reference](./api-reference.md)\n- [Configuration](./configuration.md)\n\n---\n\n\n\n## Development Setup\n\n### 相关页面\n\n相关主题：[Project Introduction](#page-project-introduction), [Backend Architecture](#page-backend-architecture)\n\n
\n相关源码文件\n\n以下源码文件用于生成本页说明：\n\n- [npx-cli/README.md](https://github.com/BloopAI/vibe-kanban/blob/main/npx-cli/README.md)\n- [npx-cli/package.json](https://github.com/BloopAI/vibe-kanban/blob/main/npx-cli/package.json)\n- [README.md](https://github.com/BloopAI/vibe-kanban/blob/main/README.md)\n- [packages/web-core/src/shared/hooks/useAzureAttachments.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/hooks/useAzureAttachments.ts)\n- [packages/web-core/src/shared/keyboard/useWorkspaceShortcuts.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/keyboard/useWorkspaceShortcuts.ts)\n
\n\n# Development Setup\n\nThis guide covers the development environment setup for Vibe Kanban, a visual project management tool for developers that integrates with git repositories and coding agents.\n\n## Project Architecture Overview\n\nVibe Kanban is a monorepo application built with multiple technologies:\n\n```mermaid\ngraph TD\n subgraph \"Frontend (TypeScript/React)\"\n A[packages/web-core] --> B[packages/ui]\n A --> C[packages/remote-web]\n end\n \n subgraph \"CLI Layer\"\n D[npx-cli] --> A\n D --> E[vibe-kanban-mcp]\n end\n \n subgraph \"Backend (Rust)\"\n F[crates/server]\n end\n \n D --> F\n```\n\n## Prerequisites\n\n### System Requirements\n\n| Requirement | Version | Purpose |\n|-------------|---------|---------|\n| Node.js | >= 20.19.0 | Frontend runtime and CLI |\n| Rust | Stable toolchain | Backend server |\n| pnpm | Latest | Package management |\n\n### Required Tools\n\n1. **Coding Agent Authentication** - Configure authentication for your preferred coding agent (Claude Code, Codex, Gemini CLI, etc.)\n2. **Git** - Repository operations and worktree management\n3. **Azure CLI** (optional) - For attachment upload functionality\n\n## Repository Structure\n\n```\nvibe-kanban/\n├── packages/\n│ ├── web-core/ # Core React hooks, stores, and components\n│ ├── ui/ # Shared UI components\n│ ├── remote-web/ # Web application pages\n│ └── public/ # Static assets\n├── crates/\n│ └── server/ # Rust backend server\n├── npx-cli/ # CLI entry point\n└── scripts/ # Build and development scripts\n```\n\n资料来源：[npx-cli/README.md:1-20](https://github.com/BloopAI/vibe-kanban/blob/main/npx-cli/README.md)\n\n## Installation\n\n### 1. Clone the Repository\n\n```bash\ngit clone https://github.com/BloopAI/vibe-kanban\ncd vibe-kanban\n```\n\n### 2. Install Dependencies\n\n```bash\nnpm install -g pnpm\npnpm install\n```\n\n### 3. Build the CLI\n\n```bash\ncd npx-cli\npnpm build\n```\n\nThe build script uses esbuild to bundle the TypeScript source:\n\n```javascript\n// npx-cli/package.json\n{\n \"scripts\": {\n \"build\": \"esbuild src/cli.ts --bundle --platform=node --target=node20 --format=cjs --outfile=bin/cli.js\"\n }\n}\n```\n\n资料来源：[npx-cli/package.json:8](https://github.com/BloopAI/vibe-kanban/blob/main/npx-cli/package.json)\n\n## Development Workflow\n\n### Running the Application\n\n```bash\nnpx vibe-kanban\n```\n\nThis launches the application locally and opens it in your browser automatically.\n\n### Available CLI Commands\n\n```bash\nnpx vibe-kanban --help\nnpx vibe-kanban --version\nnpx vibe-kanban review --help\nnpx vibe-kanban mcp --help\n```\n\n资料来源：[npx-cli/README.md:12-17](https://github.com/BloopAI/vibe-kanban/blob/main/npx-cli/README.md)\n\n## Hotkeys Reference\n\nThe application provides keyboard shortcuts for common actions:\n\n| Shortcut | Action |\n|----------|--------|\n| `v>p` | Toggle preview mode |\n| `v>s` | Toggle left sidebar |\n| `v>h` | Toggle left main panel |\n| `x>p` | Git create PR |\n| `x>m` | Git merge |\n| `x>r` | Git rebase |\n| `x>u` | Git push |\n| `y>p` | Copy workspace path |\n| `y>l` | Copy raw logs |\n| `t>d` | Toggle dev server |\n| `t>w` | Toggle wrap lines |\n| `r>s` | Run setup script |\n| `r>c` | Run cleanup script |\n\n资料来源：[packages/web-core/src/shared/keyboard/useWorkspaceShortcuts.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/keyboard/useWorkspaceShortcuts.ts)\n\n## State Management\n\nThe application uses Zustand stores for state management:\n\n```mermaid\ngraph TD\n A[UI Store] -->|paneSizes, collapsedPaths| B[useUiPreferencesStore]\n C[Workspace Store] -->|diff data| D[useWorkspaceDiffStore]\n E[Project Store] -->|organizations, projects| F[Remote Data]\n```\n\n### Key Stores\n\n| Store | Purpose | Key State |\n|-------|---------|-----------|\n| `useUiPreferencesStore` | UI layout preferences | paneSizes, collapsedPaths, layoutMode |\n| `useWorkspaceDiffStore` | GitHub comments and diffs | comments, file changes |\n\n资料来源：[packages/web-core/src/shared/stores/useUiPreferencesStore.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/stores/useUiPreferencesStore.ts)\n\n## Attachment Handling\n\nFile attachments use Azure Blob Storage for uploads:\n\n```mermaid\nsequenceDiagram\n participant User\n participant UI as React Components\n participant API as confirmAttachmentUpload\n participant Azure as Azure Blob Storage\n \n User->>UI: Select file\n UI->>Azure: Upload file chunk\n Azure-->>UI: Upload progress (0-100%)\n UI->>API: Confirm upload\n API-->>UI: Return attachment ID\n```\n\nThe attachment confirmation payload includes:\n\n```typescript\n{\n project_id: string,\n upload_id: string,\n filename: string,\n content_type: string,\n size_bytes: number,\n hash: string,\n issue_id: string,\n comment_id: string\n}\n```\n\n资料来源：[packages/web-core/src/shared/hooks/useAzureAttachments.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/hooks/useAzureAttachments.ts)\n\n## Git Integration\n\n### Worktree-Based Development\n\nVibe Kanban creates isolated git worktrees for each task attempt, enabling:\n\n- Parallel development on multiple features\n- Clean separation between task branches\n- Easy diff viewing of agent changes\n\n### Supported Git Operations\n\n| Operation | Shortcut | Description |\n|-----------|----------|-------------|\n| Create PR | `x>p` | Create pull request with AI-generated description |\n| Merge | `x>m` | Merge changes back to main |\n| Rebase | `x>r` | Rebase current branch |\n| Push | `x>u` | Push changes |\n| Force Push | Dialog | Force push with confirmation dialog |\n\n## Backend Server (Rust)\n\nThe backend server handles OAuth flows and API requests:\n\n```rust\n// OAuth flow returns HTML response\nResponse::builder()\n .status(StatusCode::OK)\n .header(\"content-type\", \"text/html; charset=utf-8\")\n .body(body)\n```\n\n资料来源：[crates/server/src/routes/oauth.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/server/src/routes/oauth.rs)\n\n## Troubleshooting\n\n### Common Setup Issues\n\n1. **Node Version Mismatch**\n - Ensure Node.js >= 20.19.0\n - Use `nvm use` or update Node installation\n\n2. **CLI Not Found After Build**\n - Run `pnpm build` in the npx-cli directory\n - Ensure bin directory is in PATH\n\n3. **Authentication Failures**\n - Verify coding agent authentication\n - Check GitHub CLI authentication with `gh auth status`\n\n## Documentation\n\nFor more information, visit:\n\n- [Official Documentation](https://vibekanban.com/docs)\n- [Self-Hosting Guide](https://vibekanban.com/docs/self-hosting/deploy-docker)\n- [Supported Coding Agents](https://vibekanban.com/docs/supported-coding-agents)\n- [GitHub Discussions](https://github.com/BloopAI/vibe-kanban/discussions)\n\n## Contributing\n\nIdeas and changes should be raised via:\n\n1. [GitHub Discussions](https://github.com/BloopAI/vibe-kanban/discussions)\n2. [Discord](https://discord.gg/AC4nwVtJM3)\n\n资料来源：[README.md:45-50](https://github.com/BloopAI/vibe-kanban/blob/main/README.md)\n\n---\n\n\n\n## Backend Architecture\n\n### 相关页面\n\n相关主题：[Crate Reference](#page-crate-reference), [Database and Data Models](#page-database-models), [Coding Agent Executors](#page-executors)\n\n
\n相关源码文件\n\n以下源码文件用于生成本页说明：\n\n- [crates/server/src/lib.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/server/src/lib.rs)\n- [crates/server/src/main.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/server/src/main.rs)\n- [crates/server/src/routes/mod.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/server/src/routes/mod.rs)\n- [crates/server/src/routes/oauth.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/server/src/routes/oauth.rs)\n- [crates/server/src/startup.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/server/src/startup.rs)\n- [crates/server/src/runtime/mod.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/server/src/runtime/mod.rs)\n
\n\n# Backend Architecture\n\n## Overview\n\nVibe Kanban's backend is built with Rust using the Axum web framework, providing a high-performance API server that handles workspace management, authentication, and integration with coding agents. The backend follows a modular architecture with clear separation between routing, runtime management, and core server functionality.\n\nThe server component (`crates/server`) serves as the central hub for coordinating between the web frontend and various external services including GitHub integrations, coding agent executors, and development workspace environments.\n\n## Architecture Components\n\n### Core Server Structure\n\nThe backend is organized into several key modules:\n\n| Module | Purpose |\n|--------|---------|\n| `main.rs` | Application entry point and initialization |\n| `lib.rs` | Library interface and shared exports |\n| `startup.rs` | Server bootstrap and configuration |\n| `routes/` | HTTP endpoint handlers |\n| `runtime/` | Agent runtime execution management |\n\n### Module Hierarchy\n\n```mermaid\ngraph TD\n A[crates/server] --> B[main.rs]\n A --> C[lib.rs]\n A --> D[startup.rs]\n A --> E[routes/]\n A --> F[runtime/]\n E --> E1[oauth.rs]\n E --> E2[mod.rs]\n F --> F1[mod.rs]\n```\n\n## Request Flow\n\n```mermaid\ngraph LR\n A[Client Request] --> B[Axum Router]\n B --> C[Route Handlers]\n C --> D[OAuth Routes]\n C --> E[API Routes]\n C --> F[Runtime Routes]\n D --> G[OAuth Callback]\n E --> H[JSON Response]\n F --> I[Agent Execution]\n```\n\n## Routing System\n\n### Route Organization\n\nThe routing layer in `crates/server/src/routes/mod.rs` acts as a central router that aggregates all HTTP endpoints. Routes are organized by functional domain:\n\n- **OAuth Routes** (`routes/oauth.rs`) - Handle GitHub authentication and OAuth callbacks\n- **API Routes** - Handle workspace operations, task management, and agent interactions\n- **Runtime Routes** (`runtime/mod.rs`) - Manage coding agent execution contexts\n\n### OAuth Implementation\n\nThe OAuth route handler in `crates/server/src/routes/oauth.rs` demonstrates the server's response pattern for authentication flows:\n\n```rust\nResponse::builder()\n .status(StatusCode::OK)\n .header(\"content-type\", \"text/html; charset=utf-8\")\n .body(body)\n .unwrap()\n```\n\n资料来源：[crates/server/src/routes/oauth.rs:20-25]()\n\nThe OAuth callback returns an HTML response with embedded base64-encoded app icon, displaying a success message and instructions to return to the application.\n\n## Startup Sequence\n\n```mermaid\ngraph TD\n A[main.rs entry] --> B[Initialize Config]\n B --> C[Load Environment]\n C --> D[startup.rs::run]\n D --> E[Build Router]\n E --> F[Bind Socket]\n F --> G[Start Axum Server]\n G --> H[Listen for Requests]\n```\n\nThe startup module (`crates/server/src/startup.rs`) handles:\n- Configuration loading from environment variables\n- Router construction with middleware\n- Socket binding and server initialization\n\n## Runtime Management\n\n### Agent Execution Model\n\nThe runtime module (`crates/server/src/runtime/mod.rs`) manages the lifecycle of coding agent processes within workspaces. Each workspace provides an agent with:\n\n| Resource | Description |\n|----------|-------------|\n| Git Branch | Isolated branch for agent modifications |\n| Terminal | Shell access for command execution |\n| Dev Server | Preview environment for testing |\n\n资料来源：[crates/server/src/runtime/mod.rs]()\n\n### Process Tracking\n\nThe backend tracks agent processes with metadata including:\n\n- `started_at` - Process initialization timestamp\n- `completed_at` - Process termination timestamp\n- `isRunning` - Active execution state\n- `filesChanged` - Modified file count\n- `linesAdded` / `linesRemoved` - Change statistics\n\n## State Management\n\n### Workspace States\n\n```mermaid\nstateDiagram-v2\n [*] --> Draft\n Draft --> Running: Start Agent\n Running --> Completed: Agent Finishes\n Running --> Error: Execution Failure\n Completed --> Archived: User Archives\n Error --> Running: Retry\n Archived --> [*]\n Draft --> [*]: Cancel\n```\n\nWorkspaces maintain states including draft, running, completed, and archived, allowing users to manage multiple concurrent agent execution contexts.\n\n## API Response Patterns\n\nThe backend uses standard HTTP response patterns with JSON payloads:\n\n| Status Code | Usage |\n|-------------|-------|\n| 200 OK | Successful requests |\n| 400 Bad Request | Invalid input |\n| 401 Unauthorized | Authentication required |\n| 500 Internal Server Error | Server-side failures |\n\n## Frontend Integration\n\nThe web-core package (`packages/web-core/src/shared/`) interacts with the backend through:\n\n- **Dialog Components** - Modal interfaces for OAuth setup, force push, workspace selection\n- **Store Hooks** - State management via `useWorkspaceDiffStore`, `useUiPreferencesStore`\n- **API Hooks** - Data fetching through `useAzureAttachments` for file handling\n\n资料来源：[crates/server/src/lib.rs]()\n资料来源：[crates/web-core/src/shared/stores/useWorkspaceDiffStore.ts]()\n资料来源：[crates/web-core/src/shared/hooks/useAzureAttachments.ts]()\n\n## Configuration\n\nThe server reads configuration from environment variables with sensible defaults for:\n\n- Server host and port\n- Database connection strings\n- OAuth client credentials\n- Agent executor profiles\n\n## Dependencies\n\nKey Rust dependencies for the backend:\n\n| Crate | Version | Purpose |\n|-------|---------|---------|\n| axum | ^0.7 | Web framework |\n| tokio | ^1 | Async runtime |\n| serde | ^1 | Serialization |\n| tower | latest | Middleware |\n\n资料来源：[crates/server/src/main.rs]()\n资料来源：[crates/server/src/routes/mod.rs]()\n\n---\n\n\n\n## Frontend Architecture\n\n### 相关页面\n\n相关主题：[Crate Reference](#page-crate-reference), [Backend Architecture](#page-backend-architecture)\n\n
\nRelevant Source Files\n\n以下源码文件用于生成本页说明：\n\n- [packages/local-web/src/routes/_app.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/local-web/src/routes/_app.tsx)\n- [packages/remote-web/src/app/entry/App.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/remote-web/src/app/entry/App.tsx)\n- [packages/web-core/src/shared/hooks/useActions.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/hooks/useActions.ts)\n- [packages/web-core/src/shared/providers/WorkspaceProvider.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/providers/WorkspaceProvider.tsx)\n- [packages/ui/src/components/KanbanBoard.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/ui/src/components/KanbanBoard.tsx)\n- [packages/ui/src/components/CommandBar.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/ui/src/components/CommandBar.tsx)\n- [packages/ui/src/components/WorkspacesSidebar.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/ui/src/components/WorkspacesSidebar.tsx)\n- [packages/web-core/src/shared/stores/useUiPreferencesStore.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/stores/useUiPreferencesStore.ts)\n- [packages/web-core/src/pages/kanban/KanbanIssuePanelContainer.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/pages/kanban/KanbanIssuePanelContainer.tsx)\n- [packages/web-core/src/shared/dialogs/command-bar/WorkspaceSelectionDialog.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/dialogs/command-bar/WorkspaceSelectionDialog.tsx)\n
\n\n# Frontend Architecture\n\n## Overview\n\nVibe Kanban implements a modern, component-driven frontend architecture designed for complex project management workflows involving AI coding agents. The frontend is organized as a monorepo using a layered package structure that separates concerns between UI primitives, business logic, and deployment variants.\n\nThe architecture follows these core principles:\n- **Component Reusability**: Shared UI components across multiple deployment contexts\n- **State Centralization**: Global state management via Zustand stores\n- **Provider Pattern**: Context-based dependency injection for cross-cutting concerns\n- **Type Safety**: Full TypeScript coverage with strict typing\n\n## Monorepo Structure\n\nThe project uses a monorepo architecture with the following key packages:\n\n| Package | Purpose |\n|---------|---------|\n| `packages/ui` | Reusable UI component library (buttons, dialogs, command bar) |\n| `packages/web-core` | Business logic, hooks, stores, and shared features |\n| `packages/local-web` | Local deployment variant (runs entirely in browser) |\n| `packages/remote-web` | Remote deployment variant (connects to backend server) |\n| `npx-cli` | CLI wrapper for easy execution via `npx vibe-kanban` |\n\n```\nvibe-kanban/\n├── packages/\n│ ├── ui/ # Shared UI primitives\n│ │ └── src/components/\n│ │ ├── CommandBar.tsx\n│ │ ├── KanbanBoard.tsx\n│ │ └── WorkspacesSidebar.tsx\n│ ├── web-core/ # Core business logic\n│ │ └── src/\n│ │ ├── shared/\n│ │ │ ├── hooks/ # useActions, useAzureAttachments\n│ │ │ ├── providers/ # WorkspaceProvider\n│ │ │ ├── stores/ # Zustand state stores\n│ │ │ └── dialogs/ # Modal components\n│ │ └── pages/\n│ ├── local-web/ # Local app entry point\n│ └── remote-web/ # Remote/server-connected variant\n└── npx-cli/ # CLI entry point\n```\n\n## Application Entry Points\n\n### Local Web Application\n\nThe local web application serves as the standalone deployment variant that runs entirely in the browser without requiring a backend server.\n\n```tsx\n// packages/local-web/src/routes/_app.tsx\n// Main entry point for local deployment\n```\n\n### Remote Web Application\n\nThe remote web application connects to a backend server for persistent storage and multi-user collaboration features.\n\n```tsx\n// packages/remote-web/src/app/entry/App.tsx\n// Main entry point for remote deployment\n```\n\n## State Management\n\n### UI Preferences Store\n\nThe application uses Zustand for centralized state management. The `useUiPreferencesStore` handles UI-specific state including sidebar visibility, panel sizes, and layout modes.\n\n```typescript\n// packages/web-core/src/shared/stores/useUiPreferencesStore.ts\ninterface UiPreferencesState {\n // Layout state\n layoutMode: 'workspaces' | 'kanban';\n isLeftSidebarVisible: boolean;\n isRightSidebarVisible: boolean;\n isTerminalVisible: boolean;\n \n // Panel states per workspace\n workspacePanelStates: Record;\n \n // Pane configurations\n paneSizes: Record;\n collapsedPaths: Record;\n}\n```\n\nKey state transitions supported by the store:\n\n| Action | Description |\n|--------|-------------|\n| `toggleLayoutMode()` | Switch between workspaces and kanban views |\n| `toggleLeftSidebar()` | Show/hide left sidebar |\n| `toggleTerminal()` | Show/hide terminal panel |\n| `toggleWorkspacePanel(workspaceId, panel)` | Toggle specific workspace panel |\n\n资料来源：[packages/web-core/src/shared/stores/useUiPreferencesStore.ts:1-50](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/stores/useUiPreferencesStore.ts)\n\n### Workspace Provider\n\nThe `WorkspaceProvider` is a React context provider that manages workspace-scoped state and operations.\n\n```tsx\n// packages/web-core/src/shared/providers/WorkspaceProvider.tsx\n// Provides workspace context to child components\n```\n\n## Core UI Components\n\n### KanbanBoard\n\nThe `KanbanBoard` component is the central UI element for task visualization and management. It renders the drag-and-drop interface for issues across different status columns.\n\n```tsx\n// packages/ui/src/components/KanbanBoard.tsx\n```\n\nThe board supports multiple item types rendered through consistent interface patterns:\n\n| Item Type | Identifier | Search Label Pattern |\n|-----------|------------|---------------------|\n| Page | `pageId` | `{pageId} {label}` |\n| Repository | `repo.id` | `{repo.id} {repo.display_name}` |\n| Branch | `branch.name` | `branch.name` |\n| Status | `status.id` | `{status.id} {status.name}` |\n| Priority | `priority.id` | `{priority.id ?? 'none'} {priority.name}` |\n| Issue | `issue.id` | `{issue.id} {issue.simple_id} {issue.title}` |\n\n资料来源：[packages/ui/src/components/CommandBar.tsx:1-50](https://github.com/BloopAI/vibe-kanban/blob/main/packages/ui/src/components/CommandBar.tsx)\n\n### CommandBar\n\nThe `CommandBar` component provides a keyboard-driven interface for navigation and actions. It groups items by category and supports fuzzy search through labels.\n\n```tsx\n// packages/ui/src/components/CommandBar.tsx\n```\n\n### WorkspacesSidebar\n\nThe `WorkspacesSidebar` displays workspace summaries with multiple layout modes:\n\n- **List Layout**: Flat vertical list with sections for active, archived, and needs-attention workspaces\n- **Accordion Layout**: Collapsible sections with header persistence\n\n```tsx\n// packages/ui/src/components/WorkspacesSidebar.tsx\n```\n\nWorkspace summaries display:\n- Workspace name and active state\n- Running status and pending approvals\n- Dev server status\n- PR status\n- Activity indicators (unseen activity flag)\n- Git statistics (files changed, lines added/removed)\n\n资料来源：[packages/ui/src/components/WorkspacesSidebar.tsx:1-80](https://github.com/BloopAI/vibe-kanban/blob/main/packages/ui/src/components/WorkspacesSidebar.tsx)\n\n## Dialog System\n\n### Dialog Architecture\n\nThe application uses a modal dialog system for complex interactions. Dialogs are defined using the `defineModal` higher-order function pattern.\n\n```tsx\n// Example dialog pattern\nexport const ForcePushDialog = defineModal(\n ForcePushDialogImpl\n);\n```\n\n### Dialog Types\n\n| Dialog | Purpose | Key Features |\n|--------|---------|--------------|\n| `ForcePushDialog` | Confirm destructive force-push operations | Loading state, destructive variant |\n| `ResolveConflictsDialog` | Handle git merge conflicts | Agent/profile selector, file list |\n| `WorkspaceSelectionDialog` | Link issues to workspaces | Workspace search, archive filtering |\n| `ReleaseNotesDialog` | Display changelog information | GitHub integration, markdown rendering |\n| `GhCliSetupDialog` | GitHub CLI authentication setup | Step-by-step instructions, error help |\n\n### ResolveConflictsDialog\n\nHandles git merge conflicts by displaying conflicted files and providing agent selection for resolution.\n\n```tsx\n// packages/web-core/src/shared/dialogs/tasks/ResolveConflictsDialog.tsx\n\n{conflictedFiles.slice(0, 5).map((file) => (\n
  • {file}
    • \n))}\n{conflictedFiles.length > 5 && (\n
  • And {conflictedFiles.length - 5} more...
    • \n)}\n```\n\nThe dialog includes:\n- Conflicted file list with truncation for large conflicts\n- Agent selector for AI-powered resolution\n- Config selector for resolution parameters\n- New session toggle for existing workspace sessions\n\n资料来源：[packages/web-core/src/shared/dialogs/tasks/ResolveConflictsDialog.tsx:80-100](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/dialogs/tasks/ResolveConflictsDialog.tsx)\n\n## Kanban Issue Panel\n\nThe `KanbanIssuePanelContainer` renders detailed issue views with multiple collapsible sections:\n\n```tsx\n// packages/web-core/src/pages/kanban/KanbanIssuePanelContainer.tsx\n\n }\n renderRelationshipsSection={(issueId) => }\n renderSubIssuesSection={(issueId) => }\n renderCommentsSection={(issueId) => }\n/>\n```\n\n### Issue Panel Sections\n\n| Section | Container Component | Purpose |\n|---------|---------------------|---------|\n| Workspaces | `IssueWorkspacesSectionContainer` | Associated workspace links |\n| Relationships | `IssueRelationshipsSectionContainer` | Linked issues and parent-child relations |\n| Sub-Issues | `IssueSubIssuesSectionContainer` | Child issues breakdown |\n| Comments | `IssueCommentsSectionContainer` | Discussion and review comments |\n\n## Hooks System\n\n### useActions Hook\n\nCustom hooks encapsulate business logic and provide clean interfaces for components.\n\n```tsx\n// packages/web-core/src/shared/hooks/useActions.ts\n// Centralizes action dispatching and state updates\n```\n\n### useAzureAttachments Hook\n\nHandles file upload workflows with progress tracking:\n\n```typescript\n// packages/web-core/src/shared/hooks/useAzureAttachments.ts\n\n// Progress tracking for uploads\nsetPendingAttachments((prev) =>\n prev.map((p) =>\n p.file === file ? { ...p, status: 'confirming', progress: 100 } : p\n ))\n);\n```\n\nThe hook manages:\n- Pending attachment states\n- Upload progress tracking\n- Confirmation workflows\n- Completed attachment tracking\n\n## Component Interaction Flow\n\n```mermaid\ngraph TD\n A[App Entry Point] --> B[WorkspaceProvider]\n A --> C[UiPreferencesStore]\n B --> D[KanbanBoard]\n B --> E[WorkspacesSidebar]\n D --> F[KanbanIssuePanelContainer]\n F --> G[Dialog System]\n E --> H[CommandBar]\n G --> I[ForcePushDialog]\n G --> J[ResolveConflictsDialog]\n G --> K[WorkspaceSelectionDialog]\n \n C --> L[Layout Toggle]\n C --> M[Sidebar Visibility]\n C --> N[Terminal Toggle]\n \n style A fill:#e1f5fe\n style B fill:#fff3e0\n style C fill:#e8f5e9\n```\n\n## Home Page Structure\n\nThe remote web application provides a structured home page with organization and project navigation:\n\n```tsx\n// packages/remote-web/src/pages/HomePage.tsx\n\nfunction OrganizationSection({ organization, projects, hostId, onRequireHost }) {\n return (\n
    \n
    \n

    {organization.name}

    \n

    {projects.length} {projects.length === 1 ? \"project\" : \"projects\"}

    \n
    \n
      \n {projects.map((project) => )}\n
    \n
    \n );\n}\n```\n\n## Deployment Variants\n\nThe application supports two deployment modes:\n\n```mermaid\ngraph LR\n subgraph Local[\"Local Deployment\"]\n L1[local-web package]\n L2[Browser-only execution]\n L3[No server required]\n end\n \n subgraph Remote[\"Remote Deployment\"]\n R1[remote-web package]\n R2[Backend server connection]\n R3[Multi-user support]\n end\n \n style Local fill:#bbdefb\n style Remote fill:#c8e6c9\n```\n\n### Local Web\n\n- Runs entirely in the browser\n- No backend server required\n- Single-user mode\n- Data stored in browser storage\n\n### Remote Web\n\n- Requires backend server (`crates/server`)\n- Multi-user support via OAuth authentication\n- Persistent storage in database\n- Real-time collaboration features\n\n## Technology Stack\n\n| Layer | Technology | Purpose |\n|-------|------------|---------|\n| Framework | React 18+ | UI rendering |\n| Language | TypeScript | Type safety |\n| State | Zustand | Lightweight state management |\n| Styling | Tailwind CSS | Utility-first styling |\n| Build | Vite + esbuild | Fast builds |\n| Routing | React Router | SPA navigation |\n| i18n | react-i18next | Internationalization |\n| Icons | Lucide React | Icon library |\n\n## Key Architectural Patterns\n\n### 1. Provider Pattern\n\nCross-cutting concerns are injected via React context providers:\n\n```tsx\n// Workspace context available throughout the component tree\n\n \n \n\n```\n\n### 2. Store Pattern\n\nZustand stores provide centralized, typed state with simple update functions:\n\n```typescript\n// Simple store usage\nconst { layoutMode, toggleLayoutMode } = useUiPreferencesStore();\n```\n\n### 3. Modal Definition Pattern\n\nDialogs use a higher-order function for consistent modal lifecycle management:\n\n```tsx\nexport const SomeDialog = defineModal(Component);\n```\n\n### 4. Lazy Loading\n\nComponents support dynamic imports for code splitting:\n\n```tsx\n// Dialogs loaded on demand to reduce initial bundle size\nconst SomeDialog = lazy(() => import('./dialogs/SomeDialog'));\n\n---\n\n\n\n## Crate Reference\n\n### 相关页面\n\n相关主题：[Backend Architecture](#page-backend-architecture), [Coding Agent Executors](#page-executors), [Relay and Remote Access](#page-relay-remote-access)\n\n
    \n相关源码文件\n\n以下源码文件用于生成本页说明：\n\n- [crates/server/src/routes/oauth.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/server/src/routes/oauth.rs)\n- [README.md](https://github.com/BloopAI/vibe-kanban/blob/main/README.md)\n
    \n\n# Crate Reference\n\n## Overview\n\nVibe Kanban is a monorepo with a multi-package architecture that combines Rust-based backend services (crates) with TypeScript/React frontend packages. The backend crates provide core infrastructure for workspace management, code execution, database operations, and secure communication.\n\nThe project structure includes:\n\n- **Frontend packages** (`packages/`): React-based UI including `web-core`, `ui`, and `remote-web`\n- **Rust crates** (`crates/`): Backend services for server operations, API types, database, executors, MCP protocol, relay tunneling, workspace management, and worktree management\n\n## Crate Architecture\n\nThe Rust backend consists of several specialized crates that work together to provide the core functionality of Vibe Kanban:\n\n| Crate | Purpose |\n|-------|---------|\n| `server` | Main HTTP server with route handlers |\n| `api-types` | Shared type definitions for API communication |\n| `db` | Database operations and models |\n| `executors` | Code execution engine for coding agents |\n| `relay-tunnel` | Secure relay communication |\n| `mcp` | Model Context Protocol integration |\n| `workspace-manager` | Workspace lifecycle management |\n| `worktree-manager` | Git worktree operations |\n\n## Server Crate\n\nThe `server` crate (`crates/server/src/`) is the main entry point for the backend application. It handles HTTP routing and serves both the API endpoints and static assets.\n\n### OAuth Routes\n\nThe server provides OAuth authentication flow endpoints for GitHub integration:\n\n**File:** `crates/server/src/routes/oauth.rs`\n\nThe OAuth handler returns an HTML page confirming successful authentication:\n\n```rust\nResponse::builder()\n .status(StatusCode::OK)\n .header(\"content-type\", \"text/html; charset=utf-8\")\n .body(body)\n .unwrap()\n```\n\nThe response includes:\n- Application logo embedded as base64 PNG\n- Success message display\n- User instruction to close the tab and return to the app\n\n## Project Organization\n\n### Monorepo Structure\n\n```\nvibe-kanban/\n├── packages/\n│ ├── web-core/ # Core web UI components\n│ ├── ui/ # Shared UI components\n│ └── remote-web/ # Remote access web interface\n├── crates/\n│ ├── server/ # HTTP server\n│ ├── api-types/ # API type definitions\n│ ├── db/ # Database layer\n│ ├── executors/ # Agent execution engine\n│ ├── relay-tunnel/ # Relay communication\n│ ├── mcp/ # MCP protocol\n│ ├── workspace-manager/ # Workspace operations\n│ └── worktree-manager/ # Git worktree management\n└── public/ # Static assets\n```\n\n## Data Flow Architecture\n\n```mermaid\ngraph TD\n subgraph Frontend[\"Frontend (TypeScript/React)\"]\n UI[UI Components]\n WC[Web Core]\n end\n \n subgraph Backend[\"Backend (Rust Crates)\"]\n Server[Server Crate]\n DB[(Database)]\n API[API Types]\n end\n \n subgraph Execution[\"Execution Layer\"]\n Exec[Executors]\n WM[Workspace Manager]\n WTM[Worktree Manager]\n MCP[MCP Protocol]\n RT[Relay Tunnel]\n end\n \n UI --> WC\n WC --> Server\n Server --> DB\n Server --> API\n Exec --> WM\n WM --> WTM\n Exec --> MCP\n Exec --> RT\n```\n\n## Key Modules\n\n### API Types\n\nThe `api-types` crate provides shared type definitions used across the frontend and backend for type-safe API communication.\n\n### Database Layer\n\nThe `db` crate handles persistent storage operations, including:\n- Workspace state persistence\n- User preferences\n- Project and organization data\n\n### Workspace Manager\n\nManages the lifecycle of workspaces, including creation, archival, and state tracking.\n\n### Worktree Manager\n\nHandles Git worktree operations, providing isolated branch environments for each workspace.\n\n### Executors\n\nThe execution engine that runs coding agents (Claude Code, Codex, Gemini CLI, etc.) within workspace environments.\n\n### Relay Tunnel\n\nProvides secure communication channels for remote access scenarios.\n\n### MCP Integration\n\nImplements the Model Context Protocol for enhanced agent capabilities.\n\n## Configuration and Preferences\n\nThe frontend manages user preferences through the `useUiPreferencesStore`, which handles:\n\n| Setting | Description |\n|---------|-------------|\n| `layoutMode` | Toggle between 'workspaces' and 'kanban' views |\n| `isLeftSidebarVisible` | Left sidebar visibility |\n| `isTerminalVisible` | Terminal panel visibility |\n| `paneSizes` | Customizable panel dimensions |\n| `collapsedPaths` | File tree collapsed state per workspace |\n| `fileSearchRepoId` | Active repository for file search |\n\n资料来源：[packages/web-core/src/shared/stores/useUiPreferencesStore.ts]()\n\n## Development Workflow\n\nThe system supports the following developer keyboard shortcuts:\n\n| Shortcut | Action |\n|----------|--------|\n| `v>p` | Toggle preview mode |\n| `v>s` | Toggle left sidebar |\n| `v>h` | Toggle left main panel |\n| `x>p` | Create Git PR |\n| `x>m` | Merge PR |\n| `x>r` | Git rebase |\n| `x>u` | Git push |\n| `t>d` | Toggle dev server |\n| `t>w` | Toggle wrap lines |\n\n资料来源：[packages/web-core/src/shared/keyboard/useWorkspaceShortcuts.ts]()\n\n## Summary\n\nThe Vibe Kanban architecture combines TypeScript/React frontend packages with Rust backend crates to provide a comprehensive coding agent workspace management system. The Rust crates handle core infrastructure including database operations, workspace lifecycle, Git worktree management, code execution, and secure communication, while the frontend provides the user interface for planning, reviewing, and managing coding agent activities.\n\nFor the latest updates and project status, refer to the official announcement at [vibekanban.com/blog/shutdown](https://vibekanban.com/blog/shutdown).\n\n---\n\n\n\n## Coding Agent Executors\n\n### 相关页面\n\n相关主题：[Crate Reference](#page-crate-reference), [MCP Server Integration](#page-mcp-integration)\n\n
    \n相关源码文件\n\n以下源码文件用于生成本页说明：\n\n- [README.md](https://github.com/BloopAI/vibe-kanban/blob/main/README.md)\n- [packages/web-core/src/features/workspace-chat/ui/SessionChatBoxContainer.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/features/workspace-chat/ui/SessionChatBoxContainer.tsx)\n- [packages/web-core/src/features/workspace-chat/ui/ConversationListContainer.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/features/workspace-chat/ui/ConversationListContainer.tsx)\n- [packages/web-core/src/shared/keyboard/useWorkspaceShortcuts.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/keyboard/useWorkspaceShortcuts.ts)\n- [packages/web-core/src/shared/dialogs/command-bar/WorkspaceSelectionDialog.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/dialogs/command-bar/WorkspaceSelectionDialog.tsx)\n- [packages/web-core/src/shared/components/tasks/TaskDetails/ProcessesTab.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/components/tasks/TaskDetails/ProcessesTab.tsx)\n
    \n\n# Coding Agent Executors\n\n## Overview\n\nCoding Agent Executors in Vibe Kanban are the runtime engines that enable AI coding agents to execute tasks within isolated workspace environments. Each workspace provides an agent with a dedicated branch, terminal, and dev server, allowing software engineers to plan work through kanban issues while agents perform the actual coding tasks.\n\nThe executor system supports multiple AI coding agents, enabling teams to choose the most appropriate agent for their specific needs or switch between agents based on task requirements.\n\n资料来源：[README.md:1-20]()\n\n## Supported Agents\n\nVibe Kanban supports the following coding agents:\n\n| Agent | Description |\n|-------|-------------|\n| Claude Code | Anthropic's CLI tool for Claude models |\n| Codex | OpenAI's coding agent |\n| Gemini CLI | Google's Gemini-based CLI agent |\n| GitHub Copilot | Microsoft's AI pair programmer |\n| Amp | Alternative coding agent |\n| Cursor | Cursor IDE's AI agent |\n| OpenCode | Open-source coding agent |\n| Droid | Mobile-optimized coding agent |\n| CCR | Custom coding agent configuration |\n| Qwen Code | Alibaba's Qwen-based coding agent |\n\n资料来源：[README.md:25]()\n\n## Architecture\n\n### Executor Components\n\nThe executor system consists of several key components:\n\n1. **Session Chat Box** - The primary interface for interacting with coding agents during task execution\n2. **Conversation List** - Displays the ongoing conversation and output between the agent and user\n3. **Process Management** - Handles the lifecycle of agent processes including start, execution, and completion\n4. **Workspace Integration** - Provides isolated environments with git branches, terminals, and dev servers\n\n```mermaid\ngraph TD\n A[Kanban Issue] --> B[Workspace Creation]\n B --> C[Session Chat Box]\n C --> D[Agent Executor]\n D --> E[Conversation List]\n D --> F[Process Execution]\n F --> G[Branch & Terminal]\n F --> H[Dev Server]\n E --> I[Diff Review]\n I --> J[Inline Comments]\n J --> K[Pull Request]\n```\n\n资料来源：[packages/web-core/src/features/workspace-chat/ui/SessionChatBoxContainer.tsx:1-50]()\n\n## Session Chat Box\n\nThe `SessionChatBox` component is the central hub for agent interaction. It manages the chat interface, editor input, and session state.\n\n### Key Properties\n\n| Property | Type | Purpose |\n|----------|------|---------|\n| `status` | `idle` \\| `running` \\| `completed` | Current execution state |\n| `repoIds` | `string[]` | Associated repository identifiers |\n| `tokenUsageInfo` | `TokenUsageInfo` | Usage tracking for billing |\n| `formatExecutorLabel` | `Function` | Formats agent display names |\n| `formatSessionDate` | `Function` | Formats session timestamps |\n| `renderAgentIcon` | `Function` | Renders agent-specific icons |\n\n### Session State Management\n\n```typescript\nsession={{\n sessions: [],\n selectedSessionId: undefined,\n onSelectSession: () => {},\n isNewSessionMode: false,\n onNewSession: undefined,\n}}\n```\n\nThe session object tracks the active conversation context, allowing users to switch between multiple agent sessions within a workspace.\n\n资料来源：[packages/web-core/src/features/workspace-chat/ui/SessionChatBoxContainer.tsx:60-100]()\n\n## Conversation Display\n\nThe `ConversationList` component renders the ongoing interaction with the coding agent.\n\n### Entry Types\n\n| Entry Type | Rendering Component |\n|------------|---------------------|\n| `STDOUT` | Standard output paragraphs |\n| `STDERR` | Error output paragraphs |\n| `NORMALIZED_ENTRY` | Full display with expansion support |\n| `THINKING` | Aggregated thinking blocks |\n\n```mermaid\ngraph LR\n A[Agent Output] --> B{Entry Type?}\n B -->|STDOUT| C[Paragraph Display]\n B -->|STDERR| D[Error Display]\n B -->|NORMALIZED| E[DisplayConversationEntry]\n B -->|THINKING| F[Aggregated Thinking]\n```\n\n资料来源：[packages/web-core/src/features/workspace-chat/ui/ConversationListContainer.tsx:40-70]()\n\n## Process Execution\n\nThe `ProcessesTab` component provides visibility into running and completed agent processes.\n\n### Process Information Displayed\n\n- **Process Status** - Current state (running, completed, failed)\n- **Started At** - Process initiation timestamp\n- **Completed At** - Process completion timestamp (when applicable)\n- **Log Output** - Real-time and archived process logs\n\n### Log Management\n\nThe ProcessesTab includes functionality to copy logs to clipboard for debugging and audit purposes:\n\n```typescript\nconst handleCopyLogs = () => {\n // Copies all accumulated logs to clipboard\n // Updates UI to show \"Logs copied\" confirmation\n};\n```\n\n资料来源：[packages/web-core/src/shared/components/tasks/TaskDetails/ProcessesTab.tsx:1-80]()\n\n## Workspace Shortcuts\n\nAgent-related operations can be triggered via keyboard shortcuts defined in `useWorkspaceShortcuts`:\n\n| Shortcut | Action |\n|----------|--------|\n| `v>d` | Toggle DevTools |\n| `v>p` | Toggle Preview Mode |\n| `v>s` | Toggle Left Sidebar |\n| `v>h` | Toggle Left Main Panel |\n| `x>p` | Git Create PR |\n| `x>m` | Git Merge |\n| `x>r` | Git Rebase |\n| `x>u` | Git Push |\n| `r>s` | Run Setup Script |\n| `r>c` | Run Cleanup Script |\n\n资料来源：[packages/web-core/src/shared/keyboard/useWorkspaceShortcuts.ts:1-30]()\n\n## Workspace Selection\n\nWhen linking an issue to a workspace, users can select from available workspaces or create new ones:\n\n```typescript\ninterface Workspace {\n id: string;\n name: string;\n branch: string;\n isArchived: boolean;\n filesChanged: number;\n linesAdded: number;\n linesRemoved: number;\n isRunning: boolean;\n isPinned: boolean;\n hasPendingApproval: boolean;\n hasRunningDevServer: boolean;\n hasUnseenActivity: boolean;\n latestProcessCompletedAt: Date | null;\n latestProcessStatus: string | null;\n prStatus: string | null;\n}\n```\n\n资料来源：[packages/web-core/src/shared/dialogs/command-bar/WorkspaceSelectionDialog.tsx:50-90]()\n\n## Executor Profile Configuration\n\nEach executor can be configured with specific profiles that define:\n\n- **Model Selection** - Which AI model to use (e.g., Claude 3.5 Sonnet, GPT-4)\n- **System Prompt** - Custom instructions for the agent\n- **Temperature** - Response randomness setting\n- **Max Tokens** - Response length limits\n\nProfiles are stored in `default_profiles.json` and can be selected per-workspace or globally.\n\n## Workflow Summary\n\n```mermaid\ngraph TD\n A[Create Kanban Issue] --> B[Open/Create Workspace]\n B --> C[Select Agent & Profile]\n C --> D[Start Agent Session]\n D --> E[Agent Reads Issue Context]\n E --> F[Agent Executes Tasks]\n F --> G[Changes Applied to Branch]\n G --> H[Review Diff in UI]\n H --> I{Changes Approved?}\n I -->|Yes| J[Create Pull Request]\n I -->|No| K[Send Feedback to Agent]\n K --> F\n J --> L[Merge PR]\n```\n\n## Related Components\n\n| Component | File Path | Role |\n|-----------|-----------|------|\n| `SessionChatBoxContainer` | `packages/web-core/src/features/workspace-chat/ui/` | Main agent interaction UI |\n| `ConversationListContainer` | `packages/web-core/src/features/workspace-chat/ui/` | Conversation message display |\n| `ProcessesTab` | `packages/web-core/src/shared/components/tasks/TaskDetails/` | Process monitoring |\n| `WorkspaceSelectionDialog` | `packages/web-core/src/shared/dialogs/command-bar/` | Workspace linking |\n| `useWorkspaceShortcuts` | `packages/web-core/src/shared/keyboard/` | Keyboard navigation |\n\n---\n\n\n\n## MCP Server Integration\n\n### 相关页面\n\n相关主题：[Coding Agent Executors](#page-executors), [Database and Data Models](#page-database-models)\n\nThe requested MCP-related source files were not included in the provided context. The `
    ` block references these files:\n\n- `crates/mcp/src/lib.rs`\n- `crates/mcp/src/task_server/mod.rs`\n- `crates/mcp/src/task_server/handler.rs`\n- `crates/mcp/src/task_server/tools/mod.rs`\n- `crates/executors/src/mcp_config.rs`\n- `crates/executors/default_mcp.json`\n\nHowever, **none of these files appear in the retrieved context**. The context only contains files from `packages/web-core`, `packages/ui`, `packages/remote-web`, and `crates/server`.\n\n**What I can see from the available context:**\n\nThe repository is a **TypeScript/JavaScript monorepo** with these visible packages:\n\n| Package | Path | Purpose |\n|---------|------|---------|\n| `web-core` | `packages/web-core/src/` | Core UI components, dialogs, stores, hooks |\n| `ui` | `packages/ui/src/` | Shared UI components (CommandBar, WorkspacesSidebar) |\n| `remote-web` | `packages/remote-web/src/` | HomePage, organization/project views |\n| `server` | `crates/server/src/` | Rust backend with OAuth routes |\n\nThe visible files show a **Kanban workspace management system** with:\n- Git integration dialogs (ForcePushDialog, ResolveConflictsDialog)\n- Command bar interface\n- Organization and project management\n- Process list handling\n- Workspace diff/comment tracking\n- Keyboard shortcuts for workspace operations\n\n**To generate the MCP Server Integration wiki page**, please provide the actual MCP-related source files from the `crates/mcp/` directory.\n\n---\n\n\n\n## Relay and Remote Access\n\n### 相关页面\n\n相关主题：[Crate Reference](#page-crate-reference), [Deployment and Infrastructure](#page-deployment-infrastructure)\n\n
    \n相关源码文件\n\n以下源码文件用于生成本页说明：\n\n- [crates/server/src/middleware/origin.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/server/src/middleware/origin.rs)\n- [packages/remote-web/src/app/layout/RemoteAppShell.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/remote-web/src/app/layout/RemoteAppShell.tsx)\n- [packages/web-core/src/shared/stores/useUiPreferencesStore.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/stores/useUiPreferencesStore.ts)\n- [packages/web-core/src/shared/hooks/useAzureAttachments.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/hooks/useAzureAttachments.ts)\n- [crates/server/src/error.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/server/src/error.rs)\n
    \n\n# Relay and Remote Access\n\n## Overview\n\nThe Relay and Remote Access system in Vibe Kanban enables secure, low-latency communication between local development environments and remote hosts. This system allows users to access their coding workspaces and development servers from anywhere while maintaining proper authentication and origin verification.\n\nThe relay architecture consists of multiple layers:\n\n- **Relay Tunnel** - Handles encrypted tunneled connections\n- **Relay WebRTC** - Provides peer-to-peer communication channels\n- **Relay Hosts** - Manages the registry and lifecycle of remote hosts\n- **Relay Protocol** - Defines the communication protocol between clients and hosts\n- **Relay Client** - Implements the client-side connection logic\n\n## Architecture\n\n### System Components\n\n| Component | Purpose | Location |\n|-----------|---------|----------|\n| Relay Tunnel | Encrypted tunnel establishment | `crates/relay-tunnel/src/lib.rs` |\n| Relay WebRTC | Peer-to-peer communication | `crates/relay-webrtc/src/lib.rs` |\n| Relay Hosts | Host registry and management | `crates/relay-hosts/src/lib.rs` |\n| Relay Protocol | Communication protocol definition | `crates/relay-protocol/src/lib.rs` |\n| Relay Client | Client-side connection logic | `crates/relay-client/src/lib.rs` |\n| Origin Middleware | Request origin verification | `crates/server/src/middleware/origin.rs` |\n\n### Connection Flow\n\n```mermaid\ngraph TD\n A[Client Browser] -->|HTTPS + Relay Header| B[Server Middleware]\n B -->|Verify Origin| C{Origin Valid?}\n C -->|Yes| D[Relay Host Lookup]\n C -->|No| E[403 Forbidden Response]\n D -->|Host Online| F[Establish WebSocket]\n D -->|Host Unpaired| G[Pairing Flow]\n F -->|Tunnel Established| H[Remote Workspace Access]\n G -->|Paired Successfully| F\n```\n\n## Origin Verification Middleware\n\nThe server implements an `origin.rs` middleware that validates all incoming requests to ensure they originate from legitimate sources.\n\n### Key Components\n\n**RELAY_HEADER Constant**\nThe relay header (`x-vibe-relay`) identifies requests coming through the relay system. When present with value `\"1\"`, the request is flagged as a relay request.\n\n资料来源：[crates/server/src/middleware/origin.rs:1-5]()\n\n**Header Retrieval Functions**\n\n| Function | Purpose |\n|----------|---------|\n| `get_host_header` | Extracts the `Host` header from a request |\n| `get_header` | Retrieves any specified header by name |\n| `is_relay_request` | Checks if request contains relay header |\n\n```rust\nfn is_relay_request(req: &Request) -> bool {\n req.headers()\n .get(RELAY_HEADER)\n .and_then(|v| v.to_str().ok())\n .is_some_and(|v| v.trim() == \"1\")\n}\n```\n\n资料来源：[crates/server/src/middleware/origin.rs:15-21]()\n\n**Host Normalization**\nThe `normalize_host` function standardizes host strings for consistent comparison:\n\n1. Trims whitespace and IPv6 brackets\n2. Converts to lowercase\n3. Converts `localhost` aliases to `\"localhost\"`\n4. Converts loopback IPs to `\"localhost\"`\n5. Returns normalized IP or hostname\n\n```rust\nfn normalize_host(host: &str) -> String {\n let trimmed = host.trim().trim_start_matches('[').trim_end_matches(']');\n let lower = trimmed.to_ascii_lowercase();\n if lower == \"localhost\" {\n return \"localhost\".to_string();\n }\n if let Ok(ip) = lower.parse::() {\n if ip.is_loopback() {\n return \"localhost\".to_string();\n }\n return ip.to_string();\n }\n lower\n}\n```\n\n资料来源：[crates/server/src/middleware/origin.rs:31-45]()\n\n**Origin Matching**\nThe `origin_matches_host` function validates that the request origin corresponds to the host header:\n\n```rust\nfn origin_matches_host(origin: &str, host: &str) -> bool {\n origin\n .strip_prefix(\"http://\")\n .or_else(|| origin.strip_prefix(\"https://\"))\n .is_some_and(|rest| rest.eq_ignore_ascii_case(host))\n}\n```\n\n资料来源：[crates/server/src/middleware/origin.rs:26-29]()\n\n### Forbidden Response\n\nWhen origin verification fails, the middleware returns a `403 Forbidden` response:\n\n```rust\nfn forbidden() -> Response {\n Response::builder()\n .status(StatusCode::FORBIDDEN)\n .body(Body::empty())\n .unwrap_or_else(|_| Response::new(Body::empty()))\n}\n```\n\n资料来源：[crates/server/src/middleware/origin.rs:23-25]()\n\n## Remote Host Management\n\n### Host Status Types\n\n| Status | Description | UI Behavior |\n|--------|-------------|-------------|\n| `online` | Host is connected and ready | Clickable, allows connection |\n| `unpaired` | Host exists but not authenticated | Clickable, triggers pairing |\n| Other | Host is offline or unavailable | Disabled, grayed out |\n\nThe UI displays host status with visual indicators:\n\n```tsx\nconst isOnline = host.status === \"online\";\nconst isUnpaired = host.status === \"unpaired\";\nconst isClickable = isOnline || isUnpaired;\n```\n\n资料来源：[packages/remote-web/src/app/layout/RemoteAppShell.tsx:1-50]()\n\n### Host Display\n\nHosts are rendered with status indicators using color coding:\n\n```tsx\n {\n handleHostClick(host.id, host.status);\n setIsDrawerOpen(false);\n}}\n```\n\n资料来源：[packages/remote-web/src/app/layout/RemoteAppShell.tsx:38-41]()\n\n## Relay Pairing System\n\n### Pairing Errors\n\nThe error handling system maps various pairing errors to appropriate HTTP responses:\n\n| Error Type | HTTP Status | Condition |\n|------------|-------------|-----------|\n| Authentication Failed | `401 Unauthorized` | Invalid credentials |\n| Pairing Failed | `400 Bad Request` | General pairing issue |\n| Serialization Error | `502 Bad Gateway` | Store serialization failure |\n| Storage Error | `502 Bad Gateway` | Persistence failure |\n\n```rust\nRelayPairingClientError::RemoteClient(ref inner) => {\n tracing::warn!(%inner, \"Relay host pairing authentication failed\");\n ApiError::Unauthorized\n}\nRelayPairingClientError::Pairing(ref detail) => {\n tracing::warn!(%detail, \"Relay host pairing failed\");\n ApiError::BadRequest(err.to_string())\n}\n```\n\n资料来源：[crates/server/src/error.rs:1-30]()\n\n### Unconfigured Relay\n\nWhen the relay API is not configured, the system returns:\n\n```rust\nfrom(_: RelayHostsNotConfigured) -> Self {\n ApiError::BadRequest(\"Remote relay API is not configured\".to_string())\n}\n```\n\n资料来源：[crates/server/src/error.rs:45-48]()\n\n## Attachment Upload via Relay\n\nThe relay system also handles file attachments when working remotely. The upload process involves:\n\n1. Initialize upload with Azure blob storage\n2. Upload chunks with progress tracking\n3. Confirm upload completion\n\n```typescript\nconst result = await confirmAttachmentUpload({\n project_id: projectId,\n upload_id: initResult.upload_id,\n filename: file.name,\n content_type: file.type,\n size_bytes: file.size,\n hash,\n issue_id: issueIdRef.current,\n comment_id: commentIdRef.current,\n});\n```\n\n资料来源：[packages/web-core/src/shared/hooks/useAzureAttachments.ts:1-50]()\n\n## Workspace Panel States\n\nThe relay system integrates with the workspace panel state management:\n\n```typescript\ntoggleLeftMainPanel: (workspaceId) => {\n if (!workspaceId) return;\n const state = get();\n const wsState = state.workspacePanelStates[workspaceId] ?? DEFAULT_WORKSPACE_PANEL_STATE;\n if (wsState.isLeftMainPanelVisible && wsState.rightMainPanelMode === null)\n return;\n set({\n workspacePanelStates: {\n ...state.workspacePanelStates,\n [workspaceId]: {\n ...wsState,\n isLeftMainPanelVisible: !wsState.isLeftMainPanelVisible,\n },\n },\n });\n},\n```\n\n资料来源：[packages/web-core/src/shared/stores/useUiPreferencesStore.ts:1-40]()\n\n## Security Considerations\n\n### CORS and Origin Validation\n\nAll relay requests undergo strict origin validation:\n\n1. Requests must include a valid `Origin` header\n2. The origin must match the `Host` header (with protocol prefix stripped)\n3. Relay requests are identified via the `x-vibe-relay` header\n4. Loopback addresses and `localhost` are normalized for consistent comparison\n\n### Authentication Flow\n\n```mermaid\nsequenceDiagram\n participant C as Client\n participant S as Server\n participant R as Relay Host\n \n C->>S: Request with x-vibe-relay: 1\n S->>S: Validate Origin matches Host\n alt Valid Request\n S->>R: Relay connection\n R-->>C: Authenticated tunnel\n else Invalid Origin\n S-->>C: 403 Forbidden\n end\n```\n\n## Configuration\n\n### Environment Variables\n\n| Variable | Purpose |\n|----------|---------|\n| `RELAY_API_URL` | Base URL for relay API |\n| `RELAY_API_KEY` | Authentication key for relay |\n| `ALLOWED_ORIGINS` | Comma-separated list of allowed origins |\n\n### Default Port Resolution\n\nThe system includes logic for determining default ports based on HTTPS configuration:\n\n```rust\nfn default_port(https: bool)\n```\n\n资料来源：[crates/server/src/middleware/origin.rs:50]()\n\n## Troubleshooting\n\n### Common Issues\n\n| Issue | Cause | Resolution |\n|-------|-------|------------|\n| 403 Forbidden on relay requests | Origin mismatch | Check `Origin` and `Host` headers |\n| Host shows as \"offline\" | Network connectivity | Verify host is running and connected |\n| Pairing fails | Authentication error | Re-authenticate the relay host |\n| Slow connection | High latency | Check network conditions, consider WebRTC fallback |\n\n### Diagnostic Steps\n\n1. Verify the `x-vibe-relay` header is present in requests\n2. Check server logs for relay-related warnings and errors\n3. Confirm host status in the Remote App Shell UI\n4. Validate origin normalization with `normalize_host()` function\n\n---\n\n\n\n## Database and Data Models\n\n### 相关页面\n\n相关主题：[Backend Architecture](#page-backend-architecture), [Key Concepts](#page-key-concepts)\n\n
    \n相关源码文件\n\n以下源码文件用于生成本页说明：\n\n- [crates/db/src/lib.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/db/src/lib.rs)\n- [crates/db/src/models/mod.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/db/src/models/mod.rs)\n- [crates/db/src/models/workspace.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/db/src/models/workspace.rs)\n- [crates/db/src/models/session.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/db/src/models/session.rs)\n- [crates/db/src/models/task.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/db/src/models/task.rs)\n- [crates/db/src/models/project.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/db/src/models/project.rs)\n- [crates/db/src/models/repo.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/db/src/models/repo.rs)\n- [crates/api-types/src/lib.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/api-types/src/lib.rs)\n
    \n\n# Database and Data Models\n\n## Overview\n\nVibe Kanban uses a Rust-based database layer (`crates/db`) for persistent storage, with shared API types defined in `crates/api-types`. The architecture separates concerns between the database implementation, business logic, and the web frontend, enabling type-safe data flow across the application.\n\n## Architecture Overview\n\n```mermaid\ngraph TD\n A[Web Frontend
    packages/web-core] --> B[API Types
    crates/api-types]\n C[Remote Web
    packages/remote-web] --> B\n B --> D[Database Layer
    crates/db]\n D --> E[(SQLite
    Database)]\n F[Server
    crates/server] --> D\n```\n\n## Core Data Models\n\n### Workspace Model\n\nThe workspace model represents a coding agent execution environment. Each workspace is associated with a specific branch, terminal session, and dev server configuration.\n\n| Field | Type | Description |\n|-------|------|-------------|\n| `id` | UUID | Unique identifier for the workspace |\n| `name` | String | Display name of the workspace |\n| `project_id` | UUID | Associated project reference |\n| `branch_name` | String | Git branch name |\n| `is_running` | Boolean | Whether the agent is currently executing |\n| `is_pinned` | Boolean | Whether the workspace is pinned |\n| `has_pending_approval` | Boolean | Indicates pending approval state |\n| `has_running_dev_server` | Boolean | Whether dev server is active |\n| `has_unseen_activity` | Boolean | New activity since last view |\n| `files_changed` | Integer | Count of modified files |\n| `lines_added` | Integer | Lines of code added |\n| `lines_removed` | Integer | Lines of code removed |\n| `latest_process_completed_at` | Timestamp | Last process completion time |\n| `latest_process_status` | Enum | Current process status |\n\n资料来源：[crates/db/src/models/workspace.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/db/src/models/workspace.rs)\n\n### Session Model\n\nSessions represent individual coding agent execution runs within a workspace.\n\n| Field | Type | Description |\n|-------|------|-------------|\n| `id` | UUID | Unique session identifier |\n| `workspace_id` | UUID | Parent workspace reference |\n| `started_at` | Timestamp | Session start time |\n| `completed_at` | Timestamp | Session end time (nullable) |\n| `status` | Enum | Session state (running, completed, failed) |\n\n资料来源：[crates/db/src/models/session.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/db/src/models/session.rs)\n\n### Task Model\n\nTasks (issues) are the fundamental unit of work in the kanban system.\n\n| Field | Type | Description |\n|-------|------|-------------|\n| `id` | UUID | Unique task identifier |\n| `simple_id` | String | Human-readable ID (e.g., \"PROJ-123\") |\n| `title` | String | Task title |\n| `description` | Text | Detailed description |\n| `status_id` | UUID | Current status column |\n| `priority_id` | UUID | Priority level |\n| `assignee_id` | UUID | Assigned user (nullable) |\n| `project_id` | UUID | Parent project |\n| `created_at` | Timestamp | Creation time |\n| `updated_at` | Timestamp | Last modification time |\n\n资料来源：[crates/db/src/models/task.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/db/src/models/task.rs)\n\n### Project Model\n\nProjects organize tasks and workspaces into logical units.\n\n| Field | Type | Description |\n|-------|------|-------------|\n| `id` | UUID | Unique project identifier |\n| `name` | String | Project name |\n| `color` | String | Display color (hex format) |\n| `organization_id` | UUID | Parent organization |\n| `created_at` | Timestamp | Creation time |\n| `updated_at` | Timestamp | Last modification time |\n\n资料来源：[crates/db/src/models/project.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/db/src/models/project.rs)\n\n### Repository Model\n\nRepository configurations link external Git repositories to the system.\n\n| Field | Type | Description |\n|-------|------|-------------|\n| `id` | UUID | Unique repository identifier |\n| `display_name` | String | Repository display name |\n| `clone_url` | String | Git clone URL |\n| `default_branch` | String | Primary branch name |\n| `is_current` | Boolean | Currently checked out |\n\n资料来源：[crates/db/src/models/repo.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/db/src/models/repo.rs)\n\n## API Types System\n\nThe `crates/api-types` crate defines shared TypeScript types used across the frontend packages. These types ensure type safety between the server and client applications.\n\n### Key Type Exports\n\nThe API types module re-exports types from the database models and extends them with frontend-specific metadata:\n\n```typescript\n// Shared type definitions for workspace state\ninterface WorkspaceState {\n workspaceId: string;\n branchName: string;\n filesChanged: number;\n linesAdded: number;\n linesRemoved: number;\n isRunning: boolean;\n isPinned: boolean;\n hasPendingApproval: boolean;\n hasRunningDevServer: boolean;\n hasUnseenActivity: boolean;\n latestProcessCompletedAt: string | null;\n latestProcessStatus: ProcessStatus;\n prStatus: PRStatus | null;\n}\n```\n\n资料来源：[crates/api-types/src/lib.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/api-types/src/lib.rs)\n\n## State Management Integration\n\n### Workspace Diff Store\n\nThe frontend uses Zustand stores to manage client-side state that syncs with the database models.\n\n```typescript\n// From packages/web-core/src/shared/stores/useWorkspaceDiffStore.ts\nexport const useGetGitHubCommentCountForFile = () =>\n useWorkspaceDiffStore((s) => s.getGitHubCommentCountForFile);\n\nexport const useGetFilesWithGitHubComments = () =>\n useWorkspaceDiffStore((s) => s.getFilesWithGitHubComments);\n```\n\n### UI Preferences Store\n\nUser interface preferences are persisted and managed through a dedicated store:\n\n| Preference | Type | Description |\n|------------|------|-------------|\n| `layoutMode` | 'workspaces' \\| 'kanban' | Active layout view |\n| `isLeftSidebarVisible` | Boolean | Left sidebar visibility |\n| `isRightSidebarVisible` | Boolean | Right sidebar visibility |\n| `isTerminalVisible` | Boolean | Terminal panel visibility |\n| `paneSizes` | Record | Customizable panel dimensions |\n| `collapsedPaths` | Record | Expanded/collapsed tree states |\n\n资料来源：[packages/web-core/src/shared/stores/useUiPreferencesStore.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/stores/useUiPreferencesStore.ts)\n\n## Data Flow Architecture\n\n```mermaid\ngraph LR\n A[User Action] --> B[React Component]\n B --> C[Zustand Store]\n C --> D[API Client]\n D --> E[Rust Server
    crates/server]\n E --> F[Database Layer
    crates/db]\n F --> G[(SQLite)]\n G --> F\n F --> E\n E --> D\n D --> C\n C --> B\n```\n\n## Relationships Between Models\n\n```mermaid\nerDiagram\n PROJECT ||--o{ TASK : contains\n PROJECT ||--o{ WORKSPACE : contains\n PROJECT ||--o{ REPO : links\n TASK ||--o{ SESSION : executes\n WORKSPACE ||--o{ SESSION : contains\n REPO ||--o{ WORKSPACE : checked_out\n```\n\n## Database Module Structure\n\nThe database crate (`crates/db`) is organized into the following modules:\n\n| Module | Purpose |\n|--------|---------|\n| `lib.rs` | Main entry point, exports all models and database operations |\n| `models/mod.rs` | Model aggregation and re-exports |\n| `models/workspace.rs` | Workspace entity definition |\n| `models/session.rs` | Session entity definition |\n| `models/task.rs` | Task/Issue entity definition |\n| `models/project.rs` | Project entity definition |\n| `models/repo.rs` | Repository entity definition |\n\n资料来源：[crates/db/src/lib.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/db/src/lib.rs), [crates/db/src/models/mod.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/db/src/models/mod.rs)\n\n## Attachment Management\n\nThe system supports file attachments associated with tasks and comments:\n\n| Attachment Field | Type | Description |\n|------------------|------|-------------|\n| `id` | UUID | Unique attachment identifier |\n| `filename` | String | Original filename |\n| `blob_id` | String | Storage reference |\n| `upload_progress` | Integer | Upload percentage (0-100) |\n| `pending_status` | Enum | confirming, uploaded, failed |\n| `content_type` | String | MIME type |\n| `size_bytes` | Integer | File size |\n\n资料来源：[packages/web-core/src/shared/hooks/useAzureAttachments.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/hooks/useAzureAttachments.ts)\n\n## Process Tracking\n\nThe system tracks coding agent processes with the following states:\n\n| Status | Description |\n|--------|-------------|\n| `started` | Process initiated |\n| `running` | Currently executing |\n| `completed` | Successfully finished |\n| `failed` | Execution error |\n| `cancelled` | User terminated |\n\n资料来源：[packages/web-core/src/shared/components/tasks/TaskDetails/ProcessesTab.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/components/tasks/TaskDetails/ProcessesTab.tsx)\n\n## Summary\n\nThe Vibe Kanban database layer provides a type-safe, Rust-based persistence system with clear separation between:\n\n1. **Core Entities**: Workspace, Session, Task, Project, and Repository models define the data structure\n2. **API Types**: Shared TypeScript types ensure consistency across frontend packages\n3. **State Management**: Zustand stores provide reactive client-side state synchronized with server data\n4. **Relationships**: Well-defined foreign key relationships enable complex queries and data navigation\n\nThis architecture enables the application to manage coding agent workflows efficiently while maintaining data integrity and type safety throughout the stack.\n\n---\n\n\n\n## Deployment and Infrastructure\n\n### 相关页面\n\n相关主题：[Relay and Remote Access](#page-relay-remote-access), [Development Setup](#page-development-setup)\n\n
    \nRelated Source Files\n\n以下源码文件用于生成本页说明：\n\n- [Dockerfile](https://github.com/BloopAI/vibe-kanban/blob/main/Dockerfile)\n- [Caddyfile.example](https://github.com/BloopAI/vibe-kanban/blob/main/Caddyfile.example)\n- [crates/remote/Dockerfile](https://github.com/BloopAI/vibe-kanban/blob/main/crates/remote/Dockerfile)\n- [crates/relay-tunnel/Dockerfile](https://github.com/BloopAI/vibe-kanban/blob/main/crates/relay-tunnel/Dockerfile)\n- [docs/self-hosting/deploy-docker.mdx](https://github.com/BloopAI/vibe-kanban/blob/main/docs/self-hosting/deploy-docker.mdx)\n- [docs/self-hosting/local-development.mdx](https://github.com/BloopAI/vibe-kanban/blob/main/docs/self-hosting/local-development.mdx)\n
    \n\n# Deployment and Infrastructure\n\n## Overview\n\nVibe Kanban provides flexible deployment options ranging from local development to production-grade Docker-based self-hosting. The infrastructure supports both single-machine deployments and distributed architectures with optional relay tunneling for remote access. 资料来源：[README.md:1-60]()\n\nThe project uses a monorepo structure with the following key deployment components:\n\n| Component | Technology | Purpose |\n|-----------|------------|---------|\n| Web UI | React/TypeScript | Frontend application |\n| API Server | Rust (Axum) | Backend REST API |\n| Database | PostgreSQL | Primary data store |\n| Relay Tunnel | Rust | Secure remote access |\n| TLS Termination | Caddy | HTTPS reverse proxy |\n\n## Architecture Overview\n\nVibe Kanban's deployment architecture consists of multiple Docker containers orchestrated via Docker Compose. The system supports three deployment profiles: default, relay, and attachments.\n\n```mermaid\ngraph TD\n User([User Browser]) --> Caddy[Caddy Reverse Proxy]\n Caddy --> RemoteWeb[remote-web:3001]\n Caddy --> RemoteServer[remote-server:3000]\n \n RemoteServer --> Electric[(Electric SQL
    PostgreSQL)]\n RemoteServer --> Azurite[(Azurite
    Blob Storage)]\n \n RemoteWeb -->|WebSocket| RelayTunnel[relay-tunnel:8082]\n User -->|Secure Tunnel| RelayTunnel\n \n subgraph Docker Network\n Caddy\n RemoteWeb\n RemoteServer\n Electric\n Azurite\n RelayTunnel\n end\n```\n\n### Component Responsibilities\n\n| Service | Port | Description |\n|---------|------|-------------|\n| `remote-web` | 3001 | Remote web UI and API gateway |\n| `remote-server` | 3000 | Core API server with business logic |\n| `electric` | 5433 | PostgreSQL with Electric SQL sync |\n| `relay-tunnel` | 8082 | WebSocket relay for remote access |\n| `azurite` | 10000 | Local Azure Blob Storage emulator |\n\n## Docker Deployment\n\n### Prerequisites\n\n- Docker Engine 24.0+\n- Docker Compose v2.20+\n- Minimum 4GB RAM available\n- 10GB disk space\n\n### Quick Start\n\nClone the repository and navigate to the remote deployment directory:\n\n```bash\ncd crates/remote\ndocker compose --env-file .env.remote up --build\n```\n\nThis starts the default stack with web UI, API server, and database.\n\n### Starting the Development Stack\n\nFrom the repository root:\n\n```bash\npnpm run remote:dev\n```\n\nFor full stack with relay and local attachment storage:\n\n```bash\npnpm run remote:dev:full\n```\n\nEquivalent manual command:\n\n```bash\ncd crates/remote\ndocker compose --env-file .env.remote --profile relay --profile attachments up --build\n```\n\n资料来源：[crates/remote/README.md:45-70]()\n\n## Environment Configuration\n\n### Required Environment Variables\n\n| Variable | Description | Example |\n|----------|-------------|---------|\n| `DATABASE_URL` | PostgreSQL connection string | `postgres://remote:remote@localhost:5433/remote` |\n| `JWT_SECRET` | Secret for JWT token signing | Base64 encoded 48-byte string |\n| `VK_SHARED_API_BASE` | Internal API base URL | `http://localhost:3000` |\n| `VK_SHARED_RELAY_API_BASE` | Relay API base URL | `http://relay.localhost:3001` |\n\n### Generating JWT Secret\n\nGenerate a secure JWT secret using OpenSSL:\n\n```bash\nopenssl rand -base64 48\n```\n\n### OAuth Configuration\n\nConfigure OAuth callback URLs for external authentication:\n\n| Provider | Callback URL |\n|----------|--------------|\n| GitHub | `https://localhost:3001/v1/oauth/github/callback` |\n| Google | `https://localhost:3001/v1/oauth/google/callback` |\n\n资料来源：[crates/remote/README.md:1-50]()\n\n## Docker Compose Profiles\n\nVibe Kanban uses Docker Compose profiles to enable optional components:\n\n### Default Profile\n\nStarts core infrastructure only:\n\n```bash\ncd crates/remote\ndocker compose --env-file .env.remote up --build\n```\n\nServices started:\n- `remote-db` (PostgreSQL via Electric SQL)\n- `remote-server`\n- `remote-web`\n\n### Relay Profile\n\nEnables remote access via WebSocket tunnel:\n\n```bash\ncd crates/remote\ndocker compose --env-file .env.remote --profile relay up --build\n```\n\nAdditional service:\n- `relay-tunnel` on port 8082\n\n### Attachments Profile\n\nEnables local file storage using Azurite:\n\n```bash\ncd crates/remote\ndocker compose --env-file .env.remote --profile attachments up --build\n```\n\nAdditional service:\n- `azurite` on ports 10000/10001/10002\n\n### Combined Profiles\n\nEnable both relay and attachments:\n\n```bash\ncd crates/remote\ndocker compose --env-file .env.remote --profile relay --profile attachments up --build\n```\n\n## Local HTTPS with Caddy\n\nFor development environments requiring HTTPS, Caddy serves as a reverse proxy with automatic TLS certificate management.\n\n### Install Caddy\n\n**macOS:**\n```bash\nbrew install caddy\n```\n\n**Debian/Ubuntu:**\n```bash\nsudo apt install caddy\n```\n\n### Configuration\n\nThe repository includes `Caddyfile.example` with the required routing configuration. Start Caddy from the repository root:\n\n```bash\ncaddy run --config Caddyfile.example\n```\n\nOn first run, Caddy installs a local CA certificate and may prompt for administrator password.\n\n### Endpoint Routing\n\n| External URL | Internal Service |\n|--------------|------------------|\n| `https://localhost:3001` | Remote web UI/API |\n| `https://relay.localhost:3001` | Relay API |\n\n资料来源：[crates/remote/README.md:15-45]()\n\n### Health Check Endpoints\n\nVerify deployment health:\n\n```bash\ncurl -sk https://localhost:3001/v1/health\ncurl -sk https://relay.localhost:3001/health\n```\n\nIf the relay health endpoint returns HTML instead of `{\"status\":\"ok\"}`, the Caddy host routing configuration is incorrect.\n\n## Database Infrastructure\n\n### Electric SQL with PostgreSQL\n\nVibe Kanban uses Electric SQL for database synchronization, providing:\n- Real-time data sync across instances\n- Offline-first capability\n- PostgreSQL compatibility\n\n### Connection Configuration\n\n| Setting | Default Value |\n|---------|---------------|\n| Host | `localhost` |\n| Port | `5433` |\n| Database | `remote` |\n| Username | `remote` |\n| Password | `remote` |\n\n### Container Networking\n\nAll services communicate through the Docker bridge network, with the database accessible only to internal services.\n\n## Relay Tunnel Service\n\nThe relay tunnel enables secure remote access to Vibe Kanban when deployed behind NAT or firewalls.\n\n```mermaid\nsequenceDiagram\n participant Client as Remote Client\n participant Relay as relay-tunnel:8082\n participant WebUI as remote-web:3001\n participant Server as remote-server:3000\n \n Client->>Relay: WebSocket Connection\n Relay->>WebUI: Forward WebSocket\n WebUI->>Server: API Request\n Server-->>WebUI: Response\n WebUI-->>Relay: WebSocket Response\n Relay-->>Client: Tunneled Response\n```\n\n### Requirements\n\n- `relay` profile enabled in Docker Compose\n- `VK_SHARED_RELAY_API_BASE` environment variable set\n- Caddy configured with `relay.localhost:3001` route\n\n## Attachment Storage\n\n### Azure Blob Storage (Production)\n\nProduction deployments should configure Azure Blob Storage for file attachments:\n\n| Setting | Description |\n|---------|-------------|\n| Account Name | Azure storage account name |\n| Account Key | Azure storage access key |\n| Container | Blob container name |\n| Endpoint | Azure blob endpoint URL |\n\n### Azurite (Development)\n\nLocal development uses Azurite, an Azure Storage emulator:\n\n```yaml\nazurite:\n image: mcr.microsoft.com/azure-storage/azurite\n ports:\n - \"10000:10000\" # Blob service\n - \"10001:10001\" # Queue service\n - \"10002:10002\" # Table service\n```\n\n资料来源：[crates/remote/README.md:70-95]()\n\n## API Endpoints Reference\n\n### Health Check Endpoints\n\n| Endpoint | Method | Description |\n|----------|--------|-------------|\n| `/v1/health` | GET | API server health status |\n| `/health` | GET | Relay tunnel health status |\n\n### OAuth Endpoints\n\n| Endpoint | Provider |\n|----------|----------|\n| `/v1/oauth/github/callback` | GitHub |\n| `/v1/oauth/google/callback` | Google |\n\n## Deployment States\n\n```mermaid\nstateDiagram-v2\n [*] --> Initializing\n Initializing --> StartingServices: docker compose up\n StartingServices --> DatabaseReady: PostgreSQL online\n DatabaseReady --> APIServerReady: Server responding\n APIServerReady --> WebUIAvailable: UI accessible\n WebUIAvailable --> RelayEnabled: relay profile active\n RelayEnabled --> [*]: Services running\n \n Initializing --> Failed: Container error\n StartingServices --> Failed: Port conflict\n APIServerReady --> Degraded: Health check failing\n Degraded --> APIServerReady: Auto-recovery\n Failed --> Initializing: Restart triggered\n```\n\n## Development vs Production\n\n### Development Stack\n\n| Aspect | Setting |\n|--------|---------|\n| TLS | Self-signed or Caddy |\n| Storage | Azurite emulator |\n| Database | Local Electric SQL |\n| Access | Local network only |\n| Debugging | Full logging enabled |\n\n### Production Stack\n\n| Aspect | Setting |\n|--------|---------|\n| TLS | Let's Encrypt or managed certificate |\n| Storage | Azure Blob Storage |\n| Database | Managed PostgreSQL or Electric SQL Cloud |\n| Access | VPN or secure tunnel |\n| Debugging | Structured logging with levels |\n\n## Troubleshooting\n\n### Container Startup Failures\n\n1. Check port availability:\n ```bash\n lsof -i :3000 -i :3001 -i :5433 -i :8082\n ```\n\n2. Verify environment variables are set:\n ```bash\n docker compose --env-file .env.remote config\n ```\n\n3. Check container logs:\n ```bash\n docker compose --env-file .env.remote logs -f\n ```\n\n### Database Connection Issues\n\n1. Ensure database container is healthy:\n ```bash\n docker compose ps remote-db\n ```\n\n2. Test connection manually:\n ```bash\n psql \"postgres://remote:remote@localhost:5433/remote\"\n ```\n\n### Relay Tunnel Not Working\n\n1. Verify Caddy routing for `relay.localhost`:\n ```bash\n curl -sk https://relay.localhost:3001/health\n ```\n\n2. Check relay container logs:\n ```bash\n docker compose logs relay-tunnel\n ```\n\n3. Ensure firewall allows WebSocket connections on port 8082\n\n### OAuth Configuration Errors\n\nEnsure OAuth callback URLs in your provider settings match exactly:\n\n- Protocol: `https://` (not `http://`)\n- Port: `3001` (unless custom configured)\n- Path: `/v1/oauth/{provider}/callback`\n\n## Security Considerations\n\n### Network Isolation\n\nAll internal services communicate within the Docker network without exposure to the host:\n\n```yaml\nnetworks:\n default:\n driver: bridge\n internal: false\n```\n\n### Secret Management\n\n- Never commit `.env.remote` to version control\n- Use Docker secrets for production deployments\n- Rotate `JWT_SECRET` periodically\n\n### TLS Requirements\n\n- Use HTTPS in all production deployments\n- Configure Caddy with valid certificates for OAuth providers\n- Some OAuth providers require HTTPS callback URLs\n\n---\n\n---\n\n## Doramagic 踩坑日志\n\n项目：BloopAI/vibe-kanban\n\n摘要：发现 19 个潜在踩坑项，其中 3 个为 high/blocking；最高优先级：安装坑 - 来源证据：Deployment(Other(Migration failed: error returned from database: (code: 1) no such column: ep.session_id))。\n\n## 1. 安装坑 · 来源证据：Deployment(Other(Migration failed: error returned from database: (code: 1) no such column: ep.session_id))\n\n- 严重度：high\n- 证据强度：source_linked\n- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Deployment(Other(Migration failed: error returned from database: (code: 1) no such column: ep.session_id))\n- 对用户的影响：可能影响升级、迁移或版本选择。\n- 建议检查：来源问题仍为 open，Pack Agent 需要复核是否仍影响当前版本。\n- 防护动作：不得脱离来源链接放大为确定性结论；需要标注适用版本和复核状态。\n- 证据：community_evidence:github | cevd_b34b2ea1b35a4dc2a4a0eb0681bdb883 | https://github.com/BloopAI/vibe-kanban/issues/2972 | 来源讨论提到 windows 相关条件，需在安装/试用前复核。\n\n## 2. 配置坑 · 来源证据：Support for self-hosted projects and better export\n\n- 严重度：high\n- 证据强度：source_linked\n- 发现：GitHub 社区证据显示该项目存在一个配置相关的待验证问题：Support for self-hosted projects and better export\n- 对用户的影响：可能阻塞安装或首次运行。\n- 建议检查：来源问题仍为 open，Pack Agent 需要复核是否仍影响当前版本。\n- 防护动作：不得脱离来源链接放大为确定性结论；需要标注适用版本和复核状态。\n- 证据：community_evidence:github | cevd_19d27caa9e34416a9f282869f76624b0 | https://github.com/BloopAI/vibe-kanban/issues/3396 | 来源类型 github_issue 暴露的待验证使用条件。\n\n## 3. 安全/权限坑 · 来源证据：[Proposal] JIRA Integration for Vibe Kanban\n\n- 严重度：high\n- 证据强度：source_linked\n- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：[Proposal] JIRA Integration for Vibe Kanban\n- 对用户的影响：可能影响授权、密钥配置或安全边界。\n- 建议检查：来源问题仍为 open，Pack Agent 需要复核是否仍影响当前版本。\n- 防护动作：不得脱离来源链接放大为确定性结论；需要标注适用版本和复核状态。\n- 证据：community_evidence:github | cevd_ab38fe97c4574e2da01ddedd71a4fbac | https://github.com/BloopAI/vibe-kanban/issues/2424 | 来源类型 github_issue 暴露的待验证使用条件。\n\n## 4. 安装坑 · 来源证据：Pre-release v0.1.40-20260401153532\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Pre-release v0.1.40-20260401153532\n- 对用户的影响：可能阻塞安装或首次运行。\n- 建议检查：来源显示可能已有修复、规避或版本变化，说明书中必须标注适用版本。\n- 防护动作：不得脱离来源链接放大为确定性结论；需要标注适用版本和复核状态。\n- 证据：community_evidence:github | cevd_f4b99d437a4f4fd4989d2b3ef036553b | https://github.com/BloopAI/vibe-kanban/releases/tag/v0.1.40-20260401153532 | 来源讨论提到 docker 相关条件，需在安装/试用前复核。\n\n## 5. 安装坑 · 来源证据：Release v0.1.36\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Release v0.1.36\n- 对用户的影响：可能阻塞安装或首次运行。\n- 建议检查：来源显示可能已有修复、规避或版本变化，说明书中必须标注适用版本。\n- 防护动作：不得脱离来源链接放大为确定性结论；需要标注适用版本和复核状态。\n- 证据：community_evidence:github | cevd_527645be4e3f438e81757ef265a70d79 | https://github.com/BloopAI/vibe-kanban/releases/tag/v0.1.36-20260323174633 | 来源讨论提到 npm 相关条件，需在安装/试用前复核。\n\n## 6. 安装坑 · 来源证据：Release v0.1.43\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Release v0.1.43\n- 对用户的影响：可能增加新用户试用和生产接入成本。\n- 建议检查：来源显示可能已有修复、规避或版本变化，说明书中必须标注适用版本。\n- 防护动作：不得脱离来源链接放大为确定性结论；需要标注适用版本和复核状态。\n- 证据：community_evidence:github | cevd_53704dc7171446fe86b2017f72212ddc | https://github.com/BloopAI/vibe-kanban/releases/tag/v0.1.43-20260417125614 | 来源讨论提到 node 相关条件，需在安装/试用前复核。\n\n## 7. 配置坑 · 可能修改宿主 AI 配置\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：项目面向 Claude/Cursor/Codex/Gemini/OpenCode 等宿主，或安装命令涉及用户配置目录。\n- 对用户的影响：安装可能改变本机 AI 工具行为，用户需要知道写入位置和回滚方法。\n- 建议检查：列出会写入的配置文件、目录和卸载/回滚步骤。\n- 防护动作：涉及宿主配置目录时必须给回滚路径，不能只给安装命令。\n- 证据：capability.host_targets | github_repo:1002125012 | https://github.com/BloopAI/vibe-kanban | host_targets=claude, claude_code\n\n## 8. 能力坑 · 能力判断依赖假设\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：README/documentation is current enough for a first validation pass.\n- 对用户的影响：假设不成立时，用户拿不到承诺的能力。\n- 建议检查：将假设转成下游验证清单。\n- 防护动作：假设必须转成验证项；没有验证结果前不能写成事实。\n- 证据：capability.assumptions | github_repo:1002125012 | https://github.com/BloopAI/vibe-kanban | README/documentation is current enough for a first validation pass.\n\n## 9. 运行坑 · 来源证据：Pre-release v0.1.39-20260331145823\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：GitHub 社区证据显示该项目存在一个运行相关的待验证问题：Pre-release v0.1.39-20260331145823\n- 对用户的影响：可能阻塞安装或首次运行。\n- 建议检查：来源显示可能已有修复、规避或版本变化，说明书中必须标注适用版本。\n- 防护动作：不得脱离来源链接放大为确定性结论；需要标注适用版本和复核状态。\n- 证据：community_evidence:github | cevd_c005a56959634369929ce33eddbdc103 | https://github.com/BloopAI/vibe-kanban/releases/tag/v0.1.39-20260331145823 | 来源讨论提到 windows 相关条件，需在安装/试用前复核。\n\n## 10. 维护坑 · 来源证据：[Request] Support RDS for self hosting in AWS\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：GitHub 社区证据显示该项目存在一个维护/版本相关的待验证问题：[Request] Support RDS for self hosting in AWS\n- 对用户的影响：可能影响升级、迁移或版本选择。\n- 建议检查：来源问题仍为 open，Pack Agent 需要复核是否仍影响当前版本。\n- 防护动作：不得脱离来源链接放大为确定性结论；需要标注适用版本和复核状态。\n- 证据：community_evidence:github | cevd_f613b792c20942519560c0a286a82005 | https://github.com/BloopAI/vibe-kanban/issues/3405 | 来源类型 github_issue 暴露的待验证使用条件。\n\n## 11. 维护坑 · 维护活跃度未知\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：未记录 last_activity_observed。\n- 对用户的影响：新项目、停更项目和活跃项目会被混在一起，推荐信任度下降。\n- 建议检查：补 GitHub 最近 commit、release、issue/PR 响应信号。\n- 防护动作：维护活跃度未知时，推荐强度不能标为高信任。\n- 证据：evidence.maintainer_signals | github_repo:1002125012 | https://github.com/BloopAI/vibe-kanban | last_activity_observed missing\n\n## 12. 安全/权限坑 · 下游验证发现风险项\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：no_demo\n- 对用户的影响：下游已经要求复核，不能在页面中弱化。\n- 建议检查：进入安全/权限治理复核队列。\n- 防护动作：下游风险存在时必须保持 review/recommendation 降级。\n- 证据：downstream_validation.risk_items | github_repo:1002125012 | https://github.com/BloopAI/vibe-kanban | no_demo; severity=medium\n\n## 13. 安全/权限坑 · 存在安全注意事项\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：No sandbox install has been executed yet; downstream must verify before user use.\n- 对用户的影响：用户安装前需要知道权限边界和敏感操作。\n- 建议检查：转成明确权限清单和安全审查提示。\n- 防护动作：安全注意事项必须面向用户前置展示。\n- 证据：risks.safety_notes | github_repo:1002125012 | https://github.com/BloopAI/vibe-kanban | No sandbox install has been executed yet; downstream must verify before user use.\n\n## 14. 安全/权限坑 · 存在评分风险\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：no_demo\n- 对用户的影响：风险会影响是否适合普通用户安装。\n- 建议检查：把风险写入边界卡，并确认是否需要人工复核。\n- 防护动作：评分风险必须进入边界卡，不能只作为内部分数。\n- 证据：risks.scoring_risks | github_repo:1002125012 | https://github.com/BloopAI/vibe-kanban | no_demo; severity=medium\n\n## 15. 安全/权限坑 · 来源证据：Issue: Unclear Git + Bitbucket Setup for Vibe-Kanban (OpenCode) in Docker\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：Issue: Unclear Git + Bitbucket Setup for Vibe-Kanban (OpenCode) in Docker\n- 对用户的影响：可能影响升级、迁移或版本选择。\n- 建议检查：来源问题仍为 open，Pack Agent 需要复核是否仍影响当前版本。\n- 防护动作：不得脱离来源链接放大为确定性结论；需要标注适用版本和复核状态。\n- 证据：community_evidence:github | cevd_7d289a7b68ee4299ae4a5e54b0e64e35 | https://github.com/BloopAI/vibe-kanban/issues/3410 | 来源讨论提到 docker 相关条件，需在安装/试用前复核。\n\n## 16. 安全/权限坑 · 来源证据：Pre-release v0.1.37-20260327101540\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：Pre-release v0.1.37-20260327101540\n- 对用户的影响：可能影响授权、密钥配置或安全边界。\n- 建议检查：来源显示可能已有修复、规避或版本变化，说明书中必须标注适用版本。\n- 防护动作：不得脱离来源链接放大为确定性结论；需要标注适用版本和复核状态。\n- 证据：community_evidence:github | cevd_d648fba4c94b4791ac2e7683f6cb1361 | https://github.com/BloopAI/vibe-kanban/releases/tag/v0.1.37-20260327101540 | 来源讨论提到 macos 相关条件，需在安装/试用前复核。\n\n## 17. 安全/权限坑 · 来源证据：remote-v0.1.26\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：remote-v0.1.26\n- 对用户的影响：可能影响授权、密钥配置或安全边界。\n- 建议检查：来源显示可能已有修复、规避或版本变化，说明书中必须标注适用版本。\n- 防护动作：不得脱离来源链接放大为确定性结论；需要标注适用版本和复核状态。\n- 证据：community_evidence:github | cevd_3f212752e8c142d68ffe2993ac23dd37 | https://github.com/BloopAI/vibe-kanban/releases/tag/remote-v0.1.26 | 来源讨论提到 macos 相关条件，需在安装/试用前复核。\n\n## 18. 维护坑 · issue/PR 响应质量未知\n\n- 严重度：low\n- 证据强度：source_linked\n- 发现：issue_or_pr_quality=unknown。\n- 对用户的影响：用户无法判断遇到问题后是否有人维护。\n- 建议检查：抽样最近 issue/PR，判断是否长期无人处理。\n- 防护动作：issue/PR 响应未知时，必须提示维护风险。\n- 证据：evidence.maintainer_signals | github_repo:1002125012 | https://github.com/BloopAI/vibe-kanban | issue_or_pr_quality=unknown\n\n## 19. 维护坑 · 发布节奏不明确\n\n- 严重度：low\n- 证据强度：source_linked\n- 发现：release_recency=unknown。\n- 对用户的影响：安装命令和文档可能落后于代码，用户踩坑概率升高。\n- 建议检查：确认最近 release/tag 和 README 安装命令是否一致。\n- 防护动作：发布节奏未知或过期时，安装说明必须标注可能漂移。\n- 证据：evidence.maintainer_signals | github_repo:1002125012 | https://github.com/BloopAI/vibe-kanban | release_recency=unknown\n\n\n", "markdown_key": "vibe-kanban", "pages": "draft", "source_refs": [ { "evidence_id": "github_repo:1002125012", "kind": "repo", "supports_claim_ids": [ "claim_identity", "claim_distribution", "claim_capability" ], "url": "https://github.com/BloopAI/vibe-kanban" }, { "evidence_id": "art_f7a8f562234649b7b40da7395ba0ea47", "kind": "docs", "supports_claim_ids": [ "claim_identity", "claim_distribution", "claim_capability" ], "url": "https://github.com/BloopAI/vibe-kanban#readme" } ], "summary": "DeepWiki/Human Wiki 完整输出，末尾追加 Discovery Agent 踩坑日志。", "title": "vibe-kanban 说明书", "toc": [ "https://github.com/BloopAI/vibe-kanban 项目说明书", "目录", "Project Introduction", "Purpose and Scope", "Supported AI Agents", "Architecture Overview", "Key Features", "UI State Management", "Doramagic 踩坑日志" ] } }, "quality_gate": { "blocking_gaps": [], "category_confidence": "medium", "compile_status": "ready_for_review", "five_assets_present": true, "install_sandbox_verified": true, "missing_evidence": [], "next_action": "publish to Doramagic.ai project surfaces", "prompt_preview_boundary_ok": true, "publish_status": "publishable", "quick_start_verified": true, "repo_clone_verified": true, "repo_commit": "4deb7eca8f381f7cbc1f9d15515a9ab8f8009053", "repo_inspection_error": null, "repo_inspection_files": [ "pnpm-lock.yaml", "Dockerfile", "package.json", "README.md", "docs/AGENTS.md", "docs/troubleshooting.mdx", "docs/browser-testing.mdx", "docs/reviewing-code.mdx", "docs/issue-management.mdx", "docs/getting-started.mdx", "docs/CLAUDE.md", "docs/supported-coding-agents.mdx", "docs/index.mdx", "docs/README.md", "docs/docs.json", "docs/frontend-ui-library-refactor-audit.md", "docs/remote-access.mdx", "docs/responsible-disclosure.mdx", "docs/settings/general.mdx", "docs/settings/remote-projects.mdx", "docs/settings/agent-configurations.mdx", "docs/settings/organization-settings.mdx", "docs/settings/index.mdx", "docs/settings/creating-task-tags.mdx", "docs/settings/mcp-servers.mdx", "docs/settings/projects-repositories.mdx", "docs/workspaces/changes.mdx", "docs/workspaces/slash-commands.mdx", "docs/workspaces/managing-workspaces.mdx", "docs/workspaces/multi-repo-sessions.mdx", "docs/workspaces/repositories.mdx", "docs/workspaces/git-operations.mdx", "docs/workspaces/index.mdx", "docs/workspaces/command-bar.mdx", "docs/workspaces/interface.mdx", "docs/workspaces/chat-interface.mdx", "docs/workspaces/creating-workspaces.mdx", "docs/workspaces/sessions.mdx", "docs/core-features/reviewing-code-changes.mdx", "docs/core-features/new-task-attempts.mdx" ], "repo_inspection_verified": true, "review_reasons": [], "tag_count_ok": true, "unsupported_claims": [] }, "schema_version": "0.1", "user_assets": { "ai_context_pack": { "asset_id": "ai_context_pack", "filename": "AI_CONTEXT_PACK.md", "markdown": "# vibe-kanban - Doramagic AI Context Pack\n\n> 定位：安装前体验与判断资产。它帮助宿主 AI 有一个好的开始，但不代表已经安装、执行或验证目标项目。\n\n## 充分原则\n\n- **充分原则，不是压缩原则**：AI Context Pack 应该充分到让宿主 AI 在开工前理解项目价值、能力边界、使用入口、风险和证据来源；它可以分层组织，但不以最短摘要为目标。\n- **压缩策略**：只压缩噪声和重复内容，不压缩会影响判断和开工质量的上下文。\n\n## 给宿主 AI 的使用方式\n\n你正在读取 Doramagic 为 vibe-kanban 编译的 AI Context Pack。请把它当作开工前上下文：帮助用户理解适合谁、能做什么、如何开始、哪些必须安装后验证、风险在哪里。不要声称你已经安装、运行或执行了目标项目。\n\n## Claim 消费规则\n\n- **事实来源**：Repo Evidence + Claim/Evidence Graph；Human Wiki 只提供显著性、术语和叙事结构。\n- **事实最低状态**：`supported`\n- `supported`：可以作为项目事实使用，但回答中必须引用 claim_id 和证据路径。\n- `weak`：只能作为低置信度线索，必须要求用户继续核实。\n- `inferred`：只能用于风险提示或待确认问题，不能包装成项目事实。\n- `unverified`：不得作为事实使用，应明确说证据不足。\n- `contradicted`：必须展示冲突来源，不得替用户强行选择一个版本。\n\n## 它最适合谁\n\n- **正在使用 Claude/Codex/Cursor/Gemini 等宿主 AI 的开发者**：README 或插件配置提到多个宿主 AI。 证据：`README.md` Claim：`clm_0002` supported 0.86\n\n## 它能做什么\n\n- **命令行启动或安装流程**（需要安装后验证）：项目文档中存在可执行命令，真实使用需要在本地或宿主环境中运行这些命令。 证据：`README.md` Claim：`clm_0001` supported 0.86\n\n## 怎么开始\n\n- `npx vibe-kanban` 证据：`README.md` Claim：`clm_0003` supported 0.86\n\n## 继续前判断卡\n\n- **当前建议**：需要管理员/安全审批\n- **为什么**：继续前可能涉及密钥、账号、外部服务或敏感上下文，建议先经过管理员或安全审批。\n\n### 30 秒判断\n\n- **现在怎么做**：需要管理员/安全审批\n- **最小安全下一步**：先跑 Prompt Preview；若涉及凭证或企业环境，先审批再试装\n- **先别相信**：工具权限边界不能在安装前相信。\n- **继续会触碰**：命令执行、宿主 AI 配置、本地环境或项目文件\n\n### 现在可以相信\n\n- **适合人群线索：正在使用 Claude/Codex/Cursor/Gemini 等宿主 AI 的开发者**（supported）：有 supported claim 或项目证据支撑，但仍不等于真实安装效果。 证据：`README.md` Claim：`clm_0002` supported 0.86\n- **能力存在：命令行启动或安装流程**（supported）：可以相信项目包含这类能力线索；是否适合你的具体任务仍要试用或安装后验证。 证据：`README.md` Claim：`clm_0001` supported 0.86\n- **存在 Quick Start / 安装命令线索**（supported）：可以相信项目文档出现过启动或安装入口；不要因此直接在主力环境运行。 证据：`README.md` Claim：`clm_0003` supported 0.86\n\n### 现在还不能相信\n\n- **工具权限边界不能在安装前相信。**（unverified）：MCP/tool 类项目通常会触碰文件、网络、浏览器或外部 API，必须真实检查权限和日志。\n- **真实输出质量不能在安装前相信。**（unverified）：Prompt Preview 只能展示引导方式，不能证明真实项目中的结果质量。\n- **宿主 AI 版本兼容性不能在安装前相信。**（unverified）：Claude、Cursor、Codex、Gemini 等宿主加载规则和版本差异必须在真实环境验证。\n- **不会污染现有宿主 AI 行为，不能直接相信。**（inferred）：Skill、plugin、AGENTS/CLAUDE/GEMINI 指令可能改变宿主 AI 的默认行为。 证据：`AGENTS.md`\n- **可安全回滚不能默认相信。**（unverified）：除非项目明确提供卸载和恢复说明，否则必须先在隔离环境验证。\n- **真实安装后是否与用户当前宿主 AI 版本兼容？**（unverified）：兼容性只能通过实际宿主环境验证。\n- **项目输出质量是否满足用户具体任务？**（unverified）：安装前预览只能展示流程和边界，不能替代真实评测。\n- **安装命令是否需要网络、权限或全局写入？**（unverified）：这影响企业环境和个人环境的安装风险。 证据：`README.md`\n\n### 继续会触碰什么\n\n- **命令执行**：包管理器、网络下载、本地插件目录、项目配置或用户主目录。 原因：运行第一条命令就可能产生环境改动；必须先判断是否值得跑。 证据：`README.md`\n- **宿主 AI 配置**：Claude/Codex/Cursor/Gemini/OpenCode 等宿主的 plugin、Skill 或规则加载配置。 原因：宿主配置会改变 AI 后续工作方式，可能和用户已有规则冲突。 证据：`AGENTS.md`\n- **本地环境或项目文件**：安装结果、插件缓存、项目配置或本地依赖目录。 原因：安装前无法证明写入范围和回滚方式，需要隔离验证。 证据：`README.md`\n- **环境变量 / API Key**：项目入口文档明确出现 API key、token、secret 或账号凭证配置。 原因：如果真实安装需要凭证，应先使用测试凭证并经过权限/合规判断。 证据：`README.md`\n- **宿主 AI 上下文**：AI Context Pack、Prompt Preview、Skill 路由、风险规则和项目事实。 原因：导入上下文会影响宿主 AI 后续判断，必须避免把未验证项包装成事实。\n\n### 最小安全下一步\n\n- **先跑 Prompt Preview**：用安装前交互式试用判断工作方式是否匹配，不需要授权或改环境。（适用：任何项目都适用，尤其是输出质量未知时。）\n- **只在隔离目录或测试账号试装**：避免安装命令污染主力宿主 AI、真实项目或用户主目录。（适用：存在命令执行、插件配置或本地写入线索时。）\n- **先备份宿主 AI 配置**：Skill、plugin、规则文件可能改变 Claude/Cursor/Codex 的默认行为。（适用：存在插件 manifest、Skill 或宿主规则入口时。）\n- **不要使用真实生产凭证**：环境变量/API key 一旦进入宿主或工具链，可能产生账号和合规风险。（适用：出现 API、TOKEN、KEY、SECRET 等环境线索时。）\n- **安装后只验证一个最小任务**：先验证加载、兼容、输出质量和回滚，再决定是否深用。（适用：准备从试用进入真实工作流时。）\n\n### 退出方式\n\n- **保留安装前状态**：记录原始宿主配置和项目状态，后续才能判断是否可恢复。\n- **准备移除宿主 plugin / Skill / 规则入口**：如果试装后行为异常，可以把宿主 AI 恢复到试装前状态。\n- **记录安装命令和写入路径**：没有明确卸载说明时，至少要知道哪些目录或配置需要手动清理。\n- **准备撤销测试 API key 或 token**：测试凭证泄露或误用时，可以快速止损。\n- **如果没有回滚路径，不进入主力环境**：不可回滚是继续前阻断项，不应靠信任或运气继续。\n\n## 哪些只能预览\n\n- 解释项目适合谁和能做什么\n- 基于项目文档演示典型对话流程\n- 帮助用户判断是否值得安装或继续研究\n\n## 哪些必须安装后验证\n\n- 真实安装 Skill、插件或 CLI\n- 执行脚本、修改本地文件或访问外部服务\n- 验证真实输出质量、性能和兼容性\n\n## 边界与风险判断卡\n\n- **把安装前预览误认为真实运行**：用户可能高估项目已经完成的配置、权限和兼容性验证。 处理方式：明确区分 prompt_preview_can_do 与 runtime_required。 Claim：`clm_0004` inferred 0.45\n- **命令执行会修改本地环境**：安装命令可能写入用户主目录、宿主插件目录或项目配置。 处理方式：先在隔离环境或测试账号中运行。 证据：`README.md` Claim：`clm_0005` supported 0.86\n- **待确认**：真实安装后是否与用户当前宿主 AI 版本兼容？。原因：兼容性只能通过实际宿主环境验证。\n- **待确认**：项目输出质量是否满足用户具体任务？。原因：安装前预览只能展示流程和边界，不能替代真实评测。\n- **待确认**：安装命令是否需要网络、权限或全局写入？。原因：这影响企业环境和个人环境的安装风险。\n\n## 开工前工作上下文\n\n### 加载顺序\n\n- 先读取 how_to_use.host_ai_instruction，建立安装前判断资产的边界。\n- 读取 claim_graph_summary，确认事实来自 Claim/Evidence Graph，而不是 Human Wiki 叙事。\n- 再读取 intended_users、capabilities 和 quick_start_candidates，判断用户是否匹配。\n- 需要执行具体任务时，优先查 role_skill_index，再查 evidence_index。\n- 遇到真实安装、文件修改、网络访问、性能或兼容性问题时，转入 risk_card 和 boundaries.runtime_required。\n\n### 任务路由\n\n- **命令行启动或安装流程**：先说明这是安装后验证能力，再给出安装前检查清单。 边界：必须真实安装或运行后验证。 证据：`README.md` Claim：`clm_0001` supported 0.86\n\n### 上下文规模\n\n- 文件总数：1897\n- 重要文件覆盖：40/1897\n- 证据索引条目：80\n- 角色 / Skill 条目：14\n\n### 证据不足时的处理\n\n- **missing_evidence**：说明证据不足，要求用户提供目标文件、README 段落或安装后验证记录；不要补全事实。\n- **out_of_scope_request**：说明该任务超出当前 AI Context Pack 证据范围，并建议用户先查看 Human Manual 或真实安装后验证。\n- **runtime_request**：给出安装前检查清单和命令来源，但不要替用户执行命令或声称已执行。\n- **source_conflict**：同时展示冲突来源，标记为待核实，不要强行选择一个版本。\n\n## Prompt Recipes\n\n### 适配判断\n\n- 目标：判断这个项目是否适合用户当前任务。\n- 预期输出：适配结论、关键理由、证据引用、安装前可预览内容、必须安装后验证内容、下一步建议。\n\n```text\n请基于 vibe-kanban 的 AI Context Pack，先问我 3 个必要问题，然后判断它是否适合我的任务。回答必须包含：适合谁、能做什么、不能做什么、是否值得安装、证据来自哪里。所有项目事实必须引用 evidence_refs、source_paths 或 claim_id。\n```\n\n### 安装前体验\n\n- 目标：让用户在安装前感受核心工作流，同时避免把预览包装成真实能力或营销承诺。\n- 预期输出：一段带边界标签的体验剧本、安装后验证清单和谨慎建议；不含真实运行承诺或强营销表述。\n\n```text\n请把 vibe-kanban 当作安装前体验资产，而不是已安装工具或真实运行环境。\n\n请严格输出四段：\n1. 先问我 3 个必要问题。\n2. 给出一段“体验剧本”：用 [安装前可预览]、[必须安装后验证]、[证据不足] 三种标签展示它可能如何引导工作流。\n3. 给出安装后验证清单：列出哪些能力只有真实安装、真实宿主加载、真实项目运行后才能确认。\n4. 给出谨慎建议：只能说“值得继续研究/试装”“先补充信息后再判断”或“不建议继续”，不得替项目背书。\n\n硬性边界：\n- 不要声称已经安装、运行、执行测试、修改文件或产生真实结果。\n- 不要写“自动适配”“确保通过”“完美适配”“强烈建议安装”等承诺性表达。\n- 如果描述安装后的工作方式，必须使用“如果安装成功且宿主正确加载 Skill，它可能会……”这种条件句。\n- 体验剧本只能写成“示例台词/假设流程”：使用“可能会询问/可能会建议/可能会展示”，不要写“已写入、已生成、已通过、正在运行、正在生成”。\n- Prompt Preview 不负责给安装命令；如用户准备试装，只能提示先阅读 Quick Start 和 Risk Card，并在隔离环境验证。\n- 所有项目事实必须来自 supported claim、evidence_refs 或 source_paths；inferred/unverified 只能作风险或待确认项。\n\n```\n\n### 角色 / Skill 选择\n\n- 目标：从项目里的角色或 Skill 中挑选最匹配的资产。\n- 预期输出：候选角色或 Skill 列表，每项包含适用场景、证据路径、风险边界和是否需要安装后验证。\n\n```text\n请读取 role_skill_index，根据我的目标任务推荐 3-5 个最相关的角色或 Skill。每个推荐都要说明适用场景、可能输出、风险边界和 evidence_refs。\n```\n\n### 风险预检\n\n- 目标：安装或引入前识别环境、权限、规则冲突和质量风险。\n- 预期输出：环境、权限、依赖、许可、宿主冲突、质量风险和未知项的检查清单。\n\n```text\n请基于 risk_card、boundaries 和 quick_start_candidates，给我一份安装前风险预检清单。不要替我执行命令，只说明我应该检查什么、为什么检查、失败会有什么影响。\n```\n\n### 宿主 AI 开工指令\n\n- 目标：把项目上下文转成一次对话开始前的宿主 AI 指令。\n- 预期输出：一段边界明确、证据引用明确、适合复制给宿主 AI 的开工前指令。\n\n```text\n请基于 vibe-kanban 的 AI Context Pack，生成一段我可以粘贴给宿主 AI 的开工前指令。这段指令必须遵守 not_runtime=true，不能声称项目已经安装、运行或产生真实结果。\n```\n\n\n## 角色 / Skill 索引\n\n- 共索引 14 个角色 / Skill / 项目文档条目。\n\n- **Mintlify technical writing rule**（project_doc）：You are an AI writing assistant specialised in creating exceptional technical documentation using Mintlify components and following industry-leading technical writing practices. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/AGENTS.md`\n- **Mintlify Starter Kit**（project_doc）：Mintlify Quickstart Guide https://starter.mintlify.com/quickstart 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/README.md`\n- **Repository Guidelines**（project_doc）：Project Structure & Module Organization - crates/ : Rust workspace crates — server API + bins , db SQLx models/migrations , executors , services , utils , git Git operations , api-types shared API types for local + remote , review PR review tool , deployment , local-deployment , remote . - packages/local-web/ : Local React + TypeScript app entrypoint Vite, Tailwind . Shell source in packages/local-web/src . - packag… 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`AGENTS.md`\n- **Overview**（project_doc）：Get 10X more out of Claude Code, Gemini CLI, Codex, Amp and other coding agents... 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`README.md`\n- **Vibe Kanban**（project_doc）：A visual project management tool for developers that integrates with git repositories and coding agents like Claude Code and Amp. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`npx-cli/README.md`\n- **Remote Crate — Agent Guidelines**（project_doc）：The remote crate is the hosted Vibe Kanban Cloud server: an Axum HTTP API, a React SPA frontend, and real-time sync via ElectricSQL. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`crates/remote/AGENTS.md`\n- **New Design System Styling Guidelines**（project_doc）：New Design System Styling Guidelines 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`packages/local-web/AGENTS.md`\n- **@vibe/ui**（project_doc）：Shared UI package for reusable web app primitives. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`packages/ui/README.md`\n- **Relay Test Client**（project_doc）：Standalone browser client for testing relay path routing without modifying the Remote frontend UX. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`scripts/relay-test-client/README.md`\n- **Frontend UI Package Refactor Audit**（project_doc）：- Source audited: packages/local-web/src/components/ / .tsx - Total components: 280 - Objective: identify what should move first into a new pnpm UI library package. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`docs/frontend-ui-library-refactor-audit.md`\n- **Contributor Covenant Code of Conduct**（project_doc）：Contributor Covenant Code of Conduct 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`CODE-OF-CONDUCT.md`\n- **Contributing & Change Control**（project_doc）：All changes to production code are governed by formal change control procedures. These procedures ensure that modifications are reviewed, approved, and deployed in a controlled manner. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`CONTRIBUTORS.md`\n- **Testing on Mobile Devices**（project_doc）：This guide explains how to access the remote-web frontend from a phone iPhone/Android for UI testing. It uses Tailscale https://tailscale.com for stable networking and HTTPS certificates, and Caddy https://caddyserver.com as a reverse proxy — no custom IPs, no random URLs, works on any network. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`mobile-testing.md`\n- **Init Prompt**（project_doc）：Generate a file named AGENTS.md that serves as a contributor guide for this repository. Your goal is to produce a clear, concise, and well-structured document with descriptive headings and actionable explanations for each section. Follow the outline below, but adapt as needed — add sections if relevant, and omit those that do not apply to this project. 激活提示：当用户需要理解项目结构、安装方式或边界时参考。 证据：`crates/executors/src/executors/codex/init_prompt.md`\n\n## 证据索引\n\n- 共索引 80 条证据。\n\n- **Mintlify technical writing rule**（documentation）：You are an AI writing assistant specialised in creating exceptional technical documentation using Mintlify components and following industry-leading technical writing practices. 证据：`docs/AGENTS.md`\n- **Mintlify Starter Kit**（documentation）：Mintlify Quickstart Guide https://starter.mintlify.com/quickstart 证据：`docs/README.md`\n- **Repository Guidelines**（documentation）：Project Structure & Module Organization - crates/ : Rust workspace crates — server API + bins , db SQLx models/migrations , executors , services , utils , git Git operations , api-types shared API types for local + remote , review PR review tool , deployment , local-deployment , remote . - packages/local-web/ : Local React + TypeScript app entrypoint Vite, Tailwind . Shell source in packages/local-web/src . - packages/remote-web/ : Remote deployment frontend entrypoint. - packages/web-core/ : Shared React + TypeScript frontend library used by local + remote web packages/web-core/src . - shared/ : Generated TypeScript types shared/types.ts , shared/remote-types.ts and agent tool schemas shar… 证据：`AGENTS.md`\n- **Overview**（documentation）：Get 10X more out of Claude Code, Gemini CLI, Codex, Amp and other coding agents... 证据：`README.md`\n- **Vibe Kanban**（documentation）：A visual project management tool for developers that integrates with git repositories and coding agents like Claude Code and Amp. 证据：`npx-cli/README.md`\n- **Remote Crate — Agent Guidelines**（documentation）：The remote crate is the hosted Vibe Kanban Cloud server: an Axum HTTP API, a React SPA frontend, and real-time sync via ElectricSQL. 证据：`crates/remote/AGENTS.md`\n- **New Design System Styling Guidelines**（documentation）：New Design System Styling Guidelines 证据：`packages/local-web/AGENTS.md`\n- **@vibe/ui**（documentation）：Shared UI package for reusable web app primitives. 证据：`packages/ui/README.md`\n- **Relay Test Client**（documentation）：Standalone browser client for testing relay path routing without modifying the Remote frontend UX. 证据：`scripts/relay-test-client/README.md`\n- **Package**（package_manifest）：{ \"name\": \"vibe-kanban\", \"private\": false, \"version\": \"0.1.44\", \"main\": \"index.js\", \"bin\": { \"vibe-kanban\": \"bin/cli.js\" }, \"scripts\": { \"build\": \"esbuild src/cli.ts --bundle --platform=node --target=node20 --format=cjs --outfile=bin/cli.js --external:adm-zip --banner:js=\\\" !/usr/bin/env node\\\"\", \"check\": \"tsc --noEmit -p tsconfig.json\" }, \"keywords\": , \"author\": \"bloop\", \"repository\": { \"type\": \"git\", \"url\": \"https://github.com/BloopAI/vibe-kanban\" }, \"engines\": { \"node\": \" =20.19.0\" }, \"license\": \"\", \"description\": \"NPX wrapper around vibe-kanban and vibe-kanban-mcp\", \"devDependencies\": { \"esbuild\": \"^0.27.2\" }, \"dependencies\": { \"adm-zip\": \"^0.5.16\", \"cac\": \"^7.0.0\" }, \"files\": \"bin\", \"d… 证据：`npx-cli/package.json`\n- **Package**（package_manifest）：{ \"name\": \"vibe-kanban\", \"version\": \"0.1.44\", \"private\": true, \"bin\": { \"vibe-kanban\": \"npx-cli/bin/cli.js\" }, \"files\": \"npx-cli/bin/cli.js\", \"npx-cli/dist/ \" , \"scripts\": { \"lint\": \"pnpm run local-web:lint && pnpm run ui:lint && pnpm run backend:lint && node scripts/check-unused-i18n-keys.mjs\", \"format\": \"pnpm run backend:format && pnpm run web-core:format && pnpm run local-web:format && pnpm run remote-web:format\", \"check\": \"pnpm run local-web:legacy-path-guard && pnpm run local-web:check && pnpm run remote-web:check && pnpm run web-core:check && pnpm run ui:check && pnpm run backend:check\", \"dev\": \"export FRONTEND PORT=$ node scripts/setup-dev-environment.js frontend && export BACKEND PO… 证据：`package.json`\n- **Package**（package_manifest）：{ \"name\": \"@vibe/local-web\", \"private\": true, \"version\": \"0.1.44\", \"type\": \"module\", \"scripts\": { \"dev\": \"VITE OPEN=${VITE OPEN:-false} vite\", \"build\": \"tsc && vite build\", \"check\": \"tsc --noEmit\", \"preview\": \"vite preview\", \"lint\": \"eslint . --ext ts,tsx --report-unused-disable-directives --max-warnings 0\", \"lint:fix\": \"eslint . --ext ts,tsx --fix\", \"lint:i18n\": \"LINT I18N=true eslint . --ext ts,tsx --max-warnings 0\", \"format\": \"prettier --write \\\"src/ / .{ts,tsx,js,jsx,json,css,md}\\\"\", \"format:check\": \"prettier --check \\\"src/ / .{ts,tsx,js,jsx,json,css,md}\\\"\" }, \"dependencies\": { \"@codemirror/lang-json\": \"^6.0.2\", \"@codemirror/language\": \"^6.11.2\", \"@codemirror/lint\": \"^6.8.5\", \"@codemirr… 证据：`packages/local-web/package.json`\n- **Package**（package_manifest）：{ \"name\": \"@vibe/remote-web\", \"private\": true, \"version\": \"0.1.0\", \"type\": \"module\", \"scripts\": { \"dev\": \"vite\", \"build\": \"tsc && vite build\", \"check\": \"tsc --noEmit\", \"preview\": \"vite preview\", \"format\": \"prettier --write \\\"src/ / .{ts,tsx,js,jsx,json,css,md}\\\"\", \"format:check\": \"prettier --check \\\"src/ / .{ts,tsx,js,jsx,json,css,md}\\\"\", \"migrate:structure\": \"node ../../scripts/migrate-remote-web-structure.mjs --apply\", \"migrate:structure:dry-run\": \"node ../../scripts/migrate-remote-web-structure.mjs\" }, \"dependencies\": { \"@ebay/nice-modal-react\": \"^1.2.13\", \"@phosphor-icons/react\": \"^2.1.10\", \"@tanstack/react-query\": \"^5.85.5\", \"@tanstack/react-router\": \"^1.161.1\", \"@tanstack/zod-adapter\"… 证据：`packages/remote-web/package.json`\n- **Package**（package_manifest）：{ \"name\": \"@vibe/ui\", \"private\": true, \"version\": \"0.1.0\", \"type\": \"module\", \"scripts\": { \"check\": \"tsc --noEmit -p tsconfig.json\", \"lint\": \"eslint . --ext ts,tsx --report-unused-disable-directives --max-warnings 0\", \"format\": \"prettier --config ../../packages/local-web/.prettierrc.json --write \\\"src/ / .{ts,tsx,js,jsx,json,md}\\\"\", \"format:check\": \"prettier --config ../../packages/local-web/.prettierrc.json --check \\\"src/ / .{ts,tsx,js,jsx,json,md}\\\"\" }, \"sideEffects\": false, \"exports\": { \"./components/ \": \"./src/components/ .tsx\", \"./lib/ \": \"./src/lib/ .ts\" }, \"dependencies\": { \"@ebay/nice-modal-react\": \"^1.2.13\", \"@tanstack/react-virtual\": \"^3.13.23\", \"@hello-pangea/dnd\": \"^18.0.1\", \"@le… 证据：`packages/ui/package.json`\n- **Package**（package_manifest）：{ \"name\": \"@vibe/web-core\", \"private\": true, \"version\": \"0.1.18\", \"type\": \"module\", \"exports\": { \"./project-fallback-page\": \"./src/project-routes/ProjectFallbackPage.tsx\", \"./project-search\": \"./src/project-routes/project-search.ts\", \"./ \": \"./src/ \" }, \"dependencies\": { \"@codemirror/lang-json\": \"^6.0.2\", \"@codemirror/language\": \"^6.11.2\", \"@codemirror/lint\": \"^6.8.5\", \"@codemirror/view\": \"^6.38.1\", \"@dnd-kit/core\": \"^6.3.1\", \"@dnd-kit/sortable\": \"^10.0.0\", \"@dnd-kit/utilities\": \"^3.2.2\", \"@ebay/nice-modal-react\": \"^1.2.13\", \"@git-diff-view/file\": \"^0.0.30\", \"@git-diff-view/react\": \"^0.0.30\", \"@hello-pangea/dnd\": \"^18.0.1\", \"@lexical/code\": \"^0.36.2\", \"@lexical/link\": \"^0.36.2\", \"@lexical/l… 证据：`packages/web-core/package.json`\n- **License**（source_file）：Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ 证据：`LICENSE`\n- **Frontend UI Package Refactor Audit**（documentation）：- Source audited: packages/local-web/src/components/ / .tsx - Total components: 280 - Objective: identify what should move first into a new pnpm UI library package. 证据：`docs/frontend-ui-library-refactor-audit.md`\n- **Contributor Covenant Code of Conduct**（documentation）：Contributor Covenant Code of Conduct 证据：`CODE-OF-CONDUCT.md`\n- **Contributing & Change Control**（documentation）：All changes to production code are governed by formal change control procedures. These procedures ensure that modifications are reviewed, approved, and deployed in a controlled manner. 证据：`CONTRIBUTORS.md`\n- **Testing on Mobile Devices**（documentation）：This guide explains how to access the remote-web frontend from a phone iPhone/Android for UI testing. It uses Tailscale https://tailscale.com for stable networking and HTTPS certificates, and Caddy https://caddyserver.com as a reverse proxy — no custom IPs, no random URLs, works on any network. 证据：`mobile-testing.md`\n- **Init Prompt**（documentation）：Generate a file named AGENTS.md that serves as a contributor guide for this repository. Your goal is to produce a clear, concise, and well-structured document with descriptive headings and actionable explanations for each section. Follow the outline below, but adapt as needed — add sections if relevant, and omit those that do not apply to this project. 证据：`crates/executors/src/executors/codex/init_prompt.md`\n- **Config**（structured_config）：{ \"theme\": \"light\", \"executor\": { \"type\": \"claude\" }, \"disclaimer acknowledged\": true, \"onboarding acknowledged\": true, \"sound alerts\": true, \"sound file\": \"abstract-sound4\", \"push notifications\": true, \"editor\": { \"editor type\": \"VS CODE\", \"custom command\": null }, \"github\": { \"token\": \"\", \"default pr base\": \"main\" } } 证据：`dev_assets_seed/config.json`\n- **Docs**（structured_config）：{ \"$schema\": \"https://mintlify.com/docs.json\", \"theme\": \"mint\", \"name\": \"Vibe Kanban\", \"description\": \"A kanban board for developers to track coding tasks with AI coding agents\", \"appearance\": { \"default\": \"light\" }, \"colors\": { \"primary\": \" 000000\", \"light\": \" fefefe\", \"dark\": \" 121212\" }, \"background\": { \"color\": { \"light\": \" FAF9F5\", \"dark\": \" 2F2F2D\" } }, \"favicon\": \"/logo/v-192.png\", \"navigation\": { \"groups\": { \"group\": \"Getting started\", \"pages\": \"index\", \"getting-started\", \"browser-testing\", \"issue-management\", \"reviewing-code\", \"remote-access\", { \"group\": \"Supported Coding Agents\", \"expanded\": true, \"pages\": \"supported-coding-agents\", \"agents/claude-code\", \"agents/openai-codex\", \"ag… 证据：`docs/docs.json`\n- **Tsconfig**（structured_config）：{ \"compilerOptions\": { \"target\": \"ES2020\", \"module\": \"ESNext\", \"moduleResolution\": \"bundler\", \"strict\": true, \"noUnusedLocals\": true, \"noUnusedParameters\": true, \"resolveJsonModule\": true, \"skipLibCheck\": true, \"noEmit\": true, \"types\": \"node\" }, \"include\": \"src\" } 证据：`npx-cli/tsconfig.json`\n- **Query 039C2290B6Cf7Cdc905C8Ddc44293F067Fe7E8F246Da737E4Baad3F494Ac8B8F**（structured_config）：{ \"db name\": \"SQLite\", \"query\": \"INSERT INTO execution processes \\n id, session id, run reason, executor action,\\n status, exit code, started at, completed at, created at, updated at\\n VALUES ?, ?, ?, ?, ?, ?, ?, ?, ?, ? \", \"describe\": { \"columns\": , \"parameters\": { \"Right\": 10 }, \"nullable\": }, \"hash\": \"039c2290b6cf7cdc905c8ddc44293f067fe7e8f246da737e4baad3f494ac8b8f\" } 证据：`crates/db/.sqlx/query-039c2290b6cf7cdc905c8ddc44293f067fe7e8f246da737e4baad3f494ac8b8f.json`\n- **Query 04C207Be2C3C2C07Ff42C695542504C358D67C1F40Ca2B1E75A396A90C173A53**（structured_config）：{ \"db name\": \"SQLite\", \"query\": \"SELECT eprs.after head commit\\n FROM execution process repo states eprs\\n JOIN execution processes ep ON ep.id = eprs.execution process id\\n WHERE ep.session id = $1\\n AND eprs.repo id = $2\\n AND ep.created at < SELECT created at FROM execution processes WHERE id = $3 \\n ORDER BY ep.created at DESC\\n LIMIT 1\", \"describe\": { \"columns\": { \"name\": \"after head commit\", \"ordinal\": 0, \"type info\": \"Text\" } , \"parameters\": { \"Right\": 3 }, \"nullable\": true }, \"hash\": \"04c207be2c3c2c07ff42c695542504c358d67c1f40ca2b1e75a396a90c173a53\" } 证据：`crates/db/.sqlx/query-04c207be2c3c2c07ff42c695542504c358d67c1f40ca2b1e75a396a90c173a53.json`\n- **Query 04F17449E3E12785Affab91E4Eab308103491E34C022199B7B060E04Fa8Aed0F**（structured_config）：{ \"db name\": \"SQLite\", \"query\": \"SELECT id as \\\"id!: Uuid\\\",\\n file path as \\\"file path!\\\",\\n original name as \\\"original name!\\\",\\n mime type,\\n size bytes as \\\"size bytes!\\\",\\n hash as \\\"hash!\\\",\\n created at as \\\"created at!: DateTime \\\",\\n updated at as \\\"updated at!: DateTime \\\"\\n FROM attachments\\n WHERE hash = $1\", \"describe\": { \"columns\": { \"name\": \"id!: Uuid\", \"ordinal\": 0, \"type info\": \"Blob\" }, { \"name\": \"file path!\", \"ordinal\": 1, \"type info\": \"Text\" }, { \"name\": \"original name!\", \"ordinal\": 2, \"type info\": \"Text\" }, { \"name\": \"mime type\", \"ordinal\": 3, \"type info\": \"Text\" }, { \"name\": \"size bytes!\", \"ordinal\": 4, \"type info\": \"Integer\" }, { \"name\": \"hash!\", \"ordinal\": 5, \"type… 证据：`crates/db/.sqlx/query-04f17449e3e12785affab91e4eab308103491e34c022199b7b060e04fa8aed0f.json`\n- **Query 0Ab07Fb562E61148F3F07F33F766Ea12C73D467Df4522240008370F681C8409A**（structured_config）：{ \"db name\": \"SQLite\", \"query\": \"UPDATE workspace repos\\n SET target branch = $1, updated at = datetime 'now' \\n WHERE target branch = $2\\n AND workspace id IN \\n SELECT w.id FROM workspaces w\\n JOIN tasks t ON w.task id = t.id\\n WHERE t.parent workspace id = $3\\n \", \"describe\": { \"columns\": , \"parameters\": { \"Right\": 3 }, \"nullable\": }, \"hash\": \"0ab07fb562e61148f3f07f33f766ea12c73d467df4522240008370f681c8409a\" } 证据：`crates/db/.sqlx/query-0ab07fb562e61148f3f07f33f766ea12c73d467df4522240008370f681c8409a.json`\n- **Query 0C7B20643F119Afd3E233105B0Fa2920E8E940Bdad86Cdc95D01E485A20D6Ed4**（structured_config）：{ \"db name\": \"SQLite\", \"query\": \"SELECT\\n ep.id as \\\"id!: Uuid\\\",\\n ep.session id as \\\"session id!: Uuid\\\",\\n ep.run reason as \\\"run reason!: ExecutionProcessRunReason\\\",\\n ep.executor action as \\\"executor action!: sqlx::types::Json \\\",\\n ep.status as \\\"status!: ExecutionProcessStatus\\\",\\n ep.exit code,\\n ep.dropped as \\\"dropped!: bool\\\",\\n ep.started at as \\\"started at!: DateTime \\\",\\n ep.completed at as \\\"completed at?: DateTime \\\",\\n ep.created at as \\\"created at!: DateTime \\\",\\n ep.updated at as \\\"updated at!: DateTime \\\"\\n FROM execution processes ep\\n JOIN sessions s ON ep.session id = s.id\\n WHERE s.workspace id = ? AND ep.run reason = ? AND ep.dropped = FALSE\\n ORDER BY ep.created a… 证据：`crates/db/.sqlx/query-0c7b20643f119afd3e233105b0fa2920e8e940bdad86cdc95d01e485a20d6ed4.json`\n- **Query 0Ee24D51E7557D9D6C9418A06156C03D7Dd49Dfe938194Cd6951942Dfd8F179D**（structured_config）：{ \"db name\": \"SQLite\", \"query\": \"DELETE FROM pull requests WHERE id = ?\", \"describe\": { \"columns\": , \"parameters\": { \"Right\": 1 }, \"nullable\": }, \"hash\": \"0ee24d51e7557d9d6c9418a06156c03d7dd49dfe938194cd6951942dfd8f179d\" } 证据：`crates/db/.sqlx/query-0ee24d51e7557d9d6c9418a06156c03d7dd49dfe938194cd6951942dfd8f179d.json`\n- **Query 11793C98A4Bee67Fce9972Ed6B10A18226E0455A0E8D113D04C4D5148B72Aec7**（structured_config）：{ \"db name\": \"SQLite\", \"query\": \"SELECT id as \\\"id!: Uuid\\\", tag name, content as \\\"content!\\\", created at as \\\"created at!: DateTime \\\", updated at as \\\"updated at!: DateTime \\\"\\n FROM tags\\n WHERE id = $1\", \"describe\": { \"columns\": { \"name\": \"id!: Uuid\", \"ordinal\": 0, \"type info\": \"Blob\" }, { \"name\": \"tag name\", \"ordinal\": 1, \"type info\": \"Text\" }, { \"name\": \"content!\", \"ordinal\": 2, \"type info\": \"Text\" }, { \"name\": \"created at!: DateTime \", \"ordinal\": 3, \"type info\": \"Text\" }, { \"name\": \"updated at!: DateTime \", \"ordinal\": 4, \"type info\": \"Text\" } , \"parameters\": { \"Right\": 1 }, \"nullable\": true, false, false, false, false }, \"hash\": \"11793c98a4bee67fce9972ed6b10a18226e0455a0e8d113d04c4d… 证据：`crates/db/.sqlx/query-11793c98a4bee67fce9972ed6b10a18226e0455a0e8d113d04c4d5148b72aec7.json`\n- **Query 12A5C0A8B95D8Cb87F1C869Ff35692A2Cee52Bc418B06D00A31A4C139E12D18A**（structured_config）：{ \"db name\": \"SQLite\", \"query\": \"\\n SELECT \\n ep.id as \\\"execution id!: Uuid\\\", \\n ep.session id as \\\"session id!: Uuid\\\"\\n FROM execution processes ep\\n WHERE EXISTS \\n SELECT 1 FROM execution process logs epl WHERE epl.execution id = ep.id\\n \\n \", \"describe\": { \"columns\": { \"name\": \"execution id!: Uuid\", \"ordinal\": 0, \"type info\": \"Blob\" }, { \"name\": \"session id!: Uuid\", \"ordinal\": 1, \"type info\": \"Blob\" } , \"parameters\": { \"Right\": 0 }, \"nullable\": true, false }, \"hash\": \"12a5c0a8b95d8cb87f1c869ff35692a2cee52bc418b06d00a31a4c139e12d18a\" } 证据：`crates/db/.sqlx/query-12a5c0a8b95d8cb87f1c869ff35692a2cee52bc418b06d00a31a4c139e12d18a.json`\n- **Query 13826Fc6Fdd367255Cb921640E5972F30905Ac7A81Ad477Cf8Bbcfc24F06F39B**（structured_config）：{ \"db name\": \"SQLite\", \"query\": \"\\n SELECT\\n ep.id as \\\"id!: Uuid\\\",\\n ep.session id as \\\"session id!: Uuid\\\",\\n ep.run reason as \\\"run reason!: ExecutionProcessRunReason\\\",\\n ep.executor action as \\\"executor action!: sqlx::types::Json \\\",\\n ep.status as \\\"status!: ExecutionProcessStatus\\\",\\n ep.exit code,\\n ep.dropped as \\\"dropped!: bool\\\",\\n ep.started at as \\\"started at!: DateTime \\\",\\n ep.completed at as \\\"completed at?: DateTime \\\",\\n ep.created at as \\\"created at!: DateTime \\\",\\n ep.updated at as \\\"updated at!: DateTime \\\"\\n FROM execution processes ep\\n JOIN sessions s ON ep.session id = s.id\\n WHERE s.workspace id = ?\\n AND ep.status = 'running'\\n AND ep.run reason = 'devserver'\\n O… 证据：`crates/db/.sqlx/query-13826fc6fdd367255cb921640e5972f30905ac7a81ad477cf8bbcfc24f06f39b.json`\n- **Query 1Af7A606A64D9662D6Edc4Fbeaae0D53A4D657A6E29B2561E820085A2D9E3348**（structured_config）：{ \"db name\": \"SQLite\", \"query\": \"SELECT\\n id,\\n workspace id AS \\\"workspace id: Uuid\\\",\\n repo id AS \\\"repo id: Uuid\\\",\\n pr url,\\n pr number,\\n pr status AS \\\"pr status: MergeStatus\\\",\\n target branch name,\\n merged at AS \\\"merged at: DateTime \\\",\\n merge commit sha,\\n created at AS \\\"created at!: DateTime \\\",\\n updated at AS \\\"updated at!: DateTime \\\",\\n synced at AS \\\"synced at: DateTime \\\"\\n FROM pull requests\\n WHERE synced at IS NULL OR synced at \", \"ordinal\": 7, \"type info\": \"Text\" }, { \"name\": \"merge commit sha\", \"ordinal\": 8, \"type info\": \"Text\" }, { \"name\": \"created at!: DateTime \", \"ordinal\": 9, \"type info\": \"Datetime\" }, { \"name\": \"updated at!: DateTime \", \"ordinal\": 10, \"type i… 证据：`crates/db/.sqlx/query-1af7a606a64d9662d6edc4fbeaae0d53a4d657a6e29b2561e820085a2d9e3348.json`\n- **Query 1B186Dc075846Fc1F7270A942Afbf82A88806Ee6Ababdb437Ab5E97Ddd2122Da**（structured_config）：{ \"db name\": \"SQLite\", \"query\": \"SELECT COUNT as \\\"count!: i64\\\"\\n FROM execution processes ep\\n WHERE ep.session id = $1\\n AND ep.status = 'running'\\n AND ep.run reason = 'codingagent'\", \"describe\": { \"columns\": { \"name\": \"count!: i64\", \"ordinal\": 0, \"type info\": \"Integer\" } , \"parameters\": { \"Right\": 1 }, \"nullable\": false }, \"hash\": \"1b186dc075846fc1f7270a942afbf82a88806ee6ababdb437ab5e97ddd2122da\" } 证据：`crates/db/.sqlx/query-1b186dc075846fc1f7270a942afbf82a88806ee6ababdb437ab5e97ddd2122da.json`\n- **Query 1C2201B0Ca9305283634Fe5C72Df6Eac3Ad954C1238088A84A4B9085B1Dbdb74**（structured_config）：{ \"db name\": \"SQLite\", \"query\": \"DELETE FROM workspaces WHERE id = $1\", \"describe\": { \"columns\": , \"parameters\": { \"Right\": 1 }, \"nullable\": }, \"hash\": \"1c2201b0ca9305283634fe5c72df6eac3ad954c1238088a84a4b9085b1dbdb74\" } 证据：`crates/db/.sqlx/query-1c2201b0ca9305283634fe5c72df6eac3ad954c1238088a84a4b9085b1dbdb74.json`\n- **Query 218F1D14C72148Ea88D75E816E1Ba111C8F4678A7E428B15462E6Dfc74C25B03**（structured_config）：{ \"db name\": \"SQLite\", \"query\": \"UPDATE tags\\n SET tag name = $2, content = $3, updated at = datetime 'now', 'subsec' \\n WHERE id = $1\\n RETURNING id as \\\"id!: Uuid\\\", tag name, content as \\\"content!\\\", created at as \\\"created at!: DateTime \\\", updated at as \\\"updated at!: DateTime \\\"\", \"describe\": { \"columns\": { \"name\": \"id!: Uuid\", \"ordinal\": 0, \"type info\": \"Blob\" }, { \"name\": \"tag name\", \"ordinal\": 1, \"type info\": \"Text\" }, { \"name\": \"content!\", \"ordinal\": 2, \"type info\": \"Text\" }, { \"name\": \"created at!: DateTime \", \"ordinal\": 3, \"type info\": \"Text\" }, { \"name\": \"updated at!: DateTime \", \"ordinal\": 4, \"type info\": \"Text\" } , \"parameters\": { \"Right\": 3 }, \"nullable\": true, false, false,… 证据：`crates/db/.sqlx/query-218f1d14c72148ea88d75e816e1ba111c8f4678a7e428b15462e6dfc74c25b03.json`\n- **Query 21C7A9F62322212A5F6B923Bb410C25Ac06E6A0C857D910D93Fb80Ab77Fc9B35**（structured_config）：{ \"db name\": \"SQLite\", \"query\": \"SELECT COUNT 1 AS \\\"count!: i64\\\" FROM pull requests WHERE workspace id = ? AND pr status = 'open'\", \"describe\": { \"columns\": { \"name\": \"count!: i64\", \"ordinal\": 0, \"type info\": \"Integer\" } , \"parameters\": { \"Right\": 1 }, \"nullable\": false }, \"hash\": \"21c7a9f62322212a5f6b923bb410c25ac06e6a0c857d910d93fb80ab77fc9b35\" } 证据：`crates/db/.sqlx/query-21c7a9f62322212a5f6b923bb410c25ac06e6a0c857d910d93fb80ab77fc9b35.json`\n- **Query 2547A5D06Fd3B17360Bff34A04B7D3D929C13Ef0D86395A9201834D8Fc955295**（structured_config）：{ \"db name\": \"SQLite\", \"query\": \"SELECT\\n cat.agent session id as \\\"session id!\\\",\\n cat.agent message id as \\\"message id\\\"\\n FROM execution processes ep\\n JOIN coding agent turns cat ON ep.id = cat.execution process id\\n WHERE ep.session id = $1\\n AND ep.run reason = 'codingagent'\\n AND ep.dropped = FALSE\\n AND cat.agent session id IS NOT NULL\\n ORDER BY ep.created at DESC\\n LIMIT 1\", \"describe\": { \"columns\": { \"name\": \"session id!\", \"ordinal\": 0, \"type info\": \"Text\" }, { \"name\": \"message id\", \"ordinal\": 1, \"type info\": \"Text\" } , \"parameters\": { \"Right\": 1 }, \"nullable\": true, true }, \"hash\": \"2547a5d06fd3b17360bff34a04b7d3d929c13ef0d86395a9201834d8fc955295\" } 证据：`crates/db/.sqlx/query-2547a5d06fd3b17360bff34a04b7d3d929c13ef0d86395a9201834d8fc955295.json`\n- **Query 256F9E937384933464E6D4D00Ee977Bbb2915Ef80930C8B5C0B0525367A5264D**（structured_config）：{ \"db name\": \"SQLite\", \"query\": \"UPDATE repos SET name = $1, display name = $2, updated at = datetime 'now', 'subsec' WHERE id = $3\", \"describe\": { \"columns\": , \"parameters\": { \"Right\": 3 }, \"nullable\": }, \"hash\": \"256f9e937384933464e6d4d00ee977bbb2915ef80930c8b5c0b0525367a5264d\" } 证据：`crates/db/.sqlx/query-256f9e937384933464e6d4d00ee977bbb2915ef80930c8b5c0b0525367a5264d.json`\n- **Query 2948Ec0606A39Ee67Bdbaf4F2Cf82592448A1D91A66D7D89Cf7204F71F706274**（structured_config）：{ \"db name\": \"SQLite\", \"query\": \"UPDATE pull requests SET pr status = ?, merged at = ?, merge commit sha = ?, updated at = ?, synced at = NULL WHERE pr url = ?\", \"describe\": { \"columns\": , \"parameters\": { \"Right\": 5 }, \"nullable\": }, \"hash\": \"2948ec0606a39ee67bdbaf4f2cf82592448a1d91a66d7d89cf7204f71f706274\" } 证据：`crates/db/.sqlx/query-2948ec0606a39ee67bdbaf4f2cf82592448a1d91a66d7d89cf7204f71f706274.json`\n- **Query 2A57B702E52B3Cc9Bdbc361267985958B11D4493B01A9Ab8Daedf5D951422897**（structured_config）：{ \"db name\": \"SQLite\", \"query\": \"UPDATE workspaces SET updated at = datetime 'now', 'subsec' WHERE id = ?\", \"describe\": { \"columns\": , \"parameters\": { \"Right\": 1 }, \"nullable\": }, \"hash\": \"2a57b702e52b3cc9bdbc361267985958b11d4493b01a9ab8daedf5d951422897\" } 证据：`crates/db/.sqlx/query-2a57b702e52b3cc9bdbc361267985958b11d4493b01a9ab8daedf5d951422897.json`\n- **Query 2B253F92Ac5Daa4864E7335Fde1B82625F504Fd73D19B21992497219A9C3170A**（structured_config）：{ \"db name\": \"SQLite\", \"query\": \"INSERT INTO repos id, path, name, display name \\n VALUES $1, $2, $3, $4 \\n ON CONFLICT path DO UPDATE SET updated at = updated at\\n RETURNING id as \\\"id!: Uuid\\\",\\n path,\\n name,\\n display name,\\n setup script,\\n cleanup script,\\n archive script,\\n copy files,\\n parallel setup script as \\\"parallel setup script!: bool\\\",\\n dev server script,\\n default target branch,\\n default working dir,\\n created at as \\\"created at!: DateTime \\\",\\n updated at as \\\"updated at!: DateTime \\\"\", \"describe\": { \"columns\": { \"name\": \"id!: Uuid\", \"ordinal\": 0, \"type info\": \"Blob\" }, { \"name\": \"path\", \"ordinal\": 1, \"type info\": \"Text\" }, { \"name\": \"name\", \"ordinal\": 2, \"type info\": \"… 证据：`crates/db/.sqlx/query-2b253f92ac5daa4864e7335fde1b82625f504fd73d19b21992497219a9c3170a.json`\n- **Query 2C0172D5B2C5Bff0914727A57983D5C336F5B2Dfa73Ca6C2Efa4Ea23Bb526E05**（structured_config）：{ \"db name\": \"SQLite\", \"query\": \"SELECT id as \\\"id!: Uuid\\\",\\n name,\\n default agent working dir,\\n remote project id as \\\"remote project id: Uuid\\\",\\n created at as \\\"created at!: DateTime \\\",\\n updated at as \\\"updated at!: DateTime \\\"\\n FROM projects\\n ORDER BY created at DESC\", \"describe\": { \"columns\": { \"name\": \"id!: Uuid\", \"ordinal\": 0, \"type info\": \"Blob\" }, { \"name\": \"name\", \"ordinal\": 1, \"type info\": \"Text\" }, { \"name\": \"default agent working dir\", \"ordinal\": 2, \"type info\": \"Text\" }, { \"name\": \"remote project id: Uuid\", \"ordinal\": 3, \"type info\": \"Blob\" }, { \"name\": \"created at!: DateTime \", \"ordinal\": 4, \"type info\": \"Text\" }, { \"name\": \"updated at!: DateTime \", \"ordinal\": 5, \"typ… 证据：`crates/db/.sqlx/query-2c0172d5b2c5bff0914727a57983d5c336f5b2dfa73ca6c2efa4ea23bb526e05.json`\n- **Query 2C71Bf4Dd5683E0Dedf2341E52880Ff2C0765659D3Cf53D62Faa54Adc91071Dd**（structured_config）：{ \"db name\": \"SQLite\", \"query\": \"SELECT w.name AS \\\"name: String\\\"\\n FROM workspaces w\\n JOIN workspace repos wr ON wr.workspace id = w.id\\n WHERE wr.repo id = $1\\n AND w.archived = FALSE\", \"describe\": { \"columns\": { \"name\": \"name: String\", \"ordinal\": 0, \"type info\": \"Text\" } , \"parameters\": { \"Right\": 1 }, \"nullable\": true }, \"hash\": \"2c71bf4dd5683e0dedf2341e52880ff2c0765659d3cf53d62faa54adc91071dd\" } 证据：`crates/db/.sqlx/query-2c71bf4dd5683e0dedf2341e52880ff2c0765659d3cf53d62faa54adc91071dd.json`\n- **Query 2Cb5A269045F23Da9F4Ee0Ee679Ccb7Fffc39D4B37B1B58357B11A7Abfdba125**（structured_config）：{ \"db name\": \"SQLite\", \"query\": \"UPDATE sessions SET executor = $1, updated at = CURRENT TIMESTAMP WHERE id = $2\", \"describe\": { \"columns\": , \"parameters\": { \"Right\": 2 }, \"nullable\": }, \"hash\": \"2cb5a269045f23da9f4ee0ee679ccb7fffc39d4b37b1b58357b11a7abfdba125\" } 证据：`crates/db/.sqlx/query-2cb5a269045f23da9f4ee0ee679ccb7fffc39d4b37b1b58357b11a7abfdba125.json`\n- **Query 31F4E685Fc0B1103Ff662B3866B3Bb422Cc7Fc8E0661Ebfed30Ffd16Ea7Ed8C0**（structured_config）：{ \"db name\": \"SQLite\", \"query\": \"SELECT id as \\\"id!: Uuid\\\",\\n workspace id as \\\"workspace id!: Uuid\\\",\\n repo id as \\\"repo id!: Uuid\\\",\\n target branch,\\n created at as \\\"created at!: DateTime \\\",\\n updated at as \\\"updated at!: DateTime \\\"\\n FROM workspace repos\\n WHERE workspace id = $1\", \"describe\": { \"columns\": { \"name\": \"id!: Uuid\", \"ordinal\": 0, \"type info\": \"Blob\" }, { \"name\": \"workspace id!: Uuid\", \"ordinal\": 1, \"type info\": \"Blob\" }, { \"name\": \"repo id!: Uuid\", \"ordinal\": 2, \"type info\": \"Blob\" }, { \"name\": \"target branch\", \"ordinal\": 3, \"type info\": \"Text\" }, { \"name\": \"created at!: DateTime \", \"ordinal\": 4, \"type info\": \"Text\" }, { \"name\": \"updated at!: DateTime \", \"ordinal\": 5,… 证据：`crates/db/.sqlx/query-31f4e685fc0b1103ff662b3866b3bb422cc7fc8e0661ebfed30ffd16ea7ed8c0.json`\n- **Query 3266B6A544952177F84E2E7C31Be9Dba212C92D91B997De7F6Aa811E08Ed6C72**（structured_config）：{ \"db name\": \"SQLite\", \"query\": \"SELECT\\n ep.id as \\\"id!: Uuid\\\",\\n ep.session id as \\\"session id!: Uuid\\\",\\n ep.run reason as \\\"run reason!: ExecutionProcessRunReason\\\",\\n ep.executor action as \\\"executor action!: sqlx::types::Json \\\",\\n ep.status as \\\"status!: ExecutionProcessStatus\\\",\\n ep.exit code,\\n ep.dropped as \\\"dropped!: bool\\\",\\n ep.started at as \\\"started at!: DateTime \\\",\\n ep.completed at as \\\"completed at?: DateTime \\\",\\n ep.created at as \\\"created at!: DateTime \\\",\\n ep.updated at as \\\"updated at!: DateTime \\\"\\n FROM execution processes ep\\n WHERE ep.session id = ? AND ep.run reason = ? AND ep.dropped = FALSE\\n ORDER BY ep.created at DESC LIMIT 1\", \"describe\": { \"columns\": {… 证据：`crates/db/.sqlx/query-3266b6a544952177f84e2e7c31be9dba212c92d91b997de7f6aa811e08ed6c72.json`\n- **Query 32C74A54Fdd72A6B167583228F2C30944837B7Cc29C9Cc4Acfbb4F047Cea7118**（structured_config）：{ \"db name\": \"SQLite\", \"query\": \"SELECT\\n id,\\n workspace id AS \\\"workspace id: Uuid\\\",\\n repo id AS \\\"repo id: Uuid\\\",\\n pr url,\\n pr number,\\n pr status AS \\\"pr status: MergeStatus\\\",\\n target branch name,\\n merged at AS \\\"merged at: DateTime \\\",\\n merge commit sha,\\n created at AS \\\"created at!: DateTime \\\",\\n updated at AS \\\"updated at!: DateTime \\\",\\n synced at AS \\\"synced at: DateTime \\\"\\n FROM pull requests\\n WHERE workspace id = $1 AND repo id = $2\\n ORDER BY created at DESC\", \"describe\": { \"columns\": { \"name\": \"id\", \"ordinal\": 0, \"type info\": \"Text\" }, { \"name\": \"workspace id: Uuid\", \"ordinal\": 1, \"type info\": \"Blob\" }, { \"name\": \"repo id: Uuid\", \"ordinal\": 2, \"type info\": \"Blob\" }… 证据：`crates/db/.sqlx/query-32c74a54fdd72a6b167583228f2c30944837b7cc29c9cc4acfbb4f047cea7118.json`\n- **Query 3634E2Bab8Fef106721Bb64A791Edd81D3D49Eb34Fbabd34E4Feadfb5F229A6E**（structured_config）：{ \"db name\": \"SQLite\", \"query\": \"SELECT id as \\\"id!: Uuid\\\",\\n container ref as \\\"container ref!\\\"\\n FROM workspaces\\n WHERE container ref IS NOT NULL\", \"describe\": { \"columns\": { \"name\": \"id!: Uuid\", \"ordinal\": 0, \"type info\": \"Blob\" }, { \"name\": \"container ref!\", \"ordinal\": 1, \"type info\": \"Text\" } , \"parameters\": { \"Right\": 0 }, \"nullable\": true, true }, \"hash\": \"3634e2bab8fef106721bb64a791edd81d3d49eb34fbabd34e4feadfb5f229a6e\" } 证据：`crates/db/.sqlx/query-3634e2bab8fef106721bb64a791edd81d3d49eb34fbabd34e4feadfb5f229a6e.json`\n- **Query 3A9148E9E914D644D4D82A1C2Dc8Bd0E093D4F4C638Afa7Fd8F5211892Fb6D84**（structured_config）：{ \"db name\": \"SQLite\", \"query\": \"DELETE FROM repos WHERE id = $1\", \"describe\": { \"columns\": , \"parameters\": { \"Right\": 1 }, \"nullable\": }, \"hash\": \"3a9148e9e914d644d4d82a1c2dc8bd0e093d4f4c638afa7fd8f5211892fb6d84\" } 证据：`crates/db/.sqlx/query-3a9148e9e914d644d4d82a1c2dc8bd0e093d4f4c638afa7fd8f5211892fb6d84.json`\n- **Query 3D34580933Bc02A168F4A7C483460A6Ad13Ef72B508532F5A6Cd5E53Aff04A69**（structured_config）：{ \"db name\": \"SQLite\", \"query\": \"\\n SELECT\\n workspace id as \\\"workspace id!: Uuid\\\",\\n execution process id as \\\"execution process id!: Uuid\\\",\\n session id as \\\"session id!: Uuid\\\",\\n status as \\\"status!: ExecutionProcessStatus\\\",\\n completed at as \\\"completed at?: DateTime \\\"\\n FROM \\n SELECT\\n s.workspace id,\\n ep.id as execution process id,\\n ep.session id,\\n ep.status,\\n ep.completed at,\\n ROW NUMBER OVER \\n PARTITION BY s.workspace id\\n ORDER BY ep.created at DESC\\n as rn\\n FROM execution processes ep\\n JOIN sessions s ON ep.session id = s.id\\n JOIN workspaces w ON s.workspace id = w.id\\n WHERE w.archived = $1\\n AND ep.run reason IN 'codingagent', 'setupscript', 'cleanupscript' \\n AN… 证据：`crates/db/.sqlx/query-3d34580933bc02a168f4a7c483460a6ad13ef72b508532f5a6cd5e53aff04a69.json`\n- **Query 3F4B2179Dcd8857Fc18F1E5F6E6Cf10F152Eebbb141B2D3604Dd4191E0C2F367**（structured_config）：{ \"db name\": \"SQLite\", \"query\": \"SELECT\\n ep.id as \\\"id!: Uuid\\\",\\n ep.session id as \\\"session id!: Uuid\\\",\\n ep.run reason as \\\"run reason!: ExecutionProcessRunReason\\\",\\n ep.executor action as \\\"executor action!: sqlx::types::Json \\\",\\n ep.status as \\\"status!: ExecutionProcessStatus\\\",\\n ep.exit code,\\n ep.dropped as \\\"dropped!: bool\\\",\\n ep.started at as \\\"started at!: DateTime \\\",\\n ep.completed at as \\\"completed at?: DateTime \\\",\\n ep.created at as \\\"created at!: DateTime \\\",\\n ep.updated at as \\\"updated at!: DateTime \\\"\\n FROM execution processes ep WHERE ep.id = ?\", \"describe\": { \"columns\": { \"name\": \"id!: Uuid\", \"ordinal\": 0, \"type info\": \"Blob\" }, { \"name\": \"session id!: Uuid\", \"or… 证据：`crates/db/.sqlx/query-3f4b2179dcd8857fc18f1e5f6e6cf10f152eebbb141b2d3604dd4191e0c2f367.json`\n- **Query 420A0C490F1E4D549Fb194265E971D8C03B86Fe75B595091F6425De11D120A6B**（structured_config）：{ \"db name\": \"SQLite\", \"query\": \"UPDATE execution processes\\n SET dropped = TRUE\\n WHERE session id = $1\\n AND created at = SELECT created at FROM execution processes WHERE id = $2 \\n AND dropped = FALSE\", \"describe\": { \"columns\": , \"parameters\": { \"Right\": 2 }, \"nullable\": }, \"hash\": \"420a0c490f1e4d549fb194265e971d8c03b86fe75b595091f6425de11d120a6b\" } 证据：`crates/db/.sqlx/query-420a0c490f1e4d549fb194265e971d8c03b86fe75b595091f6425de11d120a6b.json`\n- **Query 4506Eeeb85B49F00143A9D23636C976159E1C72C9Cfce005599C5Eb52Dc15095**（structured_config）：{ \"db name\": \"SQLite\", \"query\": \"SELECT s.id AS \\\"id!: Uuid\\\",\\n s.workspace id AS \\\"workspace id!: Uuid\\\",\\n s.name,\\n s.executor,\\n s.agent working dir,\\n s.created at AS \\\"created at!: DateTime \\\",\\n s.updated at AS \\\"updated at!: DateTime \\\"\\n FROM sessions s\\n LEFT JOIN \\n SELECT ep.session id, MAX ep.created at as last used\\n FROM execution processes ep\\n WHERE ep.run reason != 'devserver' AND ep.dropped = FALSE\\n GROUP BY ep.session id\\n latest ep ON s.id = latest ep.session id\\n WHERE s.workspace id = $1\\n ORDER BY COALESCE latest ep.last used, s.created at DESC\", \"describe\": { \"columns\": { \"name\": \"id!: Uuid\", \"ordinal\": 0, \"type info\": \"Blob\" }, { \"name\": \"workspace id!: Uuid\", \"o… 证据：`crates/db/.sqlx/query-4506eeeb85b49f00143a9d23636c976159e1c72c9cfce005599c5eb52dc15095.json`\n- **Query 48C556A5317E6Ea77595A8Fdc410D30Df50C8405Adf38B371Fdf0A1Bde8C0083**（structured_config）：{ \"db name\": \"SQLite\", \"query\": \"UPDATE execution process repo states\\n SET before head commit = $1, updated at = $2\\n WHERE execution process id = $3\\n AND repo id = $4\", \"describe\": { \"columns\": , \"parameters\": { \"Right\": 4 }, \"nullable\": }, \"hash\": \"48c556a5317e6ea77595a8fdc410d30df50c8405adf38b371fdf0a1bde8c0083\" } 证据：`crates/db/.sqlx/query-48c556a5317e6ea77595a8fdc410d30df50c8405adf38b371fdf0a1bde8c0083.json`\n- **Query 4Ac35216Ead7E5Be9Cc2De504A06B6E375E23Ca2Ed14493Ec991F53E458A6A34**（structured_config）：{ \"db name\": \"SQLite\", \"query\": \"DELETE FROM attachments WHERE id = $1\", \"describe\": { \"columns\": , \"parameters\": { \"Right\": 1 }, \"nullable\": }, \"hash\": \"4ac35216ead7e5be9cc2de504a06b6e375e23ca2ed14493ec991f53e458a6a34\" } 证据：`crates/db/.sqlx/query-4ac35216ead7e5be9cc2de504a06b6e375e23ca2ed14493ec991f53e458a6a34.json`\n- **Query 4B952Fb779Fbcf70Bd402B6Bcc0Eec07B75879333614B8Ef98E5B8073Ad66Ca6**（structured_config）：{ \"db name\": \"SQLite\", \"query\": \"INSERT INTO attachments id, file path, original name, mime type, size bytes, hash \\n VALUES $1, $2, $3, $4, $5, $6 \\n RETURNING id as \\\"id!: Uuid\\\", \\n file path as \\\"file path!\\\", \\n original name as \\\"original name!\\\", \\n mime type,\\n size bytes as \\\"size bytes!\\\",\\n hash as \\\"hash!\\\",\\n created at as \\\"created at!: DateTime \\\", \\n updated at as \\\"updated at!: DateTime \\\"\", \"describe\": { \"columns\": { \"name\": \"id!: Uuid\", \"ordinal\": 0, \"type info\": \"Blob\" }, { \"name\": \"file path!\", \"ordinal\": 1, \"type info\": \"Text\" }, { \"name\": \"original name!\", \"ordinal\": 2, \"type info\": \"Text\" }, { \"name\": \"mime type\", \"ordinal\": 3, \"type info\": \"Text\" }, { \"name\": \"size… 证据：`crates/db/.sqlx/query-4b952fb779fbcf70bd402b6bcc0eec07b75879333614b8ef98e5b8073ad66ca6.json`\n- **Query 4C9B1B539Ec383Ace94Ef29C58967Bbf08112Ebdc61276E9710663A083318211**（structured_config）：{ \"db name\": \"SQLite\", \"query\": \"SELECT id as \\\"id!: Uuid\\\", project id as \\\"project id!: Uuid\\\", title, description, status as \\\"status!: TaskStatus\\\", parent workspace id as \\\"parent workspace id: Uuid\\\", created at as \\\"created at!: DateTime \\\", updated at as \\\"updated at!: DateTime \\\"\\n FROM tasks\\n ORDER BY created at ASC\", \"describe\": { \"columns\": { \"name\": \"id!: Uuid\", \"ordinal\": 0, \"type info\": \"Blob\" }, { \"name\": \"project id!: Uuid\", \"ordinal\": 1, \"type info\": \"Blob\" }, { \"name\": \"title\", \"ordinal\": 2, \"type info\": \"Text\" }, { \"name\": \"description\", \"ordinal\": 3, \"type info\": \"Text\" }, { \"name\": \"status!: TaskStatus\", \"ordinal\": 4, \"type info\": \"Text\" }, { \"name\": \"parent workspace… 证据：`crates/db/.sqlx/query-4c9b1b539ec383ace94ef29c58967bbf08112ebdc61276e9710663a083318211.json`\n- **Query 4D86Dcbf754F971Ff3Acffe9E85B5C2F455E77C40C624E09736Be9480238110B**（structured_config）：{ \"db name\": \"SQLite\", \"query\": \"UPDATE workspaces SET archived = $1, updated at = datetime 'now', 'subsec' WHERE id = $2\", \"describe\": { \"columns\": , \"parameters\": { \"Right\": 2 }, \"nullable\": }, \"hash\": \"4d86dcbf754f971ff3acffe9e85b5c2f455e77c40c624e09736be9480238110b\" } 证据：`crates/db/.sqlx/query-4d86dcbf754f971ff3acffe9e85b5c2f455e77c40c624e09736be9480238110b.json`\n- 其余 20 条证据见 `AI_CONTEXT_PACK.json` 或 `EVIDENCE_INDEX.json`。\n\n## 宿主 AI 必须遵守的规则\n\n- **把本资产当作开工前上下文，而不是运行环境。**：AI Context Pack 只包含证据化项目理解，不包含目标项目的可执行状态。 证据：`docs/AGENTS.md`, `docs/README.md`, `AGENTS.md`\n- **回答用户时区分可预览内容与必须安装后才能验证的内容。**：安装前体验的消费者价值来自降低误装和误判，而不是伪装成真实运行。 证据：`docs/AGENTS.md`, `docs/README.md`, `AGENTS.md`\n\n## 用户开工前应该回答的问题\n\n- 你准备在哪个宿主 AI 或本地环境中使用它？\n- 你只是想先体验工作流，还是准备真实安装？\n- 你最在意的是安装成本、输出质量、还是和现有规则的冲突？\n\n## 验收标准\n\n- 所有能力声明都能回指到 evidence_refs 中的文件路径。\n- AI_CONTEXT_PACK.md 没有把预览包装成真实运行。\n- 用户能在 3 分钟内看懂适合谁、能做什么、如何开始和风险边界。\n\n---\n\n## Doramagic Context Augmentation\n\n下面内容用于强化 Repomix/AI Context Pack 主体。Human Manual 只提供阅读骨架；踩坑日志会被转成宿主 AI 必须遵守的工作约束。\n\n## Human Manual 骨架\n\n使用规则：这里只是项目阅读路线和显著性信号，不是事实权威。具体事实仍必须回到 repo evidence / Claim Graph。\n\n宿主 AI 硬性规则：\n- 不得把页标题、章节顺序、摘要或 importance 当作项目事实证据。\n- 解释 Human Manual 骨架时，必须明确说它只是阅读路线/显著性信号。\n- 能力、安装、兼容性、运行状态和风险判断必须引用 repo evidence、source path 或 Claim Graph。\n\n- **Project Introduction**：importance `high`\n - source_paths: README.md, CLAUDE.md, AGENTS.md\n- **Key Concepts**：importance `high`\n - source_paths: crates/db/src/models/project.rs, crates/db/src/models/workspace.rs, crates/db/src/models/session.rs, crates/db/src/models/task.rs, crates/db/src/models/scratch.rs\n- **Development Setup**：importance `high`\n - source_paths: CONTRIBUTORS.md, local-build.sh, pnpm-workspace.yaml, rust-toolchain.toml\n- **Backend Architecture**：importance `high`\n - source_paths: crates/server/src/lib.rs, crates/server/src/main.rs, crates/server/src/routes/mod.rs, crates/server/src/startup.rs, crates/server/src/runtime/mod.rs\n- **Frontend Architecture**：importance `high`\n - source_paths: packages/local-web/src/routes/_app.tsx, packages/remote-web/src/app/entry/App.tsx, packages/web-core/src/shared/hooks/useActions.ts, packages/web-core/src/shared/providers/WorkspaceProvider.tsx, packages/ui/src/components/KanbanBoard.tsx\n- **Crate Reference**：importance `medium`\n - source_paths: crates/api-types/src/lib.rs, crates/db/src/lib.rs, crates/executors/src/lib.rs, crates/relay-tunnel/src/lib.rs, crates/mcp/src/lib.rs\n- **Coding Agent Executors**：importance `high`\n - source_paths: crates/executors/src/executors/mod.rs, crates/executors/src/executors/claude/mod.rs, crates/executors/src/executors/codex/mod.rs, crates/executors/src/executor_discovery.rs, crates/executors/src/profile.rs\n- **MCP Server Integration**：importance `medium`\n - source_paths: crates/mcp/src/lib.rs, crates/mcp/src/task_server/mod.rs, crates/mcp/src/task_server/handler.rs, crates/mcp/src/task_server/tools/mod.rs, crates/executors/src/mcp_config.rs\n\n## Repo Inspection Evidence / 源码检查证据\n\n- repo_clone_verified: true\n- repo_inspection_verified: true\n- repo_commit: `4deb7eca8f381f7cbc1f9d15515a9ab8f8009053`\n- inspected_files: `pnpm-lock.yaml`, `Dockerfile`, `package.json`, `README.md`, `docs/AGENTS.md`, `docs/troubleshooting.mdx`, `docs/browser-testing.mdx`, `docs/reviewing-code.mdx`, `docs/issue-management.mdx`, `docs/getting-started.mdx`, `docs/CLAUDE.md`, `docs/supported-coding-agents.mdx`, `docs/index.mdx`, `docs/README.md`, `docs/docs.json`, `docs/frontend-ui-library-refactor-audit.md`, `docs/remote-access.mdx`, `docs/responsible-disclosure.mdx`, `docs/settings/general.mdx`, `docs/settings/remote-projects.mdx`\n\n宿主 AI 硬性规则：\n- 没有 repo_clone_verified=true 时，不得声称已经读过源码。\n- 没有 repo_inspection_verified=true 时，不得把 README/docs/package 文件判断写成事实。\n- 没有 quick_start_verified=true 时，不得声称 Quick Start 已跑通。\n\n## Doramagic Pitfall Constraints / 踩坑约束\n\n这些规则来自 Doramagic 发现、验证或编译过程中的项目专属坑点。宿主 AI 必须把它们当作工作约束，而不是普通说明文字。\n\n### Constraint 1: 来源证据：Deployment(Other(Migration failed: error returned from database: (code: 1) no such column: ep.session_id))\n\n- Trigger: GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Deployment(Other(Migration failed: error returned from database: (code: 1) no such column: ep.session_id))\n- Host AI rule: 来源问题仍为 open，Pack Agent 需要复核是否仍影响当前版本。\n- Why it matters: 可能影响升级、迁移或版本选择。\n- Evidence: community_evidence:github | cevd_b34b2ea1b35a4dc2a4a0eb0681bdb883 | https://github.com/BloopAI/vibe-kanban/issues/2972 | 来源讨论提到 windows 相关条件，需在安装/试用前复核。\n- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。\n\n### Constraint 2: 来源证据：Support for self-hosted projects and better export\n\n- Trigger: GitHub 社区证据显示该项目存在一个配置相关的待验证问题：Support for self-hosted projects and better export\n- Host AI rule: 来源问题仍为 open，Pack Agent 需要复核是否仍影响当前版本。\n- Why it matters: 可能阻塞安装或首次运行。\n- Evidence: community_evidence:github | cevd_19d27caa9e34416a9f282869f76624b0 | https://github.com/BloopAI/vibe-kanban/issues/3396 | 来源类型 github_issue 暴露的待验证使用条件。\n- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。\n\n### Constraint 3: 来源证据：[Proposal] JIRA Integration for Vibe Kanban\n\n- Trigger: GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：[Proposal] JIRA Integration for Vibe Kanban\n- Host AI rule: 来源问题仍为 open，Pack Agent 需要复核是否仍影响当前版本。\n- Why it matters: 可能影响授权、密钥配置或安全边界。\n- Evidence: community_evidence:github | cevd_ab38fe97c4574e2da01ddedd71a4fbac | https://github.com/BloopAI/vibe-kanban/issues/2424 | 来源类型 github_issue 暴露的待验证使用条件。\n- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。\n\n### Constraint 4: 来源证据：Pre-release v0.1.40-20260401153532\n\n- Trigger: GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Pre-release v0.1.40-20260401153532\n- Host AI rule: 来源显示可能已有修复、规避或版本变化，说明书中必须标注适用版本。\n- Why it matters: 可能阻塞安装或首次运行。\n- Evidence: community_evidence:github | cevd_f4b99d437a4f4fd4989d2b3ef036553b | https://github.com/BloopAI/vibe-kanban/releases/tag/v0.1.40-20260401153532 | 来源讨论提到 docker 相关条件，需在安装/试用前复核。\n- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。\n\n### Constraint 5: 来源证据：Release v0.1.36\n\n- Trigger: GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Release v0.1.36\n- Host AI rule: 来源显示可能已有修复、规避或版本变化，说明书中必须标注适用版本。\n- Why it matters: 可能阻塞安装或首次运行。\n- Evidence: community_evidence:github | cevd_527645be4e3f438e81757ef265a70d79 | https://github.com/BloopAI/vibe-kanban/releases/tag/v0.1.36-20260323174633 | 来源讨论提到 npm 相关条件，需在安装/试用前复核。\n- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。\n\n### Constraint 6: 来源证据：Release v0.1.43\n\n- Trigger: GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Release v0.1.43\n- Host AI rule: 来源显示可能已有修复、规避或版本变化，说明书中必须标注适用版本。\n- Why it matters: 可能增加新用户试用和生产接入成本。\n- Evidence: community_evidence:github | cevd_53704dc7171446fe86b2017f72212ddc | https://github.com/BloopAI/vibe-kanban/releases/tag/v0.1.43-20260417125614 | 来源讨论提到 node 相关条件，需在安装/试用前复核。\n- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。\n\n### Constraint 7: 可能修改宿主 AI 配置\n\n- Trigger: 项目面向 Claude/Cursor/Codex/Gemini/OpenCode 等宿主，或安装命令涉及用户配置目录。\n- Host AI rule: 列出会写入的配置文件、目录和卸载/回滚步骤。\n- Why it matters: 安装可能改变本机 AI 工具行为，用户需要知道写入位置和回滚方法。\n- Evidence: capability.host_targets | github_repo:1002125012 | https://github.com/BloopAI/vibe-kanban | host_targets=claude, claude_code\n- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。\n\n### Constraint 8: 能力判断依赖假设\n\n- Trigger: README/documentation is current enough for a first validation pass.\n- Host AI rule: 将假设转成下游验证清单。\n- Why it matters: 假设不成立时，用户拿不到承诺的能力。\n- Evidence: capability.assumptions | github_repo:1002125012 | https://github.com/BloopAI/vibe-kanban | README/documentation is current enough for a first validation pass.\n- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。\n\n### Constraint 9: 来源证据：Pre-release v0.1.39-20260331145823\n\n- Trigger: GitHub 社区证据显示该项目存在一个运行相关的待验证问题：Pre-release v0.1.39-20260331145823\n- Host AI rule: 来源显示可能已有修复、规避或版本变化，说明书中必须标注适用版本。\n- Why it matters: 可能阻塞安装或首次运行。\n- Evidence: community_evidence:github | cevd_c005a56959634369929ce33eddbdc103 | https://github.com/BloopAI/vibe-kanban/releases/tag/v0.1.39-20260331145823 | 来源讨论提到 windows 相关条件，需在安装/试用前复核。\n- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。\n\n### Constraint 10: 来源证据：[Request] Support RDS for self hosting in AWS\n\n- Trigger: GitHub 社区证据显示该项目存在一个维护/版本相关的待验证问题：[Request] Support RDS for self hosting in AWS\n- Host AI rule: 来源问题仍为 open，Pack Agent 需要复核是否仍影响当前版本。\n- Why it matters: 可能影响升级、迁移或版本选择。\n- Evidence: community_evidence:github | cevd_f613b792c20942519560c0a286a82005 | https://github.com/BloopAI/vibe-kanban/issues/3405 | 来源类型 github_issue 暴露的待验证使用条件。\n- Hard boundary: 不要把这个坑点包装成已解决、已验证或可忽略，除非后续验证证据明确证明它已经关闭。\n", "summary": "给宿主 AI 的上下文和工作边界。", "title": "AI Context Pack / 带给我的 AI" }, "boundary_risk_card": { "asset_id": "boundary_risk_card", "filename": "BOUNDARY_RISK_CARD.md", "markdown": "# Boundary & Risk Card / 安装前决策卡\n\n项目：BloopAI/vibe-kanban\n\n## Doramagic 试用结论\n\n当前结论：可以进入发布前推荐检查；首次使用仍应从最小权限、临时目录和可回滚配置开始。\n\n## 用户现在可以做\n\n- 可以先阅读 Human Manual，理解项目目的和主要工作流。\n- 可以复制 Prompt Preview 做安装前体验；这只验证交互感，不代表真实运行。\n- 可以把官方 Quick Start 命令放到隔离环境中验证，不要直接进主力环境。\n\n## 现在不要做\n\n- 不要把 Prompt Preview 当成项目实际运行结果。\n- 不要把 metadata-only validation 当成沙箱安装验证。\n- 不要把未验证能力写成“已支持、已跑通、可放心安装”。\n- 不要在首次试用时交出生产数据、私人文件、真实密钥或主力配置目录。\n\n## 安装前检查\n\n- 宿主 AI 是否匹配：claude, claude_code\n- 官方安装入口状态：已发现官方入口\n- 是否在临时目录、临时宿主或容器中验证：必须是\n- 是否能回滚配置改动：必须能\n- 是否需要 API Key、网络访问、读写文件或修改宿主配置：未确认前按高风险处理\n- 是否记录了安装命令、实际输出和失败日志：必须记录\n\n## 当前阻塞项\n\n- 无阻塞项。\n\n## 项目专属踩坑\n\n- 来源证据：Deployment(Other(Migration failed: error returned from database: (code: 1) no such column: ep.session_id))（high）：可能影响升级、迁移或版本选择。 建议检查：来源问题仍为 open，Pack Agent 需要复核是否仍影响当前版本。\n- 来源证据：Support for self-hosted projects and better export（high）：可能阻塞安装或首次运行。 建议检查：来源问题仍为 open，Pack Agent 需要复核是否仍影响当前版本。\n- 来源证据：[Proposal] JIRA Integration for Vibe Kanban（high）：可能影响授权、密钥配置或安全边界。 建议检查：来源问题仍为 open，Pack Agent 需要复核是否仍影响当前版本。\n- 来源证据：Pre-release v0.1.40-20260401153532（medium）：可能阻塞安装或首次运行。 建议检查：来源显示可能已有修复、规避或版本变化，说明书中必须标注适用版本。\n- 来源证据：Release v0.1.36（medium）：可能阻塞安装或首次运行。 建议检查：来源显示可能已有修复、规避或版本变化，说明书中必须标注适用版本。\n\n## 风险与权限提示\n\n- no_demo: medium\n\n## 证据缺口\n\n- 暂未发现结构化证据缺口。\n", "summary": "安装、权限、验证和推荐前风险。", "title": "Boundary & Risk Card / 边界与风险卡" }, "human_manual": { "asset_id": "human_manual", "filename": "HUMAN_MANUAL.md", "markdown": "# https://github.com/BloopAI/vibe-kanban 项目说明书\n\n生成时间：2026-05-18 03:48:47 UTC\n\n## 目录\n\n- [Project Introduction](#page-project-introduction)\n- [Key Concepts](#page-key-concepts)\n- [Development Setup](#page-development-setup)\n- [Backend Architecture](#page-backend-architecture)\n- [Frontend Architecture](#page-frontend-architecture)\n- [Crate Reference](#page-crate-reference)\n- [Coding Agent Executors](#page-executors)\n- [MCP Server Integration](#page-mcp-integration)\n- [Relay and Remote Access](#page-relay-remote-access)\n- [Database and Data Models](#page-database-models)\n- [Deployment and Infrastructure](#page-deployment-infrastructure)\n\n\n\n## Project Introduction\n\n### 相关页面\n\n相关主题：[Key Concepts](#page-key-concepts), [Development Setup](#page-development-setup)\n\n
    \n相关源码文件\n\n以下源码文件用于生成本页说明：\n\n- [README.md](https://github.com/BloopAI/vibe-kanban/blob/main/README.md)\n- [packages/web-core/src/shared/keyboard/useWorkspaceShortcuts.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/keyboard/useWorkspaceShortcuts.ts)\n- [packages/web-core/src/shared/stores/useUiPreferencesStore.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/stores/useUiPreferencesStore.ts)\n- [packages/ui/src/components/CommandBar.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/ui/src/components/CommandBar.tsx)\n- [packages/web-core/src/shared/components/WorkspacesSidebar.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/components/WorkspacesSidebar.tsx)\n- [crates/server/src/routes/oauth.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/server/src/routes/oauth.rs)\n
    \n\n# Project Introduction\n\nVibe Kanban is a specialized project planning and agent execution platform designed for software engineering teams that leverage AI coding agents. The project provides an integrated environment where teams can plan work using kanban issues and execute coding tasks through dedicated workspaces that give AI agents controlled access to code branches, terminals, and development servers.\n\n## Purpose and Scope\n\nThe primary purpose of Vibe Kanban is to address the workflow inefficiency that emerges when software engineers spend significant time planning and reviewing AI coding agent activities. By providing a structured kanban interface combined with agent execution capabilities, the platform enables teams to:\n\n- Plan and prioritize work through visual kanban boards\n- Execute coding tasks through multiple supported AI agents\n- Review AI-generated changes with inline commenting capabilities\n- Preview applications directly within the development environment\n- Create and merge pull requests without context switching\n\n资料来源：[README.md](https://github.com/BloopAI/vibe-kanban/blob/main/README.md)\n\n## Supported AI Agents\n\nVibe Kanban integrates with a wide variety of coding agents, allowing teams to choose the most appropriate tool for their needs. The platform supports the following agents:\n\n| Agent | Description |\n|-------|-------------|\n| Claude Code | Anthropic's CLI agent |\n| Codex | OpenAI's coding agent |\n| Gemini CLI | Google's CLI agent |\n| GitHub Copilot | GitHub's AI pair programmer |\n| Amp | Alternative agent |\n| Cursor | Cursor AI IDE agent |\n| OpenCode | Open source agent |\n| Droid | Android development agent |\n| CCR | Custom agent integration |\n| Qwen Code | Alibaba's coding agent |\n\n资料来源：[README.md](https://github.com/BloopAI/vibe-kanban/blob/main/README.md)\n\n## Architecture Overview\n\nVibe Kanban follows a monorepo architecture with multiple packages organized for different concerns.\n\n```mermaid\ngraph TD\n subgraph \"packages/\"\n WC[\"web-core
    (packages/web-core)\"]\n UI[\"ui
    (packages/ui)\"]\n REM[\"remote-web
    (packages/remote-web)\"]\n end\n \n subgraph \"crates/\"\n SERVER[\"server
    (crates/server)\"]\n end\n \n WC <--> SERVER\n UI <--> WC\n REM --> SERVER\n```\n\n### Core Packages\n\nThe web application is built using multiple TypeScript packages:\n\n- **packages/web-core**: Contains shared hooks, stores, dialogs, and components that form the business logic layer\n- **packages/ui**: Reusable UI components including CommandBar, WorkspaceSidebar, and various input components\n- **packages/remote-web**: Pages and layouts for the remote/web deployment scenarios\n\nThe backend is implemented in Rust using Actix-web, providing OAuth authentication and API endpoints.\n\n资料来源：[packages/web-core/src/shared/keyboard/useWorkspaceShortcuts.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/keyboard/useWorkspaceShortcuts.ts)\n\n## Key Features\n\n### Kanban Issue Management\n\nThe kanban board provides a visual interface for creating, prioritizing, and assigning issues. Teams can organize work privately or collaboratively, with issues flowing through customizable status columns.\n\n### Workspace Execution\n\nWorkspaces provide isolated environments for AI agents to execute tasks. Each workspace includes:\n\n- A dedicated git branch for the task\n- Terminal access for command execution\n- Integrated dev server for live preview\n- Diff viewing and inline commenting\n\n```mermaid\ngraph LR\n A[Kanban Issue] --> B[Create Workspace]\n B --> C[Agent Executes on Branch]\n C --> D[Review Diffs]\n D --> E[Inline Comments]\n E --> F[Create PR]\n F --> G[Merge]\n```\n\n资料来源：[packages/ui/src/components/WorkspacesSidebar.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/ui/src/components/WorkspacesSidebar.tsx)\n\n### Command Bar Navigation\n\nThe application features a comprehensive command palette (activated via `Cmd+K`) that provides quick access to all major functionality:\n\n- Repository and branch selection\n- Status and priority filtering\n- Issue navigation and creation\n- Workspace management\n\n```typescript\n// Keyboard shortcut mappings from useWorkspaceShortcuts.ts\nconst SHORTCUTS = {\n 'v>p': 'Toggle Preview Mode',\n 'v>s': 'Toggle Left Sidebar', \n 'v>h': 'Toggle Left Main Panel',\n 'x>p': 'Git Create PR',\n 'x>m': 'Git Merge',\n 'x>r': 'Git Rebase',\n 'x>u': 'Git Push',\n 't>d': 'Toggle Dev Server',\n 'r>s': 'Run Setup Script',\n 'r>c': 'Run Cleanup Script'\n};\n```\n\n资料来源：[packages/web-core/src/shared/keyboard/useWorkspaceShortcuts.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/keyboard/useWorkspaceShortcuts.ts)\n\n### Attachment and Comment System\n\nIssues support rich commenting with file attachments. The system handles upload progression, confirmation states, and attachment metadata tracking.\n\n```typescript\n// Attachment state transitions\ntype AttachmentStatus = 'uploading' | 'confirming' | 'completed';\n\ninterface LocalAttachmentMetadata {\n path: string;\n pending_status: AttachmentStatus;\n upload_progress: number;\n}\n```\n\n资料来源：[packages/web-core/src/shared/hooks/useAzureAttachments.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/hooks/useAzureAttachments.ts)\n\n### Pending Approval Workflow\n\nWhen agents require human authorization for sensitive operations, the system displays a pending approval entry that allows users to approve or deny requests with explanatory messages.\n\n```mermaid\nstateDiagram-v2\n [*] --> AgentRequestsAction\n AgentRequestsAction --> PendingApproval\n PendingApproval --> Approved: User Approves\n PendingApproval --> Denied: User Denies\n Approved --> [*]\n Denied --> AgentResubmits: Agent Adjusts\n AgentResubmits --> PendingApproval\n```\n\n资料来源：[packages/web-core/src/shared/components/NormalizedConversation/PendingApprovalEntry.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/components/NormalizedConversation/PendingApprovalEntry.tsx)\n\n## UI State Management\n\nThe application maintains comprehensive UI state through Zustand stores, handling layout modes, panel visibility, and workspace-specific configurations.\n\n```typescript\n// Core UI preferences from useUiPreferencesStore.ts\ninterface UiPreferencesState {\n layoutMode: 'workspaces' | 'kanban' | 'accordion';\n isLeftSidebarVisible: boolean;\n isRightSidebarVisible: boolean;\n isTerminalVisible: boolean;\n paneSizes: Record;\n workspacePanelStates: Record;\n}\n```\n\n资料来源：[packages/web-core/src/shared/stores/useUiPreferencesStore.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/stores/useUiPreferencesStore.ts)\n\n## OAuth Authentication\n\nThe server implements OAuth authentication flows for secure user sessions, returning HTML responses for browser-based authentication callbacks.\n\n```rust\n// Simplified OAuth response structure\nstruct OAuthCallback {\n message: String, // Success or error message\n app_icon: Vec, // Base64 encoded application icon\n}\n```\n\n资料来源：[crates/server/src/routes/oauth.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/server/src/routes/oauth.rs)\n\n## Git Operations\n\nThe platform integrates comprehensive Git functionality directly into the workspace workflow:\n\n| Operation | Shortcut | Description |\n|-----------|----------|-------------|\n| Create Pull Request | `x>p` | Generate PR with AI-written descriptions |\n| Merge | `x>m` | Merge approved pull requests |\n| Rebase | `x>r` | Rebase branch onto target |\n| Push | `x>u` | Push changes to remote |\n| Force Push | (Dialog) | Force push with warning confirmation |\n\nForce push operations require explicit user confirmation through a dedicated dialog due to the destructive nature of the operation.\n\n资料来源：[packages/web-core/src/shared/dialogs/command-bar/ForcePushDialog.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/dialogs/command-bar/ForcePushDialog.tsx)\n\n## Conflict Resolution\n\nWhen Git operations encounter conflicts, the application provides a dedicated dialog to help users resolve them, displaying conflicted files and offering options to create new sessions or continue with existing ones.\n\n```typescript\ninterface ResolveConflictsDialogProps {\n conflictedFiles: string[];\n profiles?: ExecutorProfile[];\n hasExistingSession: boolean;\n createNewSession: boolean;\n onCreateNewSessionChange: (value: boolean) => void;\n}\n```\n\n资料来源：[packages/web-core/src/shared/dialogs/tasks/ResolveConflictsDialog.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/dialogs/tasks/ResolveConflictsDialog.tsx)\n\n## Development Workflow Summary\n\n```mermaid\ngraph TD\n A[Plan Issue on Kanban] --> B[Create Workspace]\n B --> C[Select Agent]\n C --> D[Agent Executes Tasks]\n D --> E{Requires Approval?}\n E -->|Yes| F[User Reviews & Approves/Denies]\n F --> G[Agent Continues]\n E -->|No| G\n G --> H[Review Diffs & Comments]\n H --> I[Create Pull Request]\n I --> J[Merge to Main]\n J --> K[Archive Workspace]\n```\n\nThe platform streamlines the entire development lifecycle from initial planning through final merge, keeping all stakeholders in a single interface throughout the process.\n\n---\n\n\n\n## Key Concepts\n\n### 相关页面\n\n相关主题：[Project Introduction](#page-project-introduction), [Database and Data Models](#page-database-models)\n\n
    \n相关源码文件\n\n以下源码文件用于生成本页说明：\n\n- [packages/web-core/src/shared/stores/useUiPreferencesStore.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/stores/useUiPreferencesStore.ts)\n- [packages/ui/src/components/WorkspacesSidebar.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/ui/src/components/WorkspacesSidebar.tsx)\n- [packages/web-core/src/shared/components/tasks/TaskDetails/ProcessesTab.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/components/tasks/TaskDetails/ProcessesTab.tsx)\n- [packages/ui/src/components/IssueCommentsSection.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/ui/src/components/IssueCommentsSection.tsx)\n- [packages/web-core/src/shared/keyboard/useWorkspaceShortcuts.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/keyboard/useWorkspaceShortcuts.ts)\n- [packages/web-core/src/shared/dialogs/command-bar/WorkspaceSelectionDialog.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/dialogs/command-bar/WorkspaceSelectionDialog.tsx)\n
    \n\n# Key Concepts\n\nVibe Kanban is a development workflow management tool designed for software engineering teams that work with AI coding agents. The application combines kanban-based issue planning with workspace-based agent execution, enabling engineers to plan, delegate, and review AI-assisted coding work within a unified interface.\n\n## Core Architecture Overview\n\nThe system is built around several interconnected concepts that work together to manage the lifecycle of AI-assisted development tasks.\n\n```mermaid\ngraph TD\n A[Organizations] --> B[Projects]\n B --> C[Kanban Issues]\n B --> D[Workspaces]\n C -->|Assign to| D\n D --> E[Sessions]\n D --> F[Scratches]\n E --> G[Processes]\n G --> H[Git Operations]\n E --> I[Attachments]\n D --> J[Dev Server]\n```\n\n## Projects\n\nProjects serve as the top-level organizational unit in Vibe Kanban. Each project contains its own kanban board and associated workspaces.\n\n### Project Properties\n\n| Property | Type | Description |\n|----------|------|-------------|\n| `id` | string | Unique identifier |\n| `name` | string | Display name |\n| `color` | string | Hex color for UI identification |\n| `updated_at` | timestamp | Last modification time |\n\nProjects are organized under organizations and contain all related kanban issues and workspaces. 资料来源：[packages/remote-web/src/pages/HomePage.tsx:60-80]()\n\n### Project Card Component\n\nThe `ProjectCard` component renders project items in the home page grid layout, displaying project name and providing navigation to individual project views. 资料来源：[packages/remote-web/src/pages/HomePage.tsx:80-100]()\n\n## Workspaces\n\nWorkspaces are the execution environment where coding agents operate. Each workspace provides an isolated branch, terminal access, and a dev server for a single coding agent.\n\n### Workspace Lifecycle\n\n```mermaid\nstateDiagram-v2\n [*] --> Active: Created\n Active --> Running: Agent starts\n Running --> Active: Agent pauses\n Active --> Archived: User archives\n Running --> Completed: Task finished\n Archived --> Active: User restores\n Completed --> [*]\n Active --> [*]\n```\n\n### Workspace Properties\n\n| Property | Type | Description |\n|----------|------|-------------|\n| `id` | string | Unique workspace identifier |\n| `name` | string | Display name |\n| `branch` | string | Git branch name |\n| `filesChanged` | number | Count of modified files |\n| `linesAdded` | number | Lines of code added |\n| `linesRemoved` | number | Lines of code removed |\n| `isRunning` | boolean | Agent currently executing |\n| `isPinned` | boolean | Pinned for quick access |\n| `isArchived` | boolean | Archived state |\n| `hasPendingApproval` | boolean | Awaiting human approval |\n| `hasRunningDevServer` | boolean | Dev server active |\n| `hasUnseenActivity` | boolean | New activity since last view |\n| `latestProcessCompletedAt` | timestamp | Last process completion |\n| `latestProcessStatus` | string | Status of latest process |\n| `prStatus` | string | Pull request status |\n\n资料来源：[packages/ui/src/components/WorkspacesSidebar.tsx:20-40]()\n\n### Workspace Panel State Management\n\nThe UI preferences store manages workspace panel visibility states, allowing users to toggle the left main panel and persist these preferences. 资料来源：[packages/web-core/src/shared/stores/useUiPreferencesStore.ts:30-50]()\n\n## Sessions\n\nSessions represent individual agent execution instances within a workspace. Each time a coding agent runs, it creates a new session that captures the execution context.\n\n### Session Attributes\n\nSessions track the complete execution context including:\n\n- **Profile Configuration**: The AI model and agent settings used\n- **Context Window**: Available memory and context for the agent\n- **Execution History**: Commands executed and outputs generated\n- **Process Chain**: Sequential processes that ran during the session\n\n资料来源：[packages/web-core/src/shared/components/tasks/TaskDetails/ProcessesTab.tsx:20-60]()\n\n### Process Tracking\n\nEach session contains multiple processes that represent discrete units of work:\n\n```mermaid\ngraph LR\n A[Process Start] --> B[Running]\n B --> C[User Approval Point]\n C -->|Approved| B\n C -->|Rejected| D[Stopped]\n B --> E[Completed]\n D --> E\n```\n\nThe process tab displays:\n\n- Process status (running, completed, stopped)\n- Started timestamp\n- Completed timestamp\n- Copy logs functionality\n\n资料来源：[packages/web-core/src/shared/components/tasks/TaskDetails/ProcessesTab.tsx:60-100]()\n\n## Kanban Issues\n\nKanban issues are the planning units in Vibe Kanban. They can be created, prioritized, and assigned to workspaces for execution.\n\n### Issue Comments\n\nThe `IssueCommentsSection` component handles all comment-related functionality for issues:\n\n```typescript\ninterface IssueCommentsSectionProps {\n comments: IssueCommentData[];\n commentInput: string;\n editingCommentId: string | null;\n editingValue: string;\n reactionsByCommentId: Map;\n localAttachments?: LocalAttachmentMetadata[];\n // ... additional handlers\n}\n```\n\n资料来源：[packages/ui/src/components/IssueCommentsSection.tsx:1-30]()\n\n### Comment Features\n\n| Feature | Description |\n|---------|-------------|\n| Add Comment | Submit new comments on issues |\n| Edit Comment | Modify existing comments |\n| Delete Comment | Remove comments |\n| Reactions | Add emoji reactions to comments |\n| Reply | Quote and reply to specific comments |\n| Attachments | Upload files to comments |\n\n### Issue Priority and Status\n\nIssues support priority levels and status tracking, accessible through the command bar. Priority labels include urgency indicators, while status values track issue progression through workflow states. 资料来源：[packages/ui/src/components/CommandBar.tsx:80-100]()\n\n## Scratches\n\nScratches are temporary execution spaces that allow quick experimentation or notes without creating a full workspace. They share the workspace execution environment but are not persisted in the same way.\n\n## Git Operations\n\nVibe Kanban integrates Git operations directly into the workspace workflow:\n\n| Operation | Shortcut | Description |\n|-----------|----------|-------------|\n| Create PR | `x>p` | Create pull request |\n| Merge | `x>m` | Merge current branch |\n| Rebase | `x>r` | Rebase onto target branch |\n| Push | `x>u` | Push changes |\n| Force Push | Dialog | Force push with confirmation |\n\n资料来源：[packages/web-core/src/shared/keyboard/useWorkspaceShortcuts.ts:1-20]()\n\n### Conflict Resolution\n\nWhen conflicts occur during Git operations, the `ResolveConflictsDialog` handles conflict detection and resolution workflows, allowing users to select agents and profiles for creating new resolution sessions. 资料来源：[packages/web-core/src/shared/dialogs/tasks/ResolveConflictsDialog.tsx:50-80]()\n\n## UI Layout and Navigation\n\n### Layout Modes\n\nVibe Kanban supports two primary layout modes:\n\n| Mode | Description |\n|------|-------------|\n| `kanban` | Kanban board view for issue planning |\n| `workspaces` | Workspace-focused view for agent execution |\n\nThe layout mode can be toggled via the UI preferences store. 资料来源：[packages/web-core/src/shared/stores/useUiPreferencesStore.ts:20-30]()\n\n### Keyboard Shortcuts\n\nComprehensive keyboard shortcuts enable efficient workflow management:\n\n| Category | Shortcut | Action |\n|----------|----------|--------|\n| View | `v>p` | Toggle preview mode |\n| View | `v>s` | Toggle left sidebar |\n| View | `v>h` | Toggle left main panel |\n| Git | `x>p` | Create PR |\n| Git | `x>m` | Merge |\n| Git | `x>r` | Rebase |\n| Git | `x>u` | Push |\n| Copy | `y>p` | Copy workspace path |\n| Copy | `y>l` | Copy raw logs |\n| Terminal | `t>d` | Toggle dev server |\n| Terminal | `t>w` | Toggle wrap lines |\n| Scripts | `r>s` | Run setup script |\n| Scripts | `r>c` | Run cleanup script |\n\n资料来源：[packages/web-core/src/shared/keyboard/useWorkspaceShortcuts.ts:1-30]()\n\n### Sidebar Components\n\nThe `WorkspacesSidebar` provides the main navigation interface with sections for:\n\n- Active workspaces\n- Draft workspaces (in creation)\n- Archived workspaces\n- Needs attention section (with raised hand indicator)\n\nWorkspaces can be filtered and sorted, with visual indicators for running agents, pending approvals, and unseen activity. 资料来源：[packages/ui/src/components/WorkspacesSidebar.tsx:10-50]()\n\n## Command Bar\n\nThe command bar (`CommandBar`) provides quick access to all application actions through a searchable interface:\n\n### Command Item Types\n\n| Type | Search Label Format |\n|------|---------------------|\n| `page` | `{pageId} {label}` |\n| `repo` | `{repoId} {displayName}` |\n| `branch` | `{branchName}` |\n| `status` | `{statusId} {statusName}` |\n| `priority` | `{priorityId} {priorityName}` |\n| `issue` | `{issueId} {simpleId} {title}` |\n| `createSubIssue` | `create new issue` |\n\n资料来源：[packages/ui/src/components/CommandBar.tsx:100-130]()\n\n### Workspace Selection\n\nThe `WorkspaceSelectionDialog` enables linking kanban issues to workspaces, displaying available workspaces with their branch information and archive status. 资料来源：[packages/web-core/src/shared/dialogs/command-bar/WorkspaceSelectionDialog.tsx:30-60]()\n\n## Data Flow Architecture\n\n```mermaid\ngraph TD\n subgraph Frontend\n A[React Components] --> B[Zustand Stores]\n B --> C[API Client]\n end\n \n subgraph Backend\n C --> D[Rust Server]\n D --> E[Database]\n D --> F[OAuth Handler]\n end\n \n B -->|Optimistic Updates| A\n C -->|REST API| D\n D -->|CRUD| E\n```\n\n## File Tree Persistence\n\nThe UI preferences store persists file tree collapsed paths per workspace using a keyed storage system:\n\n```typescript\nconst key = workspaceId ? `file-tree:${workspaceId}` : '';\nconst paths = useUiPreferencesStore((s) => s.collapsedPaths[key] ?? []);\n```\n\nThis ensures that file tree expansion states are preserved across sessions and workspace switches. 资料来源：[packages/web-core/src/shared/stores/useUiPreferencesStore.ts:70-100]()\n\n## Integration Points\n\n### OAuth Flow\n\nThe Rust server handles OAuth authentication flows, returning branded HTML pages for authentication completion. 资料来源：[crates/server/src/routes/oauth.rs:1-30]()\n\n### GitHub CLI Setup\n\nThe `GhCliSetupDialog` guides users through GitHub CLI installation and authentication, with help instructions for common error variants. 资料来源：[packages/web-core/src/shared/dialogs/auth/GhCliSetupDialog.tsx:1-50]()\n\n## Related Documentation\n\n- [Installation Guide](./installation.md)\n- [Getting Started](./getting-started.md)\n- [API Reference](./api-reference.md)\n- [Configuration](./configuration.md)\n\n---\n\n\n\n## Development Setup\n\n### 相关页面\n\n相关主题：[Project Introduction](#page-project-introduction), [Backend Architecture](#page-backend-architecture)\n\n
    \n相关源码文件\n\n以下源码文件用于生成本页说明：\n\n- [npx-cli/README.md](https://github.com/BloopAI/vibe-kanban/blob/main/npx-cli/README.md)\n- [npx-cli/package.json](https://github.com/BloopAI/vibe-kanban/blob/main/npx-cli/package.json)\n- [README.md](https://github.com/BloopAI/vibe-kanban/blob/main/README.md)\n- [packages/web-core/src/shared/hooks/useAzureAttachments.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/hooks/useAzureAttachments.ts)\n- [packages/web-core/src/shared/keyboard/useWorkspaceShortcuts.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/keyboard/useWorkspaceShortcuts.ts)\n
    \n\n# Development Setup\n\nThis guide covers the development environment setup for Vibe Kanban, a visual project management tool for developers that integrates with git repositories and coding agents.\n\n## Project Architecture Overview\n\nVibe Kanban is a monorepo application built with multiple technologies:\n\n```mermaid\ngraph TD\n subgraph \"Frontend (TypeScript/React)\"\n A[packages/web-core] --> B[packages/ui]\n A --> C[packages/remote-web]\n end\n \n subgraph \"CLI Layer\"\n D[npx-cli] --> A\n D --> E[vibe-kanban-mcp]\n end\n \n subgraph \"Backend (Rust)\"\n F[crates/server]\n end\n \n D --> F\n```\n\n## Prerequisites\n\n### System Requirements\n\n| Requirement | Version | Purpose |\n|-------------|---------|---------|\n| Node.js | >= 20.19.0 | Frontend runtime and CLI |\n| Rust | Stable toolchain | Backend server |\n| pnpm | Latest | Package management |\n\n### Required Tools\n\n1. **Coding Agent Authentication** - Configure authentication for your preferred coding agent (Claude Code, Codex, Gemini CLI, etc.)\n2. **Git** - Repository operations and worktree management\n3. **Azure CLI** (optional) - For attachment upload functionality\n\n## Repository Structure\n\n```\nvibe-kanban/\n├── packages/\n│ ├── web-core/ # Core React hooks, stores, and components\n│ ├── ui/ # Shared UI components\n│ ├── remote-web/ # Web application pages\n│ └── public/ # Static assets\n├── crates/\n│ └── server/ # Rust backend server\n├── npx-cli/ # CLI entry point\n└── scripts/ # Build and development scripts\n```\n\n资料来源：[npx-cli/README.md:1-20](https://github.com/BloopAI/vibe-kanban/blob/main/npx-cli/README.md)\n\n## Installation\n\n### 1. Clone the Repository\n\n```bash\ngit clone https://github.com/BloopAI/vibe-kanban\ncd vibe-kanban\n```\n\n### 2. Install Dependencies\n\n```bash\nnpm install -g pnpm\npnpm install\n```\n\n### 3. Build the CLI\n\n```bash\ncd npx-cli\npnpm build\n```\n\nThe build script uses esbuild to bundle the TypeScript source:\n\n```javascript\n// npx-cli/package.json\n{\n \"scripts\": {\n \"build\": \"esbuild src/cli.ts --bundle --platform=node --target=node20 --format=cjs --outfile=bin/cli.js\"\n }\n}\n```\n\n资料来源：[npx-cli/package.json:8](https://github.com/BloopAI/vibe-kanban/blob/main/npx-cli/package.json)\n\n## Development Workflow\n\n### Running the Application\n\n```bash\nnpx vibe-kanban\n```\n\nThis launches the application locally and opens it in your browser automatically.\n\n### Available CLI Commands\n\n```bash\nnpx vibe-kanban --help\nnpx vibe-kanban --version\nnpx vibe-kanban review --help\nnpx vibe-kanban mcp --help\n```\n\n资料来源：[npx-cli/README.md:12-17](https://github.com/BloopAI/vibe-kanban/blob/main/npx-cli/README.md)\n\n## Hotkeys Reference\n\nThe application provides keyboard shortcuts for common actions:\n\n| Shortcut | Action |\n|----------|--------|\n| `v>p` | Toggle preview mode |\n| `v>s` | Toggle left sidebar |\n| `v>h` | Toggle left main panel |\n| `x>p` | Git create PR |\n| `x>m` | Git merge |\n| `x>r` | Git rebase |\n| `x>u` | Git push |\n| `y>p` | Copy workspace path |\n| `y>l` | Copy raw logs |\n| `t>d` | Toggle dev server |\n| `t>w` | Toggle wrap lines |\n| `r>s` | Run setup script |\n| `r>c` | Run cleanup script |\n\n资料来源：[packages/web-core/src/shared/keyboard/useWorkspaceShortcuts.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/keyboard/useWorkspaceShortcuts.ts)\n\n## State Management\n\nThe application uses Zustand stores for state management:\n\n```mermaid\ngraph TD\n A[UI Store] -->|paneSizes, collapsedPaths| B[useUiPreferencesStore]\n C[Workspace Store] -->|diff data| D[useWorkspaceDiffStore]\n E[Project Store] -->|organizations, projects| F[Remote Data]\n```\n\n### Key Stores\n\n| Store | Purpose | Key State |\n|-------|---------|-----------|\n| `useUiPreferencesStore` | UI layout preferences | paneSizes, collapsedPaths, layoutMode |\n| `useWorkspaceDiffStore` | GitHub comments and diffs | comments, file changes |\n\n资料来源：[packages/web-core/src/shared/stores/useUiPreferencesStore.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/stores/useUiPreferencesStore.ts)\n\n## Attachment Handling\n\nFile attachments use Azure Blob Storage for uploads:\n\n```mermaid\nsequenceDiagram\n participant User\n participant UI as React Components\n participant API as confirmAttachmentUpload\n participant Azure as Azure Blob Storage\n \n User->>UI: Select file\n UI->>Azure: Upload file chunk\n Azure-->>UI: Upload progress (0-100%)\n UI->>API: Confirm upload\n API-->>UI: Return attachment ID\n```\n\nThe attachment confirmation payload includes:\n\n```typescript\n{\n project_id: string,\n upload_id: string,\n filename: string,\n content_type: string,\n size_bytes: number,\n hash: string,\n issue_id: string,\n comment_id: string\n}\n```\n\n资料来源：[packages/web-core/src/shared/hooks/useAzureAttachments.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/hooks/useAzureAttachments.ts)\n\n## Git Integration\n\n### Worktree-Based Development\n\nVibe Kanban creates isolated git worktrees for each task attempt, enabling:\n\n- Parallel development on multiple features\n- Clean separation between task branches\n- Easy diff viewing of agent changes\n\n### Supported Git Operations\n\n| Operation | Shortcut | Description |\n|-----------|----------|-------------|\n| Create PR | `x>p` | Create pull request with AI-generated description |\n| Merge | `x>m` | Merge changes back to main |\n| Rebase | `x>r` | Rebase current branch |\n| Push | `x>u` | Push changes |\n| Force Push | Dialog | Force push with confirmation dialog |\n\n## Backend Server (Rust)\n\nThe backend server handles OAuth flows and API requests:\n\n```rust\n// OAuth flow returns HTML response\nResponse::builder()\n .status(StatusCode::OK)\n .header(\"content-type\", \"text/html; charset=utf-8\")\n .body(body)\n```\n\n资料来源：[crates/server/src/routes/oauth.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/server/src/routes/oauth.rs)\n\n## Troubleshooting\n\n### Common Setup Issues\n\n1. **Node Version Mismatch**\n - Ensure Node.js >= 20.19.0\n - Use `nvm use` or update Node installation\n\n2. **CLI Not Found After Build**\n - Run `pnpm build` in the npx-cli directory\n - Ensure bin directory is in PATH\n\n3. **Authentication Failures**\n - Verify coding agent authentication\n - Check GitHub CLI authentication with `gh auth status`\n\n## Documentation\n\nFor more information, visit:\n\n- [Official Documentation](https://vibekanban.com/docs)\n- [Self-Hosting Guide](https://vibekanban.com/docs/self-hosting/deploy-docker)\n- [Supported Coding Agents](https://vibekanban.com/docs/supported-coding-agents)\n- [GitHub Discussions](https://github.com/BloopAI/vibe-kanban/discussions)\n\n## Contributing\n\nIdeas and changes should be raised via:\n\n1. [GitHub Discussions](https://github.com/BloopAI/vibe-kanban/discussions)\n2. [Discord](https://discord.gg/AC4nwVtJM3)\n\n资料来源：[README.md:45-50](https://github.com/BloopAI/vibe-kanban/blob/main/README.md)\n\n---\n\n\n\n## Backend Architecture\n\n### 相关页面\n\n相关主题：[Crate Reference](#page-crate-reference), [Database and Data Models](#page-database-models), [Coding Agent Executors](#page-executors)\n\n
    \n相关源码文件\n\n以下源码文件用于生成本页说明：\n\n- [crates/server/src/lib.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/server/src/lib.rs)\n- [crates/server/src/main.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/server/src/main.rs)\n- [crates/server/src/routes/mod.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/server/src/routes/mod.rs)\n- [crates/server/src/routes/oauth.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/server/src/routes/oauth.rs)\n- [crates/server/src/startup.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/server/src/startup.rs)\n- [crates/server/src/runtime/mod.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/server/src/runtime/mod.rs)\n
    \n\n# Backend Architecture\n\n## Overview\n\nVibe Kanban's backend is built with Rust using the Axum web framework, providing a high-performance API server that handles workspace management, authentication, and integration with coding agents. The backend follows a modular architecture with clear separation between routing, runtime management, and core server functionality.\n\nThe server component (`crates/server`) serves as the central hub for coordinating between the web frontend and various external services including GitHub integrations, coding agent executors, and development workspace environments.\n\n## Architecture Components\n\n### Core Server Structure\n\nThe backend is organized into several key modules:\n\n| Module | Purpose |\n|--------|---------|\n| `main.rs` | Application entry point and initialization |\n| `lib.rs` | Library interface and shared exports |\n| `startup.rs` | Server bootstrap and configuration |\n| `routes/` | HTTP endpoint handlers |\n| `runtime/` | Agent runtime execution management |\n\n### Module Hierarchy\n\n```mermaid\ngraph TD\n A[crates/server] --> B[main.rs]\n A --> C[lib.rs]\n A --> D[startup.rs]\n A --> E[routes/]\n A --> F[runtime/]\n E --> E1[oauth.rs]\n E --> E2[mod.rs]\n F --> F1[mod.rs]\n```\n\n## Request Flow\n\n```mermaid\ngraph LR\n A[Client Request] --> B[Axum Router]\n B --> C[Route Handlers]\n C --> D[OAuth Routes]\n C --> E[API Routes]\n C --> F[Runtime Routes]\n D --> G[OAuth Callback]\n E --> H[JSON Response]\n F --> I[Agent Execution]\n```\n\n## Routing System\n\n### Route Organization\n\nThe routing layer in `crates/server/src/routes/mod.rs` acts as a central router that aggregates all HTTP endpoints. Routes are organized by functional domain:\n\n- **OAuth Routes** (`routes/oauth.rs`) - Handle GitHub authentication and OAuth callbacks\n- **API Routes** - Handle workspace operations, task management, and agent interactions\n- **Runtime Routes** (`runtime/mod.rs`) - Manage coding agent execution contexts\n\n### OAuth Implementation\n\nThe OAuth route handler in `crates/server/src/routes/oauth.rs` demonstrates the server's response pattern for authentication flows:\n\n```rust\nResponse::builder()\n .status(StatusCode::OK)\n .header(\"content-type\", \"text/html; charset=utf-8\")\n .body(body)\n .unwrap()\n```\n\n资料来源：[crates/server/src/routes/oauth.rs:20-25]()\n\nThe OAuth callback returns an HTML response with embedded base64-encoded app icon, displaying a success message and instructions to return to the application.\n\n## Startup Sequence\n\n```mermaid\ngraph TD\n A[main.rs entry] --> B[Initialize Config]\n B --> C[Load Environment]\n C --> D[startup.rs::run]\n D --> E[Build Router]\n E --> F[Bind Socket]\n F --> G[Start Axum Server]\n G --> H[Listen for Requests]\n```\n\nThe startup module (`crates/server/src/startup.rs`) handles:\n- Configuration loading from environment variables\n- Router construction with middleware\n- Socket binding and server initialization\n\n## Runtime Management\n\n### Agent Execution Model\n\nThe runtime module (`crates/server/src/runtime/mod.rs`) manages the lifecycle of coding agent processes within workspaces. Each workspace provides an agent with:\n\n| Resource | Description |\n|----------|-------------|\n| Git Branch | Isolated branch for agent modifications |\n| Terminal | Shell access for command execution |\n| Dev Server | Preview environment for testing |\n\n资料来源：[crates/server/src/runtime/mod.rs]()\n\n### Process Tracking\n\nThe backend tracks agent processes with metadata including:\n\n- `started_at` - Process initialization timestamp\n- `completed_at` - Process termination timestamp\n- `isRunning` - Active execution state\n- `filesChanged` - Modified file count\n- `linesAdded` / `linesRemoved` - Change statistics\n\n## State Management\n\n### Workspace States\n\n```mermaid\nstateDiagram-v2\n [*] --> Draft\n Draft --> Running: Start Agent\n Running --> Completed: Agent Finishes\n Running --> Error: Execution Failure\n Completed --> Archived: User Archives\n Error --> Running: Retry\n Archived --> [*]\n Draft --> [*]: Cancel\n```\n\nWorkspaces maintain states including draft, running, completed, and archived, allowing users to manage multiple concurrent agent execution contexts.\n\n## API Response Patterns\n\nThe backend uses standard HTTP response patterns with JSON payloads:\n\n| Status Code | Usage |\n|-------------|-------|\n| 200 OK | Successful requests |\n| 400 Bad Request | Invalid input |\n| 401 Unauthorized | Authentication required |\n| 500 Internal Server Error | Server-side failures |\n\n## Frontend Integration\n\nThe web-core package (`packages/web-core/src/shared/`) interacts with the backend through:\n\n- **Dialog Components** - Modal interfaces for OAuth setup, force push, workspace selection\n- **Store Hooks** - State management via `useWorkspaceDiffStore`, `useUiPreferencesStore`\n- **API Hooks** - Data fetching through `useAzureAttachments` for file handling\n\n资料来源：[crates/server/src/lib.rs]()\n资料来源：[crates/web-core/src/shared/stores/useWorkspaceDiffStore.ts]()\n资料来源：[crates/web-core/src/shared/hooks/useAzureAttachments.ts]()\n\n## Configuration\n\nThe server reads configuration from environment variables with sensible defaults for:\n\n- Server host and port\n- Database connection strings\n- OAuth client credentials\n- Agent executor profiles\n\n## Dependencies\n\nKey Rust dependencies for the backend:\n\n| Crate | Version | Purpose |\n|-------|---------|---------|\n| axum | ^0.7 | Web framework |\n| tokio | ^1 | Async runtime |\n| serde | ^1 | Serialization |\n| tower | latest | Middleware |\n\n资料来源：[crates/server/src/main.rs]()\n资料来源：[crates/server/src/routes/mod.rs]()\n\n---\n\n\n\n## Frontend Architecture\n\n### 相关页面\n\n相关主题：[Crate Reference](#page-crate-reference), [Backend Architecture](#page-backend-architecture)\n\n
    \nRelevant Source Files\n\n以下源码文件用于生成本页说明：\n\n- [packages/local-web/src/routes/_app.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/local-web/src/routes/_app.tsx)\n- [packages/remote-web/src/app/entry/App.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/remote-web/src/app/entry/App.tsx)\n- [packages/web-core/src/shared/hooks/useActions.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/hooks/useActions.ts)\n- [packages/web-core/src/shared/providers/WorkspaceProvider.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/providers/WorkspaceProvider.tsx)\n- [packages/ui/src/components/KanbanBoard.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/ui/src/components/KanbanBoard.tsx)\n- [packages/ui/src/components/CommandBar.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/ui/src/components/CommandBar.tsx)\n- [packages/ui/src/components/WorkspacesSidebar.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/ui/src/components/WorkspacesSidebar.tsx)\n- [packages/web-core/src/shared/stores/useUiPreferencesStore.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/stores/useUiPreferencesStore.ts)\n- [packages/web-core/src/pages/kanban/KanbanIssuePanelContainer.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/pages/kanban/KanbanIssuePanelContainer.tsx)\n- [packages/web-core/src/shared/dialogs/command-bar/WorkspaceSelectionDialog.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/dialogs/command-bar/WorkspaceSelectionDialog.tsx)\n
    \n\n# Frontend Architecture\n\n## Overview\n\nVibe Kanban implements a modern, component-driven frontend architecture designed for complex project management workflows involving AI coding agents. The frontend is organized as a monorepo using a layered package structure that separates concerns between UI primitives, business logic, and deployment variants.\n\nThe architecture follows these core principles:\n- **Component Reusability**: Shared UI components across multiple deployment contexts\n- **State Centralization**: Global state management via Zustand stores\n- **Provider Pattern**: Context-based dependency injection for cross-cutting concerns\n- **Type Safety**: Full TypeScript coverage with strict typing\n\n## Monorepo Structure\n\nThe project uses a monorepo architecture with the following key packages:\n\n| Package | Purpose |\n|---------|---------|\n| `packages/ui` | Reusable UI component library (buttons, dialogs, command bar) |\n| `packages/web-core` | Business logic, hooks, stores, and shared features |\n| `packages/local-web` | Local deployment variant (runs entirely in browser) |\n| `packages/remote-web` | Remote deployment variant (connects to backend server) |\n| `npx-cli` | CLI wrapper for easy execution via `npx vibe-kanban` |\n\n```\nvibe-kanban/\n├── packages/\n│ ├── ui/ # Shared UI primitives\n│ │ └── src/components/\n│ │ ├── CommandBar.tsx\n│ │ ├── KanbanBoard.tsx\n│ │ └── WorkspacesSidebar.tsx\n│ ├── web-core/ # Core business logic\n│ │ └── src/\n│ │ ├── shared/\n│ │ │ ├── hooks/ # useActions, useAzureAttachments\n│ │ │ ├── providers/ # WorkspaceProvider\n│ │ │ ├── stores/ # Zustand state stores\n│ │ │ └── dialogs/ # Modal components\n│ │ └── pages/\n│ ├── local-web/ # Local app entry point\n│ └── remote-web/ # Remote/server-connected variant\n└── npx-cli/ # CLI entry point\n```\n\n## Application Entry Points\n\n### Local Web Application\n\nThe local web application serves as the standalone deployment variant that runs entirely in the browser without requiring a backend server.\n\n```tsx\n// packages/local-web/src/routes/_app.tsx\n// Main entry point for local deployment\n```\n\n### Remote Web Application\n\nThe remote web application connects to a backend server for persistent storage and multi-user collaboration features.\n\n```tsx\n// packages/remote-web/src/app/entry/App.tsx\n// Main entry point for remote deployment\n```\n\n## State Management\n\n### UI Preferences Store\n\nThe application uses Zustand for centralized state management. The `useUiPreferencesStore` handles UI-specific state including sidebar visibility, panel sizes, and layout modes.\n\n```typescript\n// packages/web-core/src/shared/stores/useUiPreferencesStore.ts\ninterface UiPreferencesState {\n // Layout state\n layoutMode: 'workspaces' | 'kanban';\n isLeftSidebarVisible: boolean;\n isRightSidebarVisible: boolean;\n isTerminalVisible: boolean;\n \n // Panel states per workspace\n workspacePanelStates: Record;\n \n // Pane configurations\n paneSizes: Record;\n collapsedPaths: Record;\n}\n```\n\nKey state transitions supported by the store:\n\n| Action | Description |\n|--------|-------------|\n| `toggleLayoutMode()` | Switch between workspaces and kanban views |\n| `toggleLeftSidebar()` | Show/hide left sidebar |\n| `toggleTerminal()` | Show/hide terminal panel |\n| `toggleWorkspacePanel(workspaceId, panel)` | Toggle specific workspace panel |\n\n资料来源：[packages/web-core/src/shared/stores/useUiPreferencesStore.ts:1-50](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/stores/useUiPreferencesStore.ts)\n\n### Workspace Provider\n\nThe `WorkspaceProvider` is a React context provider that manages workspace-scoped state and operations.\n\n```tsx\n// packages/web-core/src/shared/providers/WorkspaceProvider.tsx\n// Provides workspace context to child components\n```\n\n## Core UI Components\n\n### KanbanBoard\n\nThe `KanbanBoard` component is the central UI element for task visualization and management. It renders the drag-and-drop interface for issues across different status columns.\n\n```tsx\n// packages/ui/src/components/KanbanBoard.tsx\n```\n\nThe board supports multiple item types rendered through consistent interface patterns:\n\n| Item Type | Identifier | Search Label Pattern |\n|-----------|------------|---------------------|\n| Page | `pageId` | `{pageId} {label}` |\n| Repository | `repo.id` | `{repo.id} {repo.display_name}` |\n| Branch | `branch.name` | `branch.name` |\n| Status | `status.id` | `{status.id} {status.name}` |\n| Priority | `priority.id` | `{priority.id ?? 'none'} {priority.name}` |\n| Issue | `issue.id` | `{issue.id} {issue.simple_id} {issue.title}` |\n\n资料来源：[packages/ui/src/components/CommandBar.tsx:1-50](https://github.com/BloopAI/vibe-kanban/blob/main/packages/ui/src/components/CommandBar.tsx)\n\n### CommandBar\n\nThe `CommandBar` component provides a keyboard-driven interface for navigation and actions. It groups items by category and supports fuzzy search through labels.\n\n```tsx\n// packages/ui/src/components/CommandBar.tsx\n```\n\n### WorkspacesSidebar\n\nThe `WorkspacesSidebar` displays workspace summaries with multiple layout modes:\n\n- **List Layout**: Flat vertical list with sections for active, archived, and needs-attention workspaces\n- **Accordion Layout**: Collapsible sections with header persistence\n\n```tsx\n// packages/ui/src/components/WorkspacesSidebar.tsx\n```\n\nWorkspace summaries display:\n- Workspace name and active state\n- Running status and pending approvals\n- Dev server status\n- PR status\n- Activity indicators (unseen activity flag)\n- Git statistics (files changed, lines added/removed)\n\n资料来源：[packages/ui/src/components/WorkspacesSidebar.tsx:1-80](https://github.com/BloopAI/vibe-kanban/blob/main/packages/ui/src/components/WorkspacesSidebar.tsx)\n\n## Dialog System\n\n### Dialog Architecture\n\nThe application uses a modal dialog system for complex interactions. Dialogs are defined using the `defineModal` higher-order function pattern.\n\n```tsx\n// Example dialog pattern\nexport const ForcePushDialog = defineModal(\n ForcePushDialogImpl\n);\n```\n\n### Dialog Types\n\n| Dialog | Purpose | Key Features |\n|--------|---------|--------------|\n| `ForcePushDialog` | Confirm destructive force-push operations | Loading state, destructive variant |\n| `ResolveConflictsDialog` | Handle git merge conflicts | Agent/profile selector, file list |\n| `WorkspaceSelectionDialog` | Link issues to workspaces | Workspace search, archive filtering |\n| `ReleaseNotesDialog` | Display changelog information | GitHub integration, markdown rendering |\n| `GhCliSetupDialog` | GitHub CLI authentication setup | Step-by-step instructions, error help |\n\n### ResolveConflictsDialog\n\nHandles git merge conflicts by displaying conflicted files and providing agent selection for resolution.\n\n```tsx\n// packages/web-core/src/shared/dialogs/tasks/ResolveConflictsDialog.tsx\n\n{conflictedFiles.slice(0, 5).map((file) => (\n
  • {file}
    • \n))}\n{conflictedFiles.length > 5 && (\n
  • And {conflictedFiles.length - 5} more...
    • \n)}\n```\n\nThe dialog includes:\n- Conflicted file list with truncation for large conflicts\n- Agent selector for AI-powered resolution\n- Config selector for resolution parameters\n- New session toggle for existing workspace sessions\n\n资料来源：[packages/web-core/src/shared/dialogs/tasks/ResolveConflictsDialog.tsx:80-100](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/dialogs/tasks/ResolveConflictsDialog.tsx)\n\n## Kanban Issue Panel\n\nThe `KanbanIssuePanelContainer` renders detailed issue views with multiple collapsible sections:\n\n```tsx\n// packages/web-core/src/pages/kanban/KanbanIssuePanelContainer.tsx\n\n }\n renderRelationshipsSection={(issueId) => }\n renderSubIssuesSection={(issueId) => }\n renderCommentsSection={(issueId) => }\n/>\n```\n\n### Issue Panel Sections\n\n| Section | Container Component | Purpose |\n|---------|---------------------|---------|\n| Workspaces | `IssueWorkspacesSectionContainer` | Associated workspace links |\n| Relationships | `IssueRelationshipsSectionContainer` | Linked issues and parent-child relations |\n| Sub-Issues | `IssueSubIssuesSectionContainer` | Child issues breakdown |\n| Comments | `IssueCommentsSectionContainer` | Discussion and review comments |\n\n## Hooks System\n\n### useActions Hook\n\nCustom hooks encapsulate business logic and provide clean interfaces for components.\n\n```tsx\n// packages/web-core/src/shared/hooks/useActions.ts\n// Centralizes action dispatching and state updates\n```\n\n### useAzureAttachments Hook\n\nHandles file upload workflows with progress tracking:\n\n```typescript\n// packages/web-core/src/shared/hooks/useAzureAttachments.ts\n\n// Progress tracking for uploads\nsetPendingAttachments((prev) =>\n prev.map((p) =>\n p.file === file ? { ...p, status: 'confirming', progress: 100 } : p\n ))\n);\n```\n\nThe hook manages:\n- Pending attachment states\n- Upload progress tracking\n- Confirmation workflows\n- Completed attachment tracking\n\n## Component Interaction Flow\n\n```mermaid\ngraph TD\n A[App Entry Point] --> B[WorkspaceProvider]\n A --> C[UiPreferencesStore]\n B --> D[KanbanBoard]\n B --> E[WorkspacesSidebar]\n D --> F[KanbanIssuePanelContainer]\n F --> G[Dialog System]\n E --> H[CommandBar]\n G --> I[ForcePushDialog]\n G --> J[ResolveConflictsDialog]\n G --> K[WorkspaceSelectionDialog]\n \n C --> L[Layout Toggle]\n C --> M[Sidebar Visibility]\n C --> N[Terminal Toggle]\n \n style A fill:#e1f5fe\n style B fill:#fff3e0\n style C fill:#e8f5e9\n```\n\n## Home Page Structure\n\nThe remote web application provides a structured home page with organization and project navigation:\n\n```tsx\n// packages/remote-web/src/pages/HomePage.tsx\n\nfunction OrganizationSection({ organization, projects, hostId, onRequireHost }) {\n return (\n
    \n
    \n

    {organization.name}

    \n

    {projects.length} {projects.length === 1 ? \"project\" : \"projects\"}

    \n
    \n
      \n {projects.map((project) => )}\n
    \n
    \n );\n}\n```\n\n## Deployment Variants\n\nThe application supports two deployment modes:\n\n```mermaid\ngraph LR\n subgraph Local[\"Local Deployment\"]\n L1[local-web package]\n L2[Browser-only execution]\n L3[No server required]\n end\n \n subgraph Remote[\"Remote Deployment\"]\n R1[remote-web package]\n R2[Backend server connection]\n R3[Multi-user support]\n end\n \n style Local fill:#bbdefb\n style Remote fill:#c8e6c9\n```\n\n### Local Web\n\n- Runs entirely in the browser\n- No backend server required\n- Single-user mode\n- Data stored in browser storage\n\n### Remote Web\n\n- Requires backend server (`crates/server`)\n- Multi-user support via OAuth authentication\n- Persistent storage in database\n- Real-time collaboration features\n\n## Technology Stack\n\n| Layer | Technology | Purpose |\n|-------|------------|---------|\n| Framework | React 18+ | UI rendering |\n| Language | TypeScript | Type safety |\n| State | Zustand | Lightweight state management |\n| Styling | Tailwind CSS | Utility-first styling |\n| Build | Vite + esbuild | Fast builds |\n| Routing | React Router | SPA navigation |\n| i18n | react-i18next | Internationalization |\n| Icons | Lucide React | Icon library |\n\n## Key Architectural Patterns\n\n### 1. Provider Pattern\n\nCross-cutting concerns are injected via React context providers:\n\n```tsx\n// Workspace context available throughout the component tree\n\n \n \n\n```\n\n### 2. Store Pattern\n\nZustand stores provide centralized, typed state with simple update functions:\n\n```typescript\n// Simple store usage\nconst { layoutMode, toggleLayoutMode } = useUiPreferencesStore();\n```\n\n### 3. Modal Definition Pattern\n\nDialogs use a higher-order function for consistent modal lifecycle management:\n\n```tsx\nexport const SomeDialog = defineModal(Component);\n```\n\n### 4. Lazy Loading\n\nComponents support dynamic imports for code splitting:\n\n```tsx\n// Dialogs loaded on demand to reduce initial bundle size\nconst SomeDialog = lazy(() => import('./dialogs/SomeDialog'));\n\n---\n\n\n\n## Crate Reference\n\n### 相关页面\n\n相关主题：[Backend Architecture](#page-backend-architecture), [Coding Agent Executors](#page-executors), [Relay and Remote Access](#page-relay-remote-access)\n\n
    \n相关源码文件\n\n以下源码文件用于生成本页说明：\n\n- [crates/server/src/routes/oauth.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/server/src/routes/oauth.rs)\n- [README.md](https://github.com/BloopAI/vibe-kanban/blob/main/README.md)\n
    \n\n# Crate Reference\n\n## Overview\n\nVibe Kanban is a monorepo with a multi-package architecture that combines Rust-based backend services (crates) with TypeScript/React frontend packages. The backend crates provide core infrastructure for workspace management, code execution, database operations, and secure communication.\n\nThe project structure includes:\n\n- **Frontend packages** (`packages/`): React-based UI including `web-core`, `ui`, and `remote-web`\n- **Rust crates** (`crates/`): Backend services for server operations, API types, database, executors, MCP protocol, relay tunneling, workspace management, and worktree management\n\n## Crate Architecture\n\nThe Rust backend consists of several specialized crates that work together to provide the core functionality of Vibe Kanban:\n\n| Crate | Purpose |\n|-------|---------|\n| `server` | Main HTTP server with route handlers |\n| `api-types` | Shared type definitions for API communication |\n| `db` | Database operations and models |\n| `executors` | Code execution engine for coding agents |\n| `relay-tunnel` | Secure relay communication |\n| `mcp` | Model Context Protocol integration |\n| `workspace-manager` | Workspace lifecycle management |\n| `worktree-manager` | Git worktree operations |\n\n## Server Crate\n\nThe `server` crate (`crates/server/src/`) is the main entry point for the backend application. It handles HTTP routing and serves both the API endpoints and static assets.\n\n### OAuth Routes\n\nThe server provides OAuth authentication flow endpoints for GitHub integration:\n\n**File:** `crates/server/src/routes/oauth.rs`\n\nThe OAuth handler returns an HTML page confirming successful authentication:\n\n```rust\nResponse::builder()\n .status(StatusCode::OK)\n .header(\"content-type\", \"text/html; charset=utf-8\")\n .body(body)\n .unwrap()\n```\n\nThe response includes:\n- Application logo embedded as base64 PNG\n- Success message display\n- User instruction to close the tab and return to the app\n\n## Project Organization\n\n### Monorepo Structure\n\n```\nvibe-kanban/\n├── packages/\n│ ├── web-core/ # Core web UI components\n│ ├── ui/ # Shared UI components\n│ └── remote-web/ # Remote access web interface\n├── crates/\n│ ├── server/ # HTTP server\n│ ├── api-types/ # API type definitions\n│ ├── db/ # Database layer\n│ ├── executors/ # Agent execution engine\n│ ├── relay-tunnel/ # Relay communication\n│ ├── mcp/ # MCP protocol\n│ ├── workspace-manager/ # Workspace operations\n│ └── worktree-manager/ # Git worktree management\n└── public/ # Static assets\n```\n\n## Data Flow Architecture\n\n```mermaid\ngraph TD\n subgraph Frontend[\"Frontend (TypeScript/React)\"]\n UI[UI Components]\n WC[Web Core]\n end\n \n subgraph Backend[\"Backend (Rust Crates)\"]\n Server[Server Crate]\n DB[(Database)]\n API[API Types]\n end\n \n subgraph Execution[\"Execution Layer\"]\n Exec[Executors]\n WM[Workspace Manager]\n WTM[Worktree Manager]\n MCP[MCP Protocol]\n RT[Relay Tunnel]\n end\n \n UI --> WC\n WC --> Server\n Server --> DB\n Server --> API\n Exec --> WM\n WM --> WTM\n Exec --> MCP\n Exec --> RT\n```\n\n## Key Modules\n\n### API Types\n\nThe `api-types` crate provides shared type definitions used across the frontend and backend for type-safe API communication.\n\n### Database Layer\n\nThe `db` crate handles persistent storage operations, including:\n- Workspace state persistence\n- User preferences\n- Project and organization data\n\n### Workspace Manager\n\nManages the lifecycle of workspaces, including creation, archival, and state tracking.\n\n### Worktree Manager\n\nHandles Git worktree operations, providing isolated branch environments for each workspace.\n\n### Executors\n\nThe execution engine that runs coding agents (Claude Code, Codex, Gemini CLI, etc.) within workspace environments.\n\n### Relay Tunnel\n\nProvides secure communication channels for remote access scenarios.\n\n### MCP Integration\n\nImplements the Model Context Protocol for enhanced agent capabilities.\n\n## Configuration and Preferences\n\nThe frontend manages user preferences through the `useUiPreferencesStore`, which handles:\n\n| Setting | Description |\n|---------|-------------|\n| `layoutMode` | Toggle between 'workspaces' and 'kanban' views |\n| `isLeftSidebarVisible` | Left sidebar visibility |\n| `isTerminalVisible` | Terminal panel visibility |\n| `paneSizes` | Customizable panel dimensions |\n| `collapsedPaths` | File tree collapsed state per workspace |\n| `fileSearchRepoId` | Active repository for file search |\n\n资料来源：[packages/web-core/src/shared/stores/useUiPreferencesStore.ts]()\n\n## Development Workflow\n\nThe system supports the following developer keyboard shortcuts:\n\n| Shortcut | Action |\n|----------|--------|\n| `v>p` | Toggle preview mode |\n| `v>s` | Toggle left sidebar |\n| `v>h` | Toggle left main panel |\n| `x>p` | Create Git PR |\n| `x>m` | Merge PR |\n| `x>r` | Git rebase |\n| `x>u` | Git push |\n| `t>d` | Toggle dev server |\n| `t>w` | Toggle wrap lines |\n\n资料来源：[packages/web-core/src/shared/keyboard/useWorkspaceShortcuts.ts]()\n\n## Summary\n\nThe Vibe Kanban architecture combines TypeScript/React frontend packages with Rust backend crates to provide a comprehensive coding agent workspace management system. The Rust crates handle core infrastructure including database operations, workspace lifecycle, Git worktree management, code execution, and secure communication, while the frontend provides the user interface for planning, reviewing, and managing coding agent activities.\n\nFor the latest updates and project status, refer to the official announcement at [vibekanban.com/blog/shutdown](https://vibekanban.com/blog/shutdown).\n\n---\n\n\n\n## Coding Agent Executors\n\n### 相关页面\n\n相关主题：[Crate Reference](#page-crate-reference), [MCP Server Integration](#page-mcp-integration)\n\n
    \n相关源码文件\n\n以下源码文件用于生成本页说明：\n\n- [README.md](https://github.com/BloopAI/vibe-kanban/blob/main/README.md)\n- [packages/web-core/src/features/workspace-chat/ui/SessionChatBoxContainer.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/features/workspace-chat/ui/SessionChatBoxContainer.tsx)\n- [packages/web-core/src/features/workspace-chat/ui/ConversationListContainer.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/features/workspace-chat/ui/ConversationListContainer.tsx)\n- [packages/web-core/src/shared/keyboard/useWorkspaceShortcuts.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/keyboard/useWorkspaceShortcuts.ts)\n- [packages/web-core/src/shared/dialogs/command-bar/WorkspaceSelectionDialog.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/dialogs/command-bar/WorkspaceSelectionDialog.tsx)\n- [packages/web-core/src/shared/components/tasks/TaskDetails/ProcessesTab.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/components/tasks/TaskDetails/ProcessesTab.tsx)\n
    \n\n# Coding Agent Executors\n\n## Overview\n\nCoding Agent Executors in Vibe Kanban are the runtime engines that enable AI coding agents to execute tasks within isolated workspace environments. Each workspace provides an agent with a dedicated branch, terminal, and dev server, allowing software engineers to plan work through kanban issues while agents perform the actual coding tasks.\n\nThe executor system supports multiple AI coding agents, enabling teams to choose the most appropriate agent for their specific needs or switch between agents based on task requirements.\n\n资料来源：[README.md:1-20]()\n\n## Supported Agents\n\nVibe Kanban supports the following coding agents:\n\n| Agent | Description |\n|-------|-------------|\n| Claude Code | Anthropic's CLI tool for Claude models |\n| Codex | OpenAI's coding agent |\n| Gemini CLI | Google's Gemini-based CLI agent |\n| GitHub Copilot | Microsoft's AI pair programmer |\n| Amp | Alternative coding agent |\n| Cursor | Cursor IDE's AI agent |\n| OpenCode | Open-source coding agent |\n| Droid | Mobile-optimized coding agent |\n| CCR | Custom coding agent configuration |\n| Qwen Code | Alibaba's Qwen-based coding agent |\n\n资料来源：[README.md:25]()\n\n## Architecture\n\n### Executor Components\n\nThe executor system consists of several key components:\n\n1. **Session Chat Box** - The primary interface for interacting with coding agents during task execution\n2. **Conversation List** - Displays the ongoing conversation and output between the agent and user\n3. **Process Management** - Handles the lifecycle of agent processes including start, execution, and completion\n4. **Workspace Integration** - Provides isolated environments with git branches, terminals, and dev servers\n\n```mermaid\ngraph TD\n A[Kanban Issue] --> B[Workspace Creation]\n B --> C[Session Chat Box]\n C --> D[Agent Executor]\n D --> E[Conversation List]\n D --> F[Process Execution]\n F --> G[Branch & Terminal]\n F --> H[Dev Server]\n E --> I[Diff Review]\n I --> J[Inline Comments]\n J --> K[Pull Request]\n```\n\n资料来源：[packages/web-core/src/features/workspace-chat/ui/SessionChatBoxContainer.tsx:1-50]()\n\n## Session Chat Box\n\nThe `SessionChatBox` component is the central hub for agent interaction. It manages the chat interface, editor input, and session state.\n\n### Key Properties\n\n| Property | Type | Purpose |\n|----------|------|---------|\n| `status` | `idle` \\| `running` \\| `completed` | Current execution state |\n| `repoIds` | `string[]` | Associated repository identifiers |\n| `tokenUsageInfo` | `TokenUsageInfo` | Usage tracking for billing |\n| `formatExecutorLabel` | `Function` | Formats agent display names |\n| `formatSessionDate` | `Function` | Formats session timestamps |\n| `renderAgentIcon` | `Function` | Renders agent-specific icons |\n\n### Session State Management\n\n```typescript\nsession={{\n sessions: [],\n selectedSessionId: undefined,\n onSelectSession: () => {},\n isNewSessionMode: false,\n onNewSession: undefined,\n}}\n```\n\nThe session object tracks the active conversation context, allowing users to switch between multiple agent sessions within a workspace.\n\n资料来源：[packages/web-core/src/features/workspace-chat/ui/SessionChatBoxContainer.tsx:60-100]()\n\n## Conversation Display\n\nThe `ConversationList` component renders the ongoing interaction with the coding agent.\n\n### Entry Types\n\n| Entry Type | Rendering Component |\n|------------|---------------------|\n| `STDOUT` | Standard output paragraphs |\n| `STDERR` | Error output paragraphs |\n| `NORMALIZED_ENTRY` | Full display with expansion support |\n| `THINKING` | Aggregated thinking blocks |\n\n```mermaid\ngraph LR\n A[Agent Output] --> B{Entry Type?}\n B -->|STDOUT| C[Paragraph Display]\n B -->|STDERR| D[Error Display]\n B -->|NORMALIZED| E[DisplayConversationEntry]\n B -->|THINKING| F[Aggregated Thinking]\n```\n\n资料来源：[packages/web-core/src/features/workspace-chat/ui/ConversationListContainer.tsx:40-70]()\n\n## Process Execution\n\nThe `ProcessesTab` component provides visibility into running and completed agent processes.\n\n### Process Information Displayed\n\n- **Process Status** - Current state (running, completed, failed)\n- **Started At** - Process initiation timestamp\n- **Completed At** - Process completion timestamp (when applicable)\n- **Log Output** - Real-time and archived process logs\n\n### Log Management\n\nThe ProcessesTab includes functionality to copy logs to clipboard for debugging and audit purposes:\n\n```typescript\nconst handleCopyLogs = () => {\n // Copies all accumulated logs to clipboard\n // Updates UI to show \"Logs copied\" confirmation\n};\n```\n\n资料来源：[packages/web-core/src/shared/components/tasks/TaskDetails/ProcessesTab.tsx:1-80]()\n\n## Workspace Shortcuts\n\nAgent-related operations can be triggered via keyboard shortcuts defined in `useWorkspaceShortcuts`:\n\n| Shortcut | Action |\n|----------|--------|\n| `v>d` | Toggle DevTools |\n| `v>p` | Toggle Preview Mode |\n| `v>s` | Toggle Left Sidebar |\n| `v>h` | Toggle Left Main Panel |\n| `x>p` | Git Create PR |\n| `x>m` | Git Merge |\n| `x>r` | Git Rebase |\n| `x>u` | Git Push |\n| `r>s` | Run Setup Script |\n| `r>c` | Run Cleanup Script |\n\n资料来源：[packages/web-core/src/shared/keyboard/useWorkspaceShortcuts.ts:1-30]()\n\n## Workspace Selection\n\nWhen linking an issue to a workspace, users can select from available workspaces or create new ones:\n\n```typescript\ninterface Workspace {\n id: string;\n name: string;\n branch: string;\n isArchived: boolean;\n filesChanged: number;\n linesAdded: number;\n linesRemoved: number;\n isRunning: boolean;\n isPinned: boolean;\n hasPendingApproval: boolean;\n hasRunningDevServer: boolean;\n hasUnseenActivity: boolean;\n latestProcessCompletedAt: Date | null;\n latestProcessStatus: string | null;\n prStatus: string | null;\n}\n```\n\n资料来源：[packages/web-core/src/shared/dialogs/command-bar/WorkspaceSelectionDialog.tsx:50-90]()\n\n## Executor Profile Configuration\n\nEach executor can be configured with specific profiles that define:\n\n- **Model Selection** - Which AI model to use (e.g., Claude 3.5 Sonnet, GPT-4)\n- **System Prompt** - Custom instructions for the agent\n- **Temperature** - Response randomness setting\n- **Max Tokens** - Response length limits\n\nProfiles are stored in `default_profiles.json` and can be selected per-workspace or globally.\n\n## Workflow Summary\n\n```mermaid\ngraph TD\n A[Create Kanban Issue] --> B[Open/Create Workspace]\n B --> C[Select Agent & Profile]\n C --> D[Start Agent Session]\n D --> E[Agent Reads Issue Context]\n E --> F[Agent Executes Tasks]\n F --> G[Changes Applied to Branch]\n G --> H[Review Diff in UI]\n H --> I{Changes Approved?}\n I -->|Yes| J[Create Pull Request]\n I -->|No| K[Send Feedback to Agent]\n K --> F\n J --> L[Merge PR]\n```\n\n## Related Components\n\n| Component | File Path | Role |\n|-----------|-----------|------|\n| `SessionChatBoxContainer` | `packages/web-core/src/features/workspace-chat/ui/` | Main agent interaction UI |\n| `ConversationListContainer` | `packages/web-core/src/features/workspace-chat/ui/` | Conversation message display |\n| `ProcessesTab` | `packages/web-core/src/shared/components/tasks/TaskDetails/` | Process monitoring |\n| `WorkspaceSelectionDialog` | `packages/web-core/src/shared/dialogs/command-bar/` | Workspace linking |\n| `useWorkspaceShortcuts` | `packages/web-core/src/shared/keyboard/` | Keyboard navigation |\n\n---\n\n\n\n## MCP Server Integration\n\n### 相关页面\n\n相关主题：[Coding Agent Executors](#page-executors), [Database and Data Models](#page-database-models)\n\nThe requested MCP-related source files were not included in the provided context. The `
    ` block references these files:\n\n- `crates/mcp/src/lib.rs`\n- `crates/mcp/src/task_server/mod.rs`\n- `crates/mcp/src/task_server/handler.rs`\n- `crates/mcp/src/task_server/tools/mod.rs`\n- `crates/executors/src/mcp_config.rs`\n- `crates/executors/default_mcp.json`\n\nHowever, **none of these files appear in the retrieved context**. The context only contains files from `packages/web-core`, `packages/ui`, `packages/remote-web`, and `crates/server`.\n\n**What I can see from the available context:**\n\nThe repository is a **TypeScript/JavaScript monorepo** with these visible packages:\n\n| Package | Path | Purpose |\n|---------|------|---------|\n| `web-core` | `packages/web-core/src/` | Core UI components, dialogs, stores, hooks |\n| `ui` | `packages/ui/src/` | Shared UI components (CommandBar, WorkspacesSidebar) |\n| `remote-web` | `packages/remote-web/src/` | HomePage, organization/project views |\n| `server` | `crates/server/src/` | Rust backend with OAuth routes |\n\nThe visible files show a **Kanban workspace management system** with:\n- Git integration dialogs (ForcePushDialog, ResolveConflictsDialog)\n- Command bar interface\n- Organization and project management\n- Process list handling\n- Workspace diff/comment tracking\n- Keyboard shortcuts for workspace operations\n\n**To generate the MCP Server Integration wiki page**, please provide the actual MCP-related source files from the `crates/mcp/` directory.\n\n---\n\n\n\n## Relay and Remote Access\n\n### 相关页面\n\n相关主题：[Crate Reference](#page-crate-reference), [Deployment and Infrastructure](#page-deployment-infrastructure)\n\n
    \n相关源码文件\n\n以下源码文件用于生成本页说明：\n\n- [crates/server/src/middleware/origin.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/server/src/middleware/origin.rs)\n- [packages/remote-web/src/app/layout/RemoteAppShell.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/remote-web/src/app/layout/RemoteAppShell.tsx)\n- [packages/web-core/src/shared/stores/useUiPreferencesStore.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/stores/useUiPreferencesStore.ts)\n- [packages/web-core/src/shared/hooks/useAzureAttachments.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/hooks/useAzureAttachments.ts)\n- [crates/server/src/error.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/server/src/error.rs)\n
    \n\n# Relay and Remote Access\n\n## Overview\n\nThe Relay and Remote Access system in Vibe Kanban enables secure, low-latency communication between local development environments and remote hosts. This system allows users to access their coding workspaces and development servers from anywhere while maintaining proper authentication and origin verification.\n\nThe relay architecture consists of multiple layers:\n\n- **Relay Tunnel** - Handles encrypted tunneled connections\n- **Relay WebRTC** - Provides peer-to-peer communication channels\n- **Relay Hosts** - Manages the registry and lifecycle of remote hosts\n- **Relay Protocol** - Defines the communication protocol between clients and hosts\n- **Relay Client** - Implements the client-side connection logic\n\n## Architecture\n\n### System Components\n\n| Component | Purpose | Location |\n|-----------|---------|----------|\n| Relay Tunnel | Encrypted tunnel establishment | `crates/relay-tunnel/src/lib.rs` |\n| Relay WebRTC | Peer-to-peer communication | `crates/relay-webrtc/src/lib.rs` |\n| Relay Hosts | Host registry and management | `crates/relay-hosts/src/lib.rs` |\n| Relay Protocol | Communication protocol definition | `crates/relay-protocol/src/lib.rs` |\n| Relay Client | Client-side connection logic | `crates/relay-client/src/lib.rs` |\n| Origin Middleware | Request origin verification | `crates/server/src/middleware/origin.rs` |\n\n### Connection Flow\n\n```mermaid\ngraph TD\n A[Client Browser] -->|HTTPS + Relay Header| B[Server Middleware]\n B -->|Verify Origin| C{Origin Valid?}\n C -->|Yes| D[Relay Host Lookup]\n C -->|No| E[403 Forbidden Response]\n D -->|Host Online| F[Establish WebSocket]\n D -->|Host Unpaired| G[Pairing Flow]\n F -->|Tunnel Established| H[Remote Workspace Access]\n G -->|Paired Successfully| F\n```\n\n## Origin Verification Middleware\n\nThe server implements an `origin.rs` middleware that validates all incoming requests to ensure they originate from legitimate sources.\n\n### Key Components\n\n**RELAY_HEADER Constant**\nThe relay header (`x-vibe-relay`) identifies requests coming through the relay system. When present with value `\"1\"`, the request is flagged as a relay request.\n\n资料来源：[crates/server/src/middleware/origin.rs:1-5]()\n\n**Header Retrieval Functions**\n\n| Function | Purpose |\n|----------|---------|\n| `get_host_header` | Extracts the `Host` header from a request |\n| `get_header` | Retrieves any specified header by name |\n| `is_relay_request` | Checks if request contains relay header |\n\n```rust\nfn is_relay_request(req: &Request) -> bool {\n req.headers()\n .get(RELAY_HEADER)\n .and_then(|v| v.to_str().ok())\n .is_some_and(|v| v.trim() == \"1\")\n}\n```\n\n资料来源：[crates/server/src/middleware/origin.rs:15-21]()\n\n**Host Normalization**\nThe `normalize_host` function standardizes host strings for consistent comparison:\n\n1. Trims whitespace and IPv6 brackets\n2. Converts to lowercase\n3. Converts `localhost` aliases to `\"localhost\"`\n4. Converts loopback IPs to `\"localhost\"`\n5. Returns normalized IP or hostname\n\n```rust\nfn normalize_host(host: &str) -> String {\n let trimmed = host.trim().trim_start_matches('[').trim_end_matches(']');\n let lower = trimmed.to_ascii_lowercase();\n if lower == \"localhost\" {\n return \"localhost\".to_string();\n }\n if let Ok(ip) = lower.parse::() {\n if ip.is_loopback() {\n return \"localhost\".to_string();\n }\n return ip.to_string();\n }\n lower\n}\n```\n\n资料来源：[crates/server/src/middleware/origin.rs:31-45]()\n\n**Origin Matching**\nThe `origin_matches_host` function validates that the request origin corresponds to the host header:\n\n```rust\nfn origin_matches_host(origin: &str, host: &str) -> bool {\n origin\n .strip_prefix(\"http://\")\n .or_else(|| origin.strip_prefix(\"https://\"))\n .is_some_and(|rest| rest.eq_ignore_ascii_case(host))\n}\n```\n\n资料来源：[crates/server/src/middleware/origin.rs:26-29]()\n\n### Forbidden Response\n\nWhen origin verification fails, the middleware returns a `403 Forbidden` response:\n\n```rust\nfn forbidden() -> Response {\n Response::builder()\n .status(StatusCode::FORBIDDEN)\n .body(Body::empty())\n .unwrap_or_else(|_| Response::new(Body::empty()))\n}\n```\n\n资料来源：[crates/server/src/middleware/origin.rs:23-25]()\n\n## Remote Host Management\n\n### Host Status Types\n\n| Status | Description | UI Behavior |\n|--------|-------------|-------------|\n| `online` | Host is connected and ready | Clickable, allows connection |\n| `unpaired` | Host exists but not authenticated | Clickable, triggers pairing |\n| Other | Host is offline or unavailable | Disabled, grayed out |\n\nThe UI displays host status with visual indicators:\n\n```tsx\nconst isOnline = host.status === \"online\";\nconst isUnpaired = host.status === \"unpaired\";\nconst isClickable = isOnline || isUnpaired;\n```\n\n资料来源：[packages/remote-web/src/app/layout/RemoteAppShell.tsx:1-50]()\n\n### Host Display\n\nHosts are rendered with status indicators using color coding:\n\n```tsx\n {\n handleHostClick(host.id, host.status);\n setIsDrawerOpen(false);\n}}\n```\n\n资料来源：[packages/remote-web/src/app/layout/RemoteAppShell.tsx:38-41]()\n\n## Relay Pairing System\n\n### Pairing Errors\n\nThe error handling system maps various pairing errors to appropriate HTTP responses:\n\n| Error Type | HTTP Status | Condition |\n|------------|-------------|-----------|\n| Authentication Failed | `401 Unauthorized` | Invalid credentials |\n| Pairing Failed | `400 Bad Request` | General pairing issue |\n| Serialization Error | `502 Bad Gateway` | Store serialization failure |\n| Storage Error | `502 Bad Gateway` | Persistence failure |\n\n```rust\nRelayPairingClientError::RemoteClient(ref inner) => {\n tracing::warn!(%inner, \"Relay host pairing authentication failed\");\n ApiError::Unauthorized\n}\nRelayPairingClientError::Pairing(ref detail) => {\n tracing::warn!(%detail, \"Relay host pairing failed\");\n ApiError::BadRequest(err.to_string())\n}\n```\n\n资料来源：[crates/server/src/error.rs:1-30]()\n\n### Unconfigured Relay\n\nWhen the relay API is not configured, the system returns:\n\n```rust\nfrom(_: RelayHostsNotConfigured) -> Self {\n ApiError::BadRequest(\"Remote relay API is not configured\".to_string())\n}\n```\n\n资料来源：[crates/server/src/error.rs:45-48]()\n\n## Attachment Upload via Relay\n\nThe relay system also handles file attachments when working remotely. The upload process involves:\n\n1. Initialize upload with Azure blob storage\n2. Upload chunks with progress tracking\n3. Confirm upload completion\n\n```typescript\nconst result = await confirmAttachmentUpload({\n project_id: projectId,\n upload_id: initResult.upload_id,\n filename: file.name,\n content_type: file.type,\n size_bytes: file.size,\n hash,\n issue_id: issueIdRef.current,\n comment_id: commentIdRef.current,\n});\n```\n\n资料来源：[packages/web-core/src/shared/hooks/useAzureAttachments.ts:1-50]()\n\n## Workspace Panel States\n\nThe relay system integrates with the workspace panel state management:\n\n```typescript\ntoggleLeftMainPanel: (workspaceId) => {\n if (!workspaceId) return;\n const state = get();\n const wsState = state.workspacePanelStates[workspaceId] ?? DEFAULT_WORKSPACE_PANEL_STATE;\n if (wsState.isLeftMainPanelVisible && wsState.rightMainPanelMode === null)\n return;\n set({\n workspacePanelStates: {\n ...state.workspacePanelStates,\n [workspaceId]: {\n ...wsState,\n isLeftMainPanelVisible: !wsState.isLeftMainPanelVisible,\n },\n },\n });\n},\n```\n\n资料来源：[packages/web-core/src/shared/stores/useUiPreferencesStore.ts:1-40]()\n\n## Security Considerations\n\n### CORS and Origin Validation\n\nAll relay requests undergo strict origin validation:\n\n1. Requests must include a valid `Origin` header\n2. The origin must match the `Host` header (with protocol prefix stripped)\n3. Relay requests are identified via the `x-vibe-relay` header\n4. Loopback addresses and `localhost` are normalized for consistent comparison\n\n### Authentication Flow\n\n```mermaid\nsequenceDiagram\n participant C as Client\n participant S as Server\n participant R as Relay Host\n \n C->>S: Request with x-vibe-relay: 1\n S->>S: Validate Origin matches Host\n alt Valid Request\n S->>R: Relay connection\n R-->>C: Authenticated tunnel\n else Invalid Origin\n S-->>C: 403 Forbidden\n end\n```\n\n## Configuration\n\n### Environment Variables\n\n| Variable | Purpose |\n|----------|---------|\n| `RELAY_API_URL` | Base URL for relay API |\n| `RELAY_API_KEY` | Authentication key for relay |\n| `ALLOWED_ORIGINS` | Comma-separated list of allowed origins |\n\n### Default Port Resolution\n\nThe system includes logic for determining default ports based on HTTPS configuration:\n\n```rust\nfn default_port(https: bool)\n```\n\n资料来源：[crates/server/src/middleware/origin.rs:50]()\n\n## Troubleshooting\n\n### Common Issues\n\n| Issue | Cause | Resolution |\n|-------|-------|------------|\n| 403 Forbidden on relay requests | Origin mismatch | Check `Origin` and `Host` headers |\n| Host shows as \"offline\" | Network connectivity | Verify host is running and connected |\n| Pairing fails | Authentication error | Re-authenticate the relay host |\n| Slow connection | High latency | Check network conditions, consider WebRTC fallback |\n\n### Diagnostic Steps\n\n1. Verify the `x-vibe-relay` header is present in requests\n2. Check server logs for relay-related warnings and errors\n3. Confirm host status in the Remote App Shell UI\n4. Validate origin normalization with `normalize_host()` function\n\n---\n\n\n\n## Database and Data Models\n\n### 相关页面\n\n相关主题：[Backend Architecture](#page-backend-architecture), [Key Concepts](#page-key-concepts)\n\n
    \n相关源码文件\n\n以下源码文件用于生成本页说明：\n\n- [crates/db/src/lib.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/db/src/lib.rs)\n- [crates/db/src/models/mod.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/db/src/models/mod.rs)\n- [crates/db/src/models/workspace.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/db/src/models/workspace.rs)\n- [crates/db/src/models/session.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/db/src/models/session.rs)\n- [crates/db/src/models/task.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/db/src/models/task.rs)\n- [crates/db/src/models/project.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/db/src/models/project.rs)\n- [crates/db/src/models/repo.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/db/src/models/repo.rs)\n- [crates/api-types/src/lib.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/api-types/src/lib.rs)\n
    \n\n# Database and Data Models\n\n## Overview\n\nVibe Kanban uses a Rust-based database layer (`crates/db`) for persistent storage, with shared API types defined in `crates/api-types`. The architecture separates concerns between the database implementation, business logic, and the web frontend, enabling type-safe data flow across the application.\n\n## Architecture Overview\n\n```mermaid\ngraph TD\n A[Web Frontend
    packages/web-core] --> B[API Types
    crates/api-types]\n C[Remote Web
    packages/remote-web] --> B\n B --> D[Database Layer
    crates/db]\n D --> E[(SQLite
    Database)]\n F[Server
    crates/server] --> D\n```\n\n## Core Data Models\n\n### Workspace Model\n\nThe workspace model represents a coding agent execution environment. Each workspace is associated with a specific branch, terminal session, and dev server configuration.\n\n| Field | Type | Description |\n|-------|------|-------------|\n| `id` | UUID | Unique identifier for the workspace |\n| `name` | String | Display name of the workspace |\n| `project_id` | UUID | Associated project reference |\n| `branch_name` | String | Git branch name |\n| `is_running` | Boolean | Whether the agent is currently executing |\n| `is_pinned` | Boolean | Whether the workspace is pinned |\n| `has_pending_approval` | Boolean | Indicates pending approval state |\n| `has_running_dev_server` | Boolean | Whether dev server is active |\n| `has_unseen_activity` | Boolean | New activity since last view |\n| `files_changed` | Integer | Count of modified files |\n| `lines_added` | Integer | Lines of code added |\n| `lines_removed` | Integer | Lines of code removed |\n| `latest_process_completed_at` | Timestamp | Last process completion time |\n| `latest_process_status` | Enum | Current process status |\n\n资料来源：[crates/db/src/models/workspace.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/db/src/models/workspace.rs)\n\n### Session Model\n\nSessions represent individual coding agent execution runs within a workspace.\n\n| Field | Type | Description |\n|-------|------|-------------|\n| `id` | UUID | Unique session identifier |\n| `workspace_id` | UUID | Parent workspace reference |\n| `started_at` | Timestamp | Session start time |\n| `completed_at` | Timestamp | Session end time (nullable) |\n| `status` | Enum | Session state (running, completed, failed) |\n\n资料来源：[crates/db/src/models/session.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/db/src/models/session.rs)\n\n### Task Model\n\nTasks (issues) are the fundamental unit of work in the kanban system.\n\n| Field | Type | Description |\n|-------|------|-------------|\n| `id` | UUID | Unique task identifier |\n| `simple_id` | String | Human-readable ID (e.g., \"PROJ-123\") |\n| `title` | String | Task title |\n| `description` | Text | Detailed description |\n| `status_id` | UUID | Current status column |\n| `priority_id` | UUID | Priority level |\n| `assignee_id` | UUID | Assigned user (nullable) |\n| `project_id` | UUID | Parent project |\n| `created_at` | Timestamp | Creation time |\n| `updated_at` | Timestamp | Last modification time |\n\n资料来源：[crates/db/src/models/task.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/db/src/models/task.rs)\n\n### Project Model\n\nProjects organize tasks and workspaces into logical units.\n\n| Field | Type | Description |\n|-------|------|-------------|\n| `id` | UUID | Unique project identifier |\n| `name` | String | Project name |\n| `color` | String | Display color (hex format) |\n| `organization_id` | UUID | Parent organization |\n| `created_at` | Timestamp | Creation time |\n| `updated_at` | Timestamp | Last modification time |\n\n资料来源：[crates/db/src/models/project.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/db/src/models/project.rs)\n\n### Repository Model\n\nRepository configurations link external Git repositories to the system.\n\n| Field | Type | Description |\n|-------|------|-------------|\n| `id` | UUID | Unique repository identifier |\n| `display_name` | String | Repository display name |\n| `clone_url` | String | Git clone URL |\n| `default_branch` | String | Primary branch name |\n| `is_current` | Boolean | Currently checked out |\n\n资料来源：[crates/db/src/models/repo.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/db/src/models/repo.rs)\n\n## API Types System\n\nThe `crates/api-types` crate defines shared TypeScript types used across the frontend packages. These types ensure type safety between the server and client applications.\n\n### Key Type Exports\n\nThe API types module re-exports types from the database models and extends them with frontend-specific metadata:\n\n```typescript\n// Shared type definitions for workspace state\ninterface WorkspaceState {\n workspaceId: string;\n branchName: string;\n filesChanged: number;\n linesAdded: number;\n linesRemoved: number;\n isRunning: boolean;\n isPinned: boolean;\n hasPendingApproval: boolean;\n hasRunningDevServer: boolean;\n hasUnseenActivity: boolean;\n latestProcessCompletedAt: string | null;\n latestProcessStatus: ProcessStatus;\n prStatus: PRStatus | null;\n}\n```\n\n资料来源：[crates/api-types/src/lib.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/api-types/src/lib.rs)\n\n## State Management Integration\n\n### Workspace Diff Store\n\nThe frontend uses Zustand stores to manage client-side state that syncs with the database models.\n\n```typescript\n// From packages/web-core/src/shared/stores/useWorkspaceDiffStore.ts\nexport const useGetGitHubCommentCountForFile = () =>\n useWorkspaceDiffStore((s) => s.getGitHubCommentCountForFile);\n\nexport const useGetFilesWithGitHubComments = () =>\n useWorkspaceDiffStore((s) => s.getFilesWithGitHubComments);\n```\n\n### UI Preferences Store\n\nUser interface preferences are persisted and managed through a dedicated store:\n\n| Preference | Type | Description |\n|------------|------|-------------|\n| `layoutMode` | 'workspaces' \\| 'kanban' | Active layout view |\n| `isLeftSidebarVisible` | Boolean | Left sidebar visibility |\n| `isRightSidebarVisible` | Boolean | Right sidebar visibility |\n| `isTerminalVisible` | Boolean | Terminal panel visibility |\n| `paneSizes` | Record | Customizable panel dimensions |\n| `collapsedPaths` | Record | Expanded/collapsed tree states |\n\n资料来源：[packages/web-core/src/shared/stores/useUiPreferencesStore.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/stores/useUiPreferencesStore.ts)\n\n## Data Flow Architecture\n\n```mermaid\ngraph LR\n A[User Action] --> B[React Component]\n B --> C[Zustand Store]\n C --> D[API Client]\n D --> E[Rust Server
    crates/server]\n E --> F[Database Layer
    crates/db]\n F --> G[(SQLite)]\n G --> F\n F --> E\n E --> D\n D --> C\n C --> B\n```\n\n## Relationships Between Models\n\n```mermaid\nerDiagram\n PROJECT ||--o{ TASK : contains\n PROJECT ||--o{ WORKSPACE : contains\n PROJECT ||--o{ REPO : links\n TASK ||--o{ SESSION : executes\n WORKSPACE ||--o{ SESSION : contains\n REPO ||--o{ WORKSPACE : checked_out\n```\n\n## Database Module Structure\n\nThe database crate (`crates/db`) is organized into the following modules:\n\n| Module | Purpose |\n|--------|---------|\n| `lib.rs` | Main entry point, exports all models and database operations |\n| `models/mod.rs` | Model aggregation and re-exports |\n| `models/workspace.rs` | Workspace entity definition |\n| `models/session.rs` | Session entity definition |\n| `models/task.rs` | Task/Issue entity definition |\n| `models/project.rs` | Project entity definition |\n| `models/repo.rs` | Repository entity definition |\n\n资料来源：[crates/db/src/lib.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/db/src/lib.rs), [crates/db/src/models/mod.rs](https://github.com/BloopAI/vibe-kanban/blob/main/crates/db/src/models/mod.rs)\n\n## Attachment Management\n\nThe system supports file attachments associated with tasks and comments:\n\n| Attachment Field | Type | Description |\n|------------------|------|-------------|\n| `id` | UUID | Unique attachment identifier |\n| `filename` | String | Original filename |\n| `blob_id` | String | Storage reference |\n| `upload_progress` | Integer | Upload percentage (0-100) |\n| `pending_status` | Enum | confirming, uploaded, failed |\n| `content_type` | String | MIME type |\n| `size_bytes` | Integer | File size |\n\n资料来源：[packages/web-core/src/shared/hooks/useAzureAttachments.ts](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/hooks/useAzureAttachments.ts)\n\n## Process Tracking\n\nThe system tracks coding agent processes with the following states:\n\n| Status | Description |\n|--------|-------------|\n| `started` | Process initiated |\n| `running` | Currently executing |\n| `completed` | Successfully finished |\n| `failed` | Execution error |\n| `cancelled` | User terminated |\n\n资料来源：[packages/web-core/src/shared/components/tasks/TaskDetails/ProcessesTab.tsx](https://github.com/BloopAI/vibe-kanban/blob/main/packages/web-core/src/shared/components/tasks/TaskDetails/ProcessesTab.tsx)\n\n## Summary\n\nThe Vibe Kanban database layer provides a type-safe, Rust-based persistence system with clear separation between:\n\n1. **Core Entities**: Workspace, Session, Task, Project, and Repository models define the data structure\n2. **API Types**: Shared TypeScript types ensure consistency across frontend packages\n3. **State Management**: Zustand stores provide reactive client-side state synchronized with server data\n4. **Relationships**: Well-defined foreign key relationships enable complex queries and data navigation\n\nThis architecture enables the application to manage coding agent workflows efficiently while maintaining data integrity and type safety throughout the stack.\n\n---\n\n\n\n## Deployment and Infrastructure\n\n### 相关页面\n\n相关主题：[Relay and Remote Access](#page-relay-remote-access), [Development Setup](#page-development-setup)\n\n
    \nRelated Source Files\n\n以下源码文件用于生成本页说明：\n\n- [Dockerfile](https://github.com/BloopAI/vibe-kanban/blob/main/Dockerfile)\n- [Caddyfile.example](https://github.com/BloopAI/vibe-kanban/blob/main/Caddyfile.example)\n- [crates/remote/Dockerfile](https://github.com/BloopAI/vibe-kanban/blob/main/crates/remote/Dockerfile)\n- [crates/relay-tunnel/Dockerfile](https://github.com/BloopAI/vibe-kanban/blob/main/crates/relay-tunnel/Dockerfile)\n- [docs/self-hosting/deploy-docker.mdx](https://github.com/BloopAI/vibe-kanban/blob/main/docs/self-hosting/deploy-docker.mdx)\n- [docs/self-hosting/local-development.mdx](https://github.com/BloopAI/vibe-kanban/blob/main/docs/self-hosting/local-development.mdx)\n
    \n\n# Deployment and Infrastructure\n\n## Overview\n\nVibe Kanban provides flexible deployment options ranging from local development to production-grade Docker-based self-hosting. The infrastructure supports both single-machine deployments and distributed architectures with optional relay tunneling for remote access. 资料来源：[README.md:1-60]()\n\nThe project uses a monorepo structure with the following key deployment components:\n\n| Component | Technology | Purpose |\n|-----------|------------|---------|\n| Web UI | React/TypeScript | Frontend application |\n| API Server | Rust (Axum) | Backend REST API |\n| Database | PostgreSQL | Primary data store |\n| Relay Tunnel | Rust | Secure remote access |\n| TLS Termination | Caddy | HTTPS reverse proxy |\n\n## Architecture Overview\n\nVibe Kanban's deployment architecture consists of multiple Docker containers orchestrated via Docker Compose. The system supports three deployment profiles: default, relay, and attachments.\n\n```mermaid\ngraph TD\n User([User Browser]) --> Caddy[Caddy Reverse Proxy]\n Caddy --> RemoteWeb[remote-web:3001]\n Caddy --> RemoteServer[remote-server:3000]\n \n RemoteServer --> Electric[(Electric SQL
    PostgreSQL)]\n RemoteServer --> Azurite[(Azurite
    Blob Storage)]\n \n RemoteWeb -->|WebSocket| RelayTunnel[relay-tunnel:8082]\n User -->|Secure Tunnel| RelayTunnel\n \n subgraph Docker Network\n Caddy\n RemoteWeb\n RemoteServer\n Electric\n Azurite\n RelayTunnel\n end\n```\n\n### Component Responsibilities\n\n| Service | Port | Description |\n|---------|------|-------------|\n| `remote-web` | 3001 | Remote web UI and API gateway |\n| `remote-server` | 3000 | Core API server with business logic |\n| `electric` | 5433 | PostgreSQL with Electric SQL sync |\n| `relay-tunnel` | 8082 | WebSocket relay for remote access |\n| `azurite` | 10000 | Local Azure Blob Storage emulator |\n\n## Docker Deployment\n\n### Prerequisites\n\n- Docker Engine 24.0+\n- Docker Compose v2.20+\n- Minimum 4GB RAM available\n- 10GB disk space\n\n### Quick Start\n\nClone the repository and navigate to the remote deployment directory:\n\n```bash\ncd crates/remote\ndocker compose --env-file .env.remote up --build\n```\n\nThis starts the default stack with web UI, API server, and database.\n\n### Starting the Development Stack\n\nFrom the repository root:\n\n```bash\npnpm run remote:dev\n```\n\nFor full stack with relay and local attachment storage:\n\n```bash\npnpm run remote:dev:full\n```\n\nEquivalent manual command:\n\n```bash\ncd crates/remote\ndocker compose --env-file .env.remote --profile relay --profile attachments up --build\n```\n\n资料来源：[crates/remote/README.md:45-70]()\n\n## Environment Configuration\n\n### Required Environment Variables\n\n| Variable | Description | Example |\n|----------|-------------|---------|\n| `DATABASE_URL` | PostgreSQL connection string | `postgres://remote:remote@localhost:5433/remote` |\n| `JWT_SECRET` | Secret for JWT token signing | Base64 encoded 48-byte string |\n| `VK_SHARED_API_BASE` | Internal API base URL | `http://localhost:3000` |\n| `VK_SHARED_RELAY_API_BASE` | Relay API base URL | `http://relay.localhost:3001` |\n\n### Generating JWT Secret\n\nGenerate a secure JWT secret using OpenSSL:\n\n```bash\nopenssl rand -base64 48\n```\n\n### OAuth Configuration\n\nConfigure OAuth callback URLs for external authentication:\n\n| Provider | Callback URL |\n|----------|--------------|\n| GitHub | `https://localhost:3001/v1/oauth/github/callback` |\n| Google | `https://localhost:3001/v1/oauth/google/callback` |\n\n资料来源：[crates/remote/README.md:1-50]()\n\n## Docker Compose Profiles\n\nVibe Kanban uses Docker Compose profiles to enable optional components:\n\n### Default Profile\n\nStarts core infrastructure only:\n\n```bash\ncd crates/remote\ndocker compose --env-file .env.remote up --build\n```\n\nServices started:\n- `remote-db` (PostgreSQL via Electric SQL)\n- `remote-server`\n- `remote-web`\n\n### Relay Profile\n\nEnables remote access via WebSocket tunnel:\n\n```bash\ncd crates/remote\ndocker compose --env-file .env.remote --profile relay up --build\n```\n\nAdditional service:\n- `relay-tunnel` on port 8082\n\n### Attachments Profile\n\nEnables local file storage using Azurite:\n\n```bash\ncd crates/remote\ndocker compose --env-file .env.remote --profile attachments up --build\n```\n\nAdditional service:\n- `azurite` on ports 10000/10001/10002\n\n### Combined Profiles\n\nEnable both relay and attachments:\n\n```bash\ncd crates/remote\ndocker compose --env-file .env.remote --profile relay --profile attachments up --build\n```\n\n## Local HTTPS with Caddy\n\nFor development environments requiring HTTPS, Caddy serves as a reverse proxy with automatic TLS certificate management.\n\n### Install Caddy\n\n**macOS:**\n```bash\nbrew install caddy\n```\n\n**Debian/Ubuntu:**\n```bash\nsudo apt install caddy\n```\n\n### Configuration\n\nThe repository includes `Caddyfile.example` with the required routing configuration. Start Caddy from the repository root:\n\n```bash\ncaddy run --config Caddyfile.example\n```\n\nOn first run, Caddy installs a local CA certificate and may prompt for administrator password.\n\n### Endpoint Routing\n\n| External URL | Internal Service |\n|--------------|------------------|\n| `https://localhost:3001` | Remote web UI/API |\n| `https://relay.localhost:3001` | Relay API |\n\n资料来源：[crates/remote/README.md:15-45]()\n\n### Health Check Endpoints\n\nVerify deployment health:\n\n```bash\ncurl -sk https://localhost:3001/v1/health\ncurl -sk https://relay.localhost:3001/health\n```\n\nIf the relay health endpoint returns HTML instead of `{\"status\":\"ok\"}`, the Caddy host routing configuration is incorrect.\n\n## Database Infrastructure\n\n### Electric SQL with PostgreSQL\n\nVibe Kanban uses Electric SQL for database synchronization, providing:\n- Real-time data sync across instances\n- Offline-first capability\n- PostgreSQL compatibility\n\n### Connection Configuration\n\n| Setting | Default Value |\n|---------|---------------|\n| Host | `localhost` |\n| Port | `5433` |\n| Database | `remote` |\n| Username | `remote` |\n| Password | `remote` |\n\n### Container Networking\n\nAll services communicate through the Docker bridge network, with the database accessible only to internal services.\n\n## Relay Tunnel Service\n\nThe relay tunnel enables secure remote access to Vibe Kanban when deployed behind NAT or firewalls.\n\n```mermaid\nsequenceDiagram\n participant Client as Remote Client\n participant Relay as relay-tunnel:8082\n participant WebUI as remote-web:3001\n participant Server as remote-server:3000\n \n Client->>Relay: WebSocket Connection\n Relay->>WebUI: Forward WebSocket\n WebUI->>Server: API Request\n Server-->>WebUI: Response\n WebUI-->>Relay: WebSocket Response\n Relay-->>Client: Tunneled Response\n```\n\n### Requirements\n\n- `relay` profile enabled in Docker Compose\n- `VK_SHARED_RELAY_API_BASE` environment variable set\n- Caddy configured with `relay.localhost:3001` route\n\n## Attachment Storage\n\n### Azure Blob Storage (Production)\n\nProduction deployments should configure Azure Blob Storage for file attachments:\n\n| Setting | Description |\n|---------|-------------|\n| Account Name | Azure storage account name |\n| Account Key | Azure storage access key |\n| Container | Blob container name |\n| Endpoint | Azure blob endpoint URL |\n\n### Azurite (Development)\n\nLocal development uses Azurite, an Azure Storage emulator:\n\n```yaml\nazurite:\n image: mcr.microsoft.com/azure-storage/azurite\n ports:\n - \"10000:10000\" # Blob service\n - \"10001:10001\" # Queue service\n - \"10002:10002\" # Table service\n```\n\n资料来源：[crates/remote/README.md:70-95]()\n\n## API Endpoints Reference\n\n### Health Check Endpoints\n\n| Endpoint | Method | Description |\n|----------|--------|-------------|\n| `/v1/health` | GET | API server health status |\n| `/health` | GET | Relay tunnel health status |\n\n### OAuth Endpoints\n\n| Endpoint | Provider |\n|----------|----------|\n| `/v1/oauth/github/callback` | GitHub |\n| `/v1/oauth/google/callback` | Google |\n\n## Deployment States\n\n```mermaid\nstateDiagram-v2\n [*] --> Initializing\n Initializing --> StartingServices: docker compose up\n StartingServices --> DatabaseReady: PostgreSQL online\n DatabaseReady --> APIServerReady: Server responding\n APIServerReady --> WebUIAvailable: UI accessible\n WebUIAvailable --> RelayEnabled: relay profile active\n RelayEnabled --> [*]: Services running\n \n Initializing --> Failed: Container error\n StartingServices --> Failed: Port conflict\n APIServerReady --> Degraded: Health check failing\n Degraded --> APIServerReady: Auto-recovery\n Failed --> Initializing: Restart triggered\n```\n\n## Development vs Production\n\n### Development Stack\n\n| Aspect | Setting |\n|--------|---------|\n| TLS | Self-signed or Caddy |\n| Storage | Azurite emulator |\n| Database | Local Electric SQL |\n| Access | Local network only |\n| Debugging | Full logging enabled |\n\n### Production Stack\n\n| Aspect | Setting |\n|--------|---------|\n| TLS | Let's Encrypt or managed certificate |\n| Storage | Azure Blob Storage |\n| Database | Managed PostgreSQL or Electric SQL Cloud |\n| Access | VPN or secure tunnel |\n| Debugging | Structured logging with levels |\n\n## Troubleshooting\n\n### Container Startup Failures\n\n1. Check port availability:\n ```bash\n lsof -i :3000 -i :3001 -i :5433 -i :8082\n ```\n\n2. Verify environment variables are set:\n ```bash\n docker compose --env-file .env.remote config\n ```\n\n3. Check container logs:\n ```bash\n docker compose --env-file .env.remote logs -f\n ```\n\n### Database Connection Issues\n\n1. Ensure database container is healthy:\n ```bash\n docker compose ps remote-db\n ```\n\n2. Test connection manually:\n ```bash\n psql \"postgres://remote:remote@localhost:5433/remote\"\n ```\n\n### Relay Tunnel Not Working\n\n1. Verify Caddy routing for `relay.localhost`:\n ```bash\n curl -sk https://relay.localhost:3001/health\n ```\n\n2. Check relay container logs:\n ```bash\n docker compose logs relay-tunnel\n ```\n\n3. Ensure firewall allows WebSocket connections on port 8082\n\n### OAuth Configuration Errors\n\nEnsure OAuth callback URLs in your provider settings match exactly:\n\n- Protocol: `https://` (not `http://`)\n- Port: `3001` (unless custom configured)\n- Path: `/v1/oauth/{provider}/callback`\n\n## Security Considerations\n\n### Network Isolation\n\nAll internal services communicate within the Docker network without exposure to the host:\n\n```yaml\nnetworks:\n default:\n driver: bridge\n internal: false\n```\n\n### Secret Management\n\n- Never commit `.env.remote` to version control\n- Use Docker secrets for production deployments\n- Rotate `JWT_SECRET` periodically\n\n### TLS Requirements\n\n- Use HTTPS in all production deployments\n- Configure Caddy with valid certificates for OAuth providers\n- Some OAuth providers require HTTPS callback URLs\n\n---\n\n---\n\n## Doramagic 踩坑日志\n\n项目：BloopAI/vibe-kanban\n\n摘要：发现 19 个潜在踩坑项，其中 3 个为 high/blocking；最高优先级：安装坑 - 来源证据：Deployment(Other(Migration failed: error returned from database: (code: 1) no such column: ep.session_id))。\n\n## 1. 安装坑 · 来源证据：Deployment(Other(Migration failed: error returned from database: (code: 1) no such column: ep.session_id))\n\n- 严重度：high\n- 证据强度：source_linked\n- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Deployment(Other(Migration failed: error returned from database: (code: 1) no such column: ep.session_id))\n- 对用户的影响：可能影响升级、迁移或版本选择。\n- 建议检查：来源问题仍为 open，Pack Agent 需要复核是否仍影响当前版本。\n- 防护动作：不得脱离来源链接放大为确定性结论；需要标注适用版本和复核状态。\n- 证据：community_evidence:github | cevd_b34b2ea1b35a4dc2a4a0eb0681bdb883 | https://github.com/BloopAI/vibe-kanban/issues/2972 | 来源讨论提到 windows 相关条件，需在安装/试用前复核。\n\n## 2. 配置坑 · 来源证据：Support for self-hosted projects and better export\n\n- 严重度：high\n- 证据强度：source_linked\n- 发现：GitHub 社区证据显示该项目存在一个配置相关的待验证问题：Support for self-hosted projects and better export\n- 对用户的影响：可能阻塞安装或首次运行。\n- 建议检查：来源问题仍为 open，Pack Agent 需要复核是否仍影响当前版本。\n- 防护动作：不得脱离来源链接放大为确定性结论；需要标注适用版本和复核状态。\n- 证据：community_evidence:github | cevd_19d27caa9e34416a9f282869f76624b0 | https://github.com/BloopAI/vibe-kanban/issues/3396 | 来源类型 github_issue 暴露的待验证使用条件。\n\n## 3. 安全/权限坑 · 来源证据：[Proposal] JIRA Integration for Vibe Kanban\n\n- 严重度：high\n- 证据强度：source_linked\n- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：[Proposal] JIRA Integration for Vibe Kanban\n- 对用户的影响：可能影响授权、密钥配置或安全边界。\n- 建议检查：来源问题仍为 open，Pack Agent 需要复核是否仍影响当前版本。\n- 防护动作：不得脱离来源链接放大为确定性结论；需要标注适用版本和复核状态。\n- 证据：community_evidence:github | cevd_ab38fe97c4574e2da01ddedd71a4fbac | https://github.com/BloopAI/vibe-kanban/issues/2424 | 来源类型 github_issue 暴露的待验证使用条件。\n\n## 4. 安装坑 · 来源证据：Pre-release v0.1.40-20260401153532\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Pre-release v0.1.40-20260401153532\n- 对用户的影响：可能阻塞安装或首次运行。\n- 建议检查：来源显示可能已有修复、规避或版本变化，说明书中必须标注适用版本。\n- 防护动作：不得脱离来源链接放大为确定性结论；需要标注适用版本和复核状态。\n- 证据：community_evidence:github | cevd_f4b99d437a4f4fd4989d2b3ef036553b | https://github.com/BloopAI/vibe-kanban/releases/tag/v0.1.40-20260401153532 | 来源讨论提到 docker 相关条件，需在安装/试用前复核。\n\n## 5. 安装坑 · 来源证据：Release v0.1.36\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Release v0.1.36\n- 对用户的影响：可能阻塞安装或首次运行。\n- 建议检查：来源显示可能已有修复、规避或版本变化，说明书中必须标注适用版本。\n- 防护动作：不得脱离来源链接放大为确定性结论；需要标注适用版本和复核状态。\n- 证据：community_evidence:github | cevd_527645be4e3f438e81757ef265a70d79 | https://github.com/BloopAI/vibe-kanban/releases/tag/v0.1.36-20260323174633 | 来源讨论提到 npm 相关条件，需在安装/试用前复核。\n\n## 6. 安装坑 · 来源证据：Release v0.1.43\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Release v0.1.43\n- 对用户的影响：可能增加新用户试用和生产接入成本。\n- 建议检查：来源显示可能已有修复、规避或版本变化，说明书中必须标注适用版本。\n- 防护动作：不得脱离来源链接放大为确定性结论；需要标注适用版本和复核状态。\n- 证据：community_evidence:github | cevd_53704dc7171446fe86b2017f72212ddc | https://github.com/BloopAI/vibe-kanban/releases/tag/v0.1.43-20260417125614 | 来源讨论提到 node 相关条件，需在安装/试用前复核。\n\n## 7. 配置坑 · 可能修改宿主 AI 配置\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：项目面向 Claude/Cursor/Codex/Gemini/OpenCode 等宿主，或安装命令涉及用户配置目录。\n- 对用户的影响：安装可能改变本机 AI 工具行为，用户需要知道写入位置和回滚方法。\n- 建议检查：列出会写入的配置文件、目录和卸载/回滚步骤。\n- 防护动作：涉及宿主配置目录时必须给回滚路径，不能只给安装命令。\n- 证据：capability.host_targets | github_repo:1002125012 | https://github.com/BloopAI/vibe-kanban | host_targets=claude, claude_code\n\n## 8. 能力坑 · 能力判断依赖假设\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：README/documentation is current enough for a first validation pass.\n- 对用户的影响：假设不成立时，用户拿不到承诺的能力。\n- 建议检查：将假设转成下游验证清单。\n- 防护动作：假设必须转成验证项；没有验证结果前不能写成事实。\n- 证据：capability.assumptions | github_repo:1002125012 | https://github.com/BloopAI/vibe-kanban | README/documentation is current enough for a first validation pass.\n\n## 9. 运行坑 · 来源证据：Pre-release v0.1.39-20260331145823\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：GitHub 社区证据显示该项目存在一个运行相关的待验证问题：Pre-release v0.1.39-20260331145823\n- 对用户的影响：可能阻塞安装或首次运行。\n- 建议检查：来源显示可能已有修复、规避或版本变化，说明书中必须标注适用版本。\n- 防护动作：不得脱离来源链接放大为确定性结论；需要标注适用版本和复核状态。\n- 证据：community_evidence:github | cevd_c005a56959634369929ce33eddbdc103 | https://github.com/BloopAI/vibe-kanban/releases/tag/v0.1.39-20260331145823 | 来源讨论提到 windows 相关条件，需在安装/试用前复核。\n\n## 10. 维护坑 · 来源证据：[Request] Support RDS for self hosting in AWS\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：GitHub 社区证据显示该项目存在一个维护/版本相关的待验证问题：[Request] Support RDS for self hosting in AWS\n- 对用户的影响：可能影响升级、迁移或版本选择。\n- 建议检查：来源问题仍为 open，Pack Agent 需要复核是否仍影响当前版本。\n- 防护动作：不得脱离来源链接放大为确定性结论；需要标注适用版本和复核状态。\n- 证据：community_evidence:github | cevd_f613b792c20942519560c0a286a82005 | https://github.com/BloopAI/vibe-kanban/issues/3405 | 来源类型 github_issue 暴露的待验证使用条件。\n\n## 11. 维护坑 · 维护活跃度未知\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：未记录 last_activity_observed。\n- 对用户的影响：新项目、停更项目和活跃项目会被混在一起，推荐信任度下降。\n- 建议检查：补 GitHub 最近 commit、release、issue/PR 响应信号。\n- 防护动作：维护活跃度未知时，推荐强度不能标为高信任。\n- 证据：evidence.maintainer_signals | github_repo:1002125012 | https://github.com/BloopAI/vibe-kanban | last_activity_observed missing\n\n## 12. 安全/权限坑 · 下游验证发现风险项\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：no_demo\n- 对用户的影响：下游已经要求复核，不能在页面中弱化。\n- 建议检查：进入安全/权限治理复核队列。\n- 防护动作：下游风险存在时必须保持 review/recommendation 降级。\n- 证据：downstream_validation.risk_items | github_repo:1002125012 | https://github.com/BloopAI/vibe-kanban | no_demo; severity=medium\n\n## 13. 安全/权限坑 · 存在安全注意事项\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：No sandbox install has been executed yet; downstream must verify before user use.\n- 对用户的影响：用户安装前需要知道权限边界和敏感操作。\n- 建议检查：转成明确权限清单和安全审查提示。\n- 防护动作：安全注意事项必须面向用户前置展示。\n- 证据：risks.safety_notes | github_repo:1002125012 | https://github.com/BloopAI/vibe-kanban | No sandbox install has been executed yet; downstream must verify before user use.\n\n## 14. 安全/权限坑 · 存在评分风险\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：no_demo\n- 对用户的影响：风险会影响是否适合普通用户安装。\n- 建议检查：把风险写入边界卡，并确认是否需要人工复核。\n- 防护动作：评分风险必须进入边界卡，不能只作为内部分数。\n- 证据：risks.scoring_risks | github_repo:1002125012 | https://github.com/BloopAI/vibe-kanban | no_demo; severity=medium\n\n## 15. 安全/权限坑 · 来源证据：Issue: Unclear Git + Bitbucket Setup for Vibe-Kanban (OpenCode) in Docker\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：Issue: Unclear Git + Bitbucket Setup for Vibe-Kanban (OpenCode) in Docker\n- 对用户的影响：可能影响升级、迁移或版本选择。\n- 建议检查：来源问题仍为 open，Pack Agent 需要复核是否仍影响当前版本。\n- 防护动作：不得脱离来源链接放大为确定性结论；需要标注适用版本和复核状态。\n- 证据：community_evidence:github | cevd_7d289a7b68ee4299ae4a5e54b0e64e35 | https://github.com/BloopAI/vibe-kanban/issues/3410 | 来源讨论提到 docker 相关条件，需在安装/试用前复核。\n\n## 16. 安全/权限坑 · 来源证据：Pre-release v0.1.37-20260327101540\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：Pre-release v0.1.37-20260327101540\n- 对用户的影响：可能影响授权、密钥配置或安全边界。\n- 建议检查：来源显示可能已有修复、规避或版本变化，说明书中必须标注适用版本。\n- 防护动作：不得脱离来源链接放大为确定性结论；需要标注适用版本和复核状态。\n- 证据：community_evidence:github | cevd_d648fba4c94b4791ac2e7683f6cb1361 | https://github.com/BloopAI/vibe-kanban/releases/tag/v0.1.37-20260327101540 | 来源讨论提到 macos 相关条件，需在安装/试用前复核。\n\n## 17. 安全/权限坑 · 来源证据：remote-v0.1.26\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：remote-v0.1.26\n- 对用户的影响：可能影响授权、密钥配置或安全边界。\n- 建议检查：来源显示可能已有修复、规避或版本变化，说明书中必须标注适用版本。\n- 防护动作：不得脱离来源链接放大为确定性结论；需要标注适用版本和复核状态。\n- 证据：community_evidence:github | cevd_3f212752e8c142d68ffe2993ac23dd37 | https://github.com/BloopAI/vibe-kanban/releases/tag/remote-v0.1.26 | 来源讨论提到 macos 相关条件，需在安装/试用前复核。\n\n## 18. 维护坑 · issue/PR 响应质量未知\n\n- 严重度：low\n- 证据强度：source_linked\n- 发现：issue_or_pr_quality=unknown。\n- 对用户的影响：用户无法判断遇到问题后是否有人维护。\n- 建议检查：抽样最近 issue/PR，判断是否长期无人处理。\n- 防护动作：issue/PR 响应未知时，必须提示维护风险。\n- 证据：evidence.maintainer_signals | github_repo:1002125012 | https://github.com/BloopAI/vibe-kanban | issue_or_pr_quality=unknown\n\n## 19. 维护坑 · 发布节奏不明确\n\n- 严重度：low\n- 证据强度：source_linked\n- 发现：release_recency=unknown。\n- 对用户的影响：安装命令和文档可能落后于代码，用户踩坑概率升高。\n- 建议检查：确认最近 release/tag 和 README 安装命令是否一致。\n- 防护动作：发布节奏未知或过期时，安装说明必须标注可能漂移。\n- 证据：evidence.maintainer_signals | github_repo:1002125012 | https://github.com/BloopAI/vibe-kanban | release_recency=unknown\n\n\n", "summary": "DeepWiki/Human Wiki 完整输出，末尾追加 Discovery Agent 踩坑日志。", "title": "Human Manual / 人类版说明书" }, "pitfall_log": { "asset_id": "pitfall_log", "filename": "PITFALL_LOG.md", "markdown": "# Pitfall Log / 踩坑日志\n\n项目：BloopAI/vibe-kanban\n\n摘要：发现 19 个潜在踩坑项，其中 3 个为 high/blocking；最高优先级：安装坑 - 来源证据：Deployment(Other(Migration failed: error returned from database: (code: 1) no such column: ep.session_id))。\n\n## 1. 安装坑 · 来源证据：Deployment(Other(Migration failed: error returned from database: (code: 1) no such column: ep.session_id))\n\n- 严重度：high\n- 证据强度：source_linked\n- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Deployment(Other(Migration failed: error returned from database: (code: 1) no such column: ep.session_id))\n- 对用户的影响：可能影响升级、迁移或版本选择。\n- 建议检查：来源问题仍为 open，Pack Agent 需要复核是否仍影响当前版本。\n- 防护动作：不得脱离来源链接放大为确定性结论；需要标注适用版本和复核状态。\n- 证据：community_evidence:github | cevd_b34b2ea1b35a4dc2a4a0eb0681bdb883 | https://github.com/BloopAI/vibe-kanban/issues/2972 | 来源讨论提到 windows 相关条件，需在安装/试用前复核。\n\n## 2. 配置坑 · 来源证据：Support for self-hosted projects and better export\n\n- 严重度：high\n- 证据强度：source_linked\n- 发现：GitHub 社区证据显示该项目存在一个配置相关的待验证问题：Support for self-hosted projects and better export\n- 对用户的影响：可能阻塞安装或首次运行。\n- 建议检查：来源问题仍为 open，Pack Agent 需要复核是否仍影响当前版本。\n- 防护动作：不得脱离来源链接放大为确定性结论；需要标注适用版本和复核状态。\n- 证据：community_evidence:github | cevd_19d27caa9e34416a9f282869f76624b0 | https://github.com/BloopAI/vibe-kanban/issues/3396 | 来源类型 github_issue 暴露的待验证使用条件。\n\n## 3. 安全/权限坑 · 来源证据：[Proposal] JIRA Integration for Vibe Kanban\n\n- 严重度：high\n- 证据强度：source_linked\n- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：[Proposal] JIRA Integration for Vibe Kanban\n- 对用户的影响：可能影响授权、密钥配置或安全边界。\n- 建议检查：来源问题仍为 open，Pack Agent 需要复核是否仍影响当前版本。\n- 防护动作：不得脱离来源链接放大为确定性结论；需要标注适用版本和复核状态。\n- 证据：community_evidence:github | cevd_ab38fe97c4574e2da01ddedd71a4fbac | https://github.com/BloopAI/vibe-kanban/issues/2424 | 来源类型 github_issue 暴露的待验证使用条件。\n\n## 4. 安装坑 · 来源证据：Pre-release v0.1.40-20260401153532\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Pre-release v0.1.40-20260401153532\n- 对用户的影响：可能阻塞安装或首次运行。\n- 建议检查：来源显示可能已有修复、规避或版本变化，说明书中必须标注适用版本。\n- 防护动作：不得脱离来源链接放大为确定性结论；需要标注适用版本和复核状态。\n- 证据：community_evidence:github | cevd_f4b99d437a4f4fd4989d2b3ef036553b | https://github.com/BloopAI/vibe-kanban/releases/tag/v0.1.40-20260401153532 | 来源讨论提到 docker 相关条件，需在安装/试用前复核。\n\n## 5. 安装坑 · 来源证据：Release v0.1.36\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Release v0.1.36\n- 对用户的影响：可能阻塞安装或首次运行。\n- 建议检查：来源显示可能已有修复、规避或版本变化，说明书中必须标注适用版本。\n- 防护动作：不得脱离来源链接放大为确定性结论；需要标注适用版本和复核状态。\n- 证据：community_evidence:github | cevd_527645be4e3f438e81757ef265a70d79 | https://github.com/BloopAI/vibe-kanban/releases/tag/v0.1.36-20260323174633 | 来源讨论提到 npm 相关条件，需在安装/试用前复核。\n\n## 6. 安装坑 · 来源证据：Release v0.1.43\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Release v0.1.43\n- 对用户的影响：可能增加新用户试用和生产接入成本。\n- 建议检查：来源显示可能已有修复、规避或版本变化，说明书中必须标注适用版本。\n- 防护动作：不得脱离来源链接放大为确定性结论；需要标注适用版本和复核状态。\n- 证据：community_evidence:github | cevd_53704dc7171446fe86b2017f72212ddc | https://github.com/BloopAI/vibe-kanban/releases/tag/v0.1.43-20260417125614 | 来源讨论提到 node 相关条件，需在安装/试用前复核。\n\n## 7. 配置坑 · 可能修改宿主 AI 配置\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：项目面向 Claude/Cursor/Codex/Gemini/OpenCode 等宿主，或安装命令涉及用户配置目录。\n- 对用户的影响：安装可能改变本机 AI 工具行为，用户需要知道写入位置和回滚方法。\n- 建议检查：列出会写入的配置文件、目录和卸载/回滚步骤。\n- 防护动作：涉及宿主配置目录时必须给回滚路径，不能只给安装命令。\n- 证据：capability.host_targets | github_repo:1002125012 | https://github.com/BloopAI/vibe-kanban | host_targets=claude, claude_code\n\n## 8. 能力坑 · 能力判断依赖假设\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：README/documentation is current enough for a first validation pass.\n- 对用户的影响：假设不成立时，用户拿不到承诺的能力。\n- 建议检查：将假设转成下游验证清单。\n- 防护动作：假设必须转成验证项；没有验证结果前不能写成事实。\n- 证据：capability.assumptions | github_repo:1002125012 | https://github.com/BloopAI/vibe-kanban | README/documentation is current enough for a first validation pass.\n\n## 9. 运行坑 · 来源证据：Pre-release v0.1.39-20260331145823\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：GitHub 社区证据显示该项目存在一个运行相关的待验证问题：Pre-release v0.1.39-20260331145823\n- 对用户的影响：可能阻塞安装或首次运行。\n- 建议检查：来源显示可能已有修复、规避或版本变化，说明书中必须标注适用版本。\n- 防护动作：不得脱离来源链接放大为确定性结论；需要标注适用版本和复核状态。\n- 证据：community_evidence:github | cevd_c005a56959634369929ce33eddbdc103 | https://github.com/BloopAI/vibe-kanban/releases/tag/v0.1.39-20260331145823 | 来源讨论提到 windows 相关条件，需在安装/试用前复核。\n\n## 10. 维护坑 · 来源证据：[Request] Support RDS for self hosting in AWS\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：GitHub 社区证据显示该项目存在一个维护/版本相关的待验证问题：[Request] Support RDS for self hosting in AWS\n- 对用户的影响：可能影响升级、迁移或版本选择。\n- 建议检查：来源问题仍为 open，Pack Agent 需要复核是否仍影响当前版本。\n- 防护动作：不得脱离来源链接放大为确定性结论；需要标注适用版本和复核状态。\n- 证据：community_evidence:github | cevd_f613b792c20942519560c0a286a82005 | https://github.com/BloopAI/vibe-kanban/issues/3405 | 来源类型 github_issue 暴露的待验证使用条件。\n\n## 11. 维护坑 · 维护活跃度未知\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：未记录 last_activity_observed。\n- 对用户的影响：新项目、停更项目和活跃项目会被混在一起，推荐信任度下降。\n- 建议检查：补 GitHub 最近 commit、release、issue/PR 响应信号。\n- 防护动作：维护活跃度未知时，推荐强度不能标为高信任。\n- 证据：evidence.maintainer_signals | github_repo:1002125012 | https://github.com/BloopAI/vibe-kanban | last_activity_observed missing\n\n## 12. 安全/权限坑 · 下游验证发现风险项\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：no_demo\n- 对用户的影响：下游已经要求复核，不能在页面中弱化。\n- 建议检查：进入安全/权限治理复核队列。\n- 防护动作：下游风险存在时必须保持 review/recommendation 降级。\n- 证据：downstream_validation.risk_items | github_repo:1002125012 | https://github.com/BloopAI/vibe-kanban | no_demo; severity=medium\n\n## 13. 安全/权限坑 · 存在安全注意事项\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：No sandbox install has been executed yet; downstream must verify before user use.\n- 对用户的影响：用户安装前需要知道权限边界和敏感操作。\n- 建议检查：转成明确权限清单和安全审查提示。\n- 防护动作：安全注意事项必须面向用户前置展示。\n- 证据：risks.safety_notes | github_repo:1002125012 | https://github.com/BloopAI/vibe-kanban | No sandbox install has been executed yet; downstream must verify before user use.\n\n## 14. 安全/权限坑 · 存在评分风险\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：no_demo\n- 对用户的影响：风险会影响是否适合普通用户安装。\n- 建议检查：把风险写入边界卡，并确认是否需要人工复核。\n- 防护动作：评分风险必须进入边界卡，不能只作为内部分数。\n- 证据：risks.scoring_risks | github_repo:1002125012 | https://github.com/BloopAI/vibe-kanban | no_demo; severity=medium\n\n## 15. 安全/权限坑 · 来源证据：Issue: Unclear Git + Bitbucket Setup for Vibe-Kanban (OpenCode) in Docker\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：Issue: Unclear Git + Bitbucket Setup for Vibe-Kanban (OpenCode) in Docker\n- 对用户的影响：可能影响升级、迁移或版本选择。\n- 建议检查：来源问题仍为 open，Pack Agent 需要复核是否仍影响当前版本。\n- 防护动作：不得脱离来源链接放大为确定性结论；需要标注适用版本和复核状态。\n- 证据：community_evidence:github | cevd_7d289a7b68ee4299ae4a5e54b0e64e35 | https://github.com/BloopAI/vibe-kanban/issues/3410 | 来源讨论提到 docker 相关条件，需在安装/试用前复核。\n\n## 16. 安全/权限坑 · 来源证据：Pre-release v0.1.37-20260327101540\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：Pre-release v0.1.37-20260327101540\n- 对用户的影响：可能影响授权、密钥配置或安全边界。\n- 建议检查：来源显示可能已有修复、规避或版本变化，说明书中必须标注适用版本。\n- 防护动作：不得脱离来源链接放大为确定性结论；需要标注适用版本和复核状态。\n- 证据：community_evidence:github | cevd_d648fba4c94b4791ac2e7683f6cb1361 | https://github.com/BloopAI/vibe-kanban/releases/tag/v0.1.37-20260327101540 | 来源讨论提到 macos 相关条件，需在安装/试用前复核。\n\n## 17. 安全/权限坑 · 来源证据：remote-v0.1.26\n\n- 严重度：medium\n- 证据强度：source_linked\n- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：remote-v0.1.26\n- 对用户的影响：可能影响授权、密钥配置或安全边界。\n- 建议检查：来源显示可能已有修复、规避或版本变化，说明书中必须标注适用版本。\n- 防护动作：不得脱离来源链接放大为确定性结论；需要标注适用版本和复核状态。\n- 证据：community_evidence:github | cevd_3f212752e8c142d68ffe2993ac23dd37 | https://github.com/BloopAI/vibe-kanban/releases/tag/remote-v0.1.26 | 来源讨论提到 macos 相关条件，需在安装/试用前复核。\n\n## 18. 维护坑 · issue/PR 响应质量未知\n\n- 严重度：low\n- 证据强度：source_linked\n- 发现：issue_or_pr_quality=unknown。\n- 对用户的影响：用户无法判断遇到问题后是否有人维护。\n- 建议检查：抽样最近 issue/PR，判断是否长期无人处理。\n- 防护动作：issue/PR 响应未知时，必须提示维护风险。\n- 证据：evidence.maintainer_signals | github_repo:1002125012 | https://github.com/BloopAI/vibe-kanban | issue_or_pr_quality=unknown\n\n## 19. 维护坑 · 发布节奏不明确\n\n- 严重度：low\n- 证据强度：source_linked\n- 发现：release_recency=unknown。\n- 对用户的影响：安装命令和文档可能落后于代码，用户踩坑概率升高。\n- 建议检查：确认最近 release/tag 和 README 安装命令是否一致。\n- 防护动作：发布节奏未知或过期时，安装说明必须标注可能漂移。\n- 证据：evidence.maintainer_signals | github_repo:1002125012 | https://github.com/BloopAI/vibe-kanban | release_recency=unknown\n", "summary": "用户实践前最可能遇到的身份、安装、配置、运行和安全坑。", "title": "Pitfall Log / 踩坑日志" }, "prompt_preview": { "asset_id": "prompt_preview", "filename": "PROMPT_PREVIEW.md", "markdown": "# vibe-kanban - Prompt Preview\n\n> Copy the prompt below into your AI host before installing anything.\n> Its purpose is to let you safely feel the project's workflow, not to claim the project has already run.\n\n## Copy this prompt\n\n```text\nYou are using an independent Doramagic capability pack for BloopAI/vibe-kanban.\n\nProject:\n- Name: vibe-kanban\n- Repository: https://github.com/BloopAI/vibe-kanban\n- Summary: Get 10X more out of Claude Code, Codex or any coding agent\n- Host target: claude, claude_code\n\nGoal:\nHelp me evaluate this project for the following task without installing it yet: Get 10X more out of Claude Code, Codex or any coding agent\n\nBefore taking action:\n1. Restate my task, success standard, and boundary.\n2. Identify whether the next step requires tools, browser access, network access, filesystem access, credentials, package installation, or host configuration.\n3. Use only the Doramagic Project Pack, the upstream repository, and the source-linked evidence listed below.\n4. If a real command, install step, API call, file write, or host integration is required, mark it as \"requires post-install verification\" and ask for approval first.\n5. If evidence is missing, say \"evidence is missing\" instead of filling the gap.\n\nPreviewable capabilities:\n- Capability 1: Get 10X more out of Claude Code, Codex or any coding agent\n\nCapabilities that require post-install verification:\n- Capability 1: Use the source-backed project context to guide one small, checkable workflow step.\n\nCore service flow:\n1. page-project-introduction: Project Introduction. Produce one small intermediate artifact and wait for confirmation.\n2. page-key-concepts: Key Concepts. Produce one small intermediate artifact and wait for confirmation.\n3. page-development-setup: Development Setup. Produce one small intermediate artifact and wait for confirmation.\n4. page-backend-architecture: Backend Architecture. Produce one small intermediate artifact and wait for confirmation.\n5. page-frontend-architecture: Frontend Architecture. Produce one small intermediate artifact and wait for confirmation.\n\nSource-backed evidence to keep in mind:\n- https://github.com/BloopAI/vibe-kanban\n- https://github.com/BloopAI/vibe-kanban#readme\n- README.md\n- CLAUDE.md\n- AGENTS.md\n- crates/db/src/models/project.rs\n- crates/db/src/models/workspace.rs\n- crates/db/src/models/session.rs\n- crates/db/src/models/task.rs\n- crates/db/src/models/scratch.rs\n\nFirst response rules:\n1. Start Step 1 only.\n2. Explain the one service action you will perform first.\n3. Ask exactly three questions about my target workflow, success standard, and sandbox boundary.\n4. Stop and wait for my answers.\n\nStep 1 follow-up protocol:\n- After I answer the first three questions, stay in Step 1.\n- Produce six parts only: clarified task, success standard, boundary conditions, two or three options, tradeoffs for each option, and one recommendation.\n- End by asking whether I confirm the recommendation.\n- Do not move to Step 2 until I explicitly confirm.\n\nConversation rules:\n- Advance one step at a time and wait for confirmation after each small artifact.\n- Write outputs as recommendations or planned checks, not as completed execution.\n- Do not claim tests passed, files changed, commands ran, APIs were called, or the project was installed.\n- If the user asks for execution, first provide the sandbox setup, expected output, rollback, and approval checkpoint.\n```\n", "summary": "不安装项目也能感受能力节奏的安全试用 Prompt。", "title": "Prompt Preview / 安装前试用 Prompt" }, "quick_start": { "asset_id": "quick_start", "filename": "QUICK_START.md", "markdown": "# Quick Start / 官方入口\n\n项目：BloopAI/vibe-kanban\n\n## 官方安装入口\n\n### Node.js / npx · 官方安装入口\n\n```bash\nnpx vibe-kanban\n```\n\n来源：https://github.com/BloopAI/vibe-kanban#readme\n\n## 来源\n\n- repo: https://github.com/BloopAI/vibe-kanban\n- docs: https://github.com/BloopAI/vibe-kanban#readme\n", "summary": "从项目官方 README 或安装文档提取的开工入口。", "title": "Quick Start / 官方入口" } }, "validation_id": "dval_e55369cc1fa641a2b59247e944d86e7c" }