Overview專案總覽
Live goal, progress, blockers and recent decisions. Unknown sources stay distinct from complete empty records; fixed reports remain separate.看即時目標、進度、阻礙與近期決策。未知來源與完整空紀錄分開呈現，固定報告另讀。
Read the contract →閱讀設計合約 →See the project.
Decide with the PM.看懂專案，
與 PM 完成決策。
Understand the project, find a problem and discuss it with the PM. Review a proposed update and adopt it in the same project workspace, shared by Web and desktop.先看懂專案狀況，找到問題，再直接與 PM 討論。從原紀錄帶入脈絡、審閱提案到明確採用，都在同一個專案裡完成；Web 與桌面版共用介面。
Explore the current Dashboard with sample data. The v1.3 workflow preview simulates start, follow-up and decision. The real Start work panel is on main and needs a configured BAT host and a bound repository.用展示資料操作目前的 Dashboard。v1.3 工作流程預覽會模擬開始工作、追加修改與驗收決策。主線上已有真正的「開始工作」面板，它需要已設定的 BAT 主機與已綁定的儲存庫。
View:檢視：
Development preview開發預覽Screenshots pin merged main at 265026d4c1fc2bc04a9aaa727d566c1a2906b256, through #205 on October 16, 2026. They show the synthetic Dashboard in Development: Needs attention, a four-section live charter, an unadopted discussion proposal, twelve register records, and a manual session whose host is not set up for managed work. The gallery does not open Start work or the Result section. Gallery images do not establish installation or live acceptance. Match the package to its source before installing.截圖固定於已合併主線的 265026d4c1fc2bc04a9aaa727d566c1a2906b256，包含 2026 年 10 月 16 日的 #205。畫面是開發階段的合成 Dashboard：需要關注、四段即時專案章程、一份尚未採用的討論提案、十二筆登記，以及人工工作階段寫明此主機尚未設定受管工作。圖庫沒有打開「開始工作」或成果區。圖庫不代表安裝或實機驗收；安裝前請核對套件來源。Current scope目前範圍
Screenshot sources and reproduction →截圖來源與重拍方式 →Activity has a source活動要有來源
A session going quiet does not establish completion.session 安靜下來，不能直接判斷已完成。
Acceptance has a reason驗收要有理由
Record the criterion, result, evidence and responsible reviewer.保留條件、結果、證據與負責審閱者。
Recovery keeps the original恢復沿用原紀錄
Read back an uncertain operation before starting another.結果未知時先查回原操作，再決定下一步。
One small project first先從小專案開始
One project, from problem to decision.同一個專案，從問題走到決策。
Try member sign-in and password reset. Keep the project selected as you move from its status to a sourced discussion and a reviewable update.先試會員登入與忘記密碼的小專案。從總覽找到問題、帶入討論，到審閱更新，都保留同一份專案脈絡。
- 01
Understand the state看懂狀況
Open Overview for the goal, accepted requirements, blockers and pending decisions. Read saved reports separately.在專案總覽看目標、已驗收需求、阻礙與待決事項；需要回顧時再切換已存報告。
- 02
Find the problem找到問題
Open a record in Requirements, Issues & changes or Schedule and inspect its original evidence.從需求、問題與變更或時程開啟紀錄，查看原始證據與下一步。
- 03
Discuss with PM與 PM 討論
Use the record's Discuss action. Its context and title follow you into Discussions; save a note and ask the PM.按紀錄上的討論入口，來源與標題會一起帶入；寫下想法，再請 PM 提案。
- 04
Review and adopt審閱並採用
Check the proposed wording, retained requirements and open questions. An authorized owner explicitly adopts the reviewed update.核對建議文字、保留需求與未決問題，再由有權限的負責人明確採用。
Adoption needs the PM-owned Git worktree and owner authority. It does not start work or accept a requirement. Passing tests, merging and deployment retain their own evidence.採用需要 PM 自有 Git 工作區及工作空間擁有者權限。採用不會直接開工或完成需求驗收；測試、合併與部署各自保留證據。
Follow the PM guide →閱讀 PM 使用指南 →Follow the PM guide →閱讀 PM 使用指南 →The daily work日常工作
Keep decisions close to their evidence.讓決策與證據放在一起。
Discussions討論
Search source-bound discussions, save notes and review proposed updates. Context, Inputs and Plan open in Discussion info. Reported issue resolution remains unassessed.搜尋有來源的討論、儲存筆記並審閱建議更新；討論資料按需開啟脈絡、資訊與計畫。問題解決回報仍為未評估。
Read the contract →閱讀設計合約 →Requirements需求
Expand requirements for criteria and bound work. Inspect acceptance, PRs and deployment; unchanged refreshes keep rows and focus stable.展開需求查看條件與關聯工作，再開詳情對照驗收、PR 與部署；資料未變的更新保留列位置與焦點。
Read the contract →閱讀設計合約 →Issues & changes問題與變更
A filterable register with named findings, original records and processing timelines.用篩選登記表追蹤具名發現、原紀錄與處理時間線。
Read the contract →閱讀設計合約 →Schedule時程
Compare recorded dates on a labelled axis. Missing dates stay unknown.在標示日期的時間軸上對照已記錄日期；缺少的日期保持未知。
Read the contract →閱讀設計合約 →Dependencies技術相依
Pinned inventories, evidence styles and bounded impact reads in a matrix or graph.用矩陣或相依圖查看固定清冊、證據與有界影響。
Read the contract →閱讀設計合約 →AgentsAgent 資源
Sourced usage, rows and daily trends share one consistent read. Reported quota stays separate; unavailable data stays unknown.以同一次讀取呈現用量、來源列與每日趨勢；回報配額另列，無法取得的資料保持未知。
Read the contract →閱讀設計合約 →Board工作看板
Search, filter by requirement or agent, and open the shared work inspector. Work batches are in More actions.搜尋、依需求或 Agent 篩選，再開啟共用工作詳情；更多操作可開啟工作批次。
Read the contract →閱讀設計合約 →Governance and meetings治理與會議
Open Governance and Follow-ups from Issues & changes. Meeting threads have a Meeting tab in Discussion info. Outcomes keep their fixed sources.從問題與變更開啟治理與後續追蹤；會議類討論的資料面板另有會議分頁。結果保留固定來源。
Read the contract →閱讀設計合約 →Maintenance維護
Dependencies holds Release baselines and Maintenance policy. Preview a release before registration; adopted policy keeps explicit repair bounds.技術相依提供發布基準與維護政策；登錄前先預覽發布來源，已採用政策保留明確修復限制。
Read the contract →閱讀設計合約 →Work tools工程工具
Requirements → More actions opens quality, evidence, specification, package, handoff and issue publication tools.需求的更多操作開啟品質、成果證據、規格、工程工作包、工作包交接與議題發布工具。
Read the contract →閱讀設計合約 →Session工作階段
Read conversations and results; authorized managed controls coexist with read-only manual sessions.一起讀對話與成果；自有工作依權限操作，人工工作階段保持唯讀。
Read the contract →閱讀設計合約 →Clear responsibilities清楚的分工
One central history. Work on the chosen host.同一份中央歷史，工作留在選定主機。
Project management builds on Connector, BAT and Fleet. Web and Tauri share the same product surface.專案管理建立在 Connector、BAT 與 Fleet 之上；Web 和 Tauri 使用同一份產品介面。
Windows Fleet: connection and startupWindows Fleet：連線與啟動
Manage selected SSH tunnels, route readiness, BAT profiles and sign-in choices. Rust and the existing PowerShell backend follow explicit ownership and migration rules.管理選定 SSH tunnels、路由就緒、BAT profiles 及登入選項；Rust 與既有 PowerShell backend 遵守明確的歸屬與遷移規則。
Web DashboardWeb DashboardAuthenticated browser entry已認證的瀏覽器入口
Tauri desktopTauri 桌面Shared UI, native windows and credentials共用介面、原生視窗與憑證
CLI / MCP / agentsCLI／MCP／AgentsEach client has its own principal各 client 使用自己的身分
Python Connector / Task ServicePython Connector／Task ServicePlans · permissions · dispatch · evidence · durable operations計畫 · 權限 · 派工 · 證據 · 持久操作紀錄
↓ Governed BAT operations ↓↓ 受控 BAT 操作 ↓
Selected BAT host and workspace選定的 BAT 主機與 workspace
Your coding resources人的開發資源
Keep using BAT desktop or mobile. Connector reads human sessions and worktrees; continuation creates new owned work.照常使用 BAT desktop／mobile；Connector 唯讀人工 session 與 worktree，接續時建立新的自有工作。
Agent-owned resourcesAgent 自有資源
The PM and engineering agents retain their own workspaces, fixed source revisions and original operation links.PM 與工程 Agent 保留各自工作區、固定來源版本及原操作關聯。
Fixed result → GitHub PR → merge / deploy → maintenance固定成果 → GitHub PR → merge／部署 → 維護
Cross-host code synchronization uses explicitly bound repositories and published commits.跨主機程式碼同步使用明確綁定的 repository 與已發布 commit。
Keep the same central沿用同一個中央
Desktop prepares one private local central. Explicitly join an existing central when needed; connection failure never replaces its database.桌面準備一套私人本機中央，需要時明確加入既有中央；連線失敗不會另造資料庫。
Know where PM runs知道 PM 在哪裡執行
Bounded PM analysis runs on an eligible Linux central or BAT host. A Windows/Mac client can use that route; installing its desktop app does not add a native coding adapter.有界 PM 分析在合格 Linux 中央或 BAT 主機執行。Windows／Mac client 可使用該路徑，桌面安裝本身不會增加一般原生 coding adapter。
Windows FleetWindows Fleet
Choose what connects and what opens.選要連的主機，也選要開的視窗。
Local connectivity and startup stay visible alongside project management.專案管理之外，本機連線與啟動控制仍有清楚入口。
Connections and readiness連線與就緒
Maintain selected tunnels and configured route fallbacks. Check TLS, BAT identity and central access before work.維持選定 tunnels 與已配置備援路由，工作前核對 TLS、BAT 身分及中央存取。
Read the guide →閱讀說明 →Windows sign-inWindows 登入
Choose background connections, BAT profile windows and Dashboard independently; retain the login picker or saved choices.背景連線、BAT profile 視窗、Dashboard 各自選擇，保留登入選擇器或已存選項。
Read the guide →閱讀說明 →One connection owner明確的連線 owner
Use public Rust configuration or explicitly migrate an existing PowerShell setup after proving the old owner stopped.使用公開 Rust 設定，或證明舊 owner 已停止後明確遷移既有 PowerShell 配置。
Read the guide →閱讀說明 →Native resources原生資源
Credential Manager, files and tray controls remain available. Tailscale sign-in and fixed central bootstrap use configured local facilities.保留 Credential Manager、檔案及系統匣操作；Tailscale 登入與固定中央 bootstrap 使用已配置的本機能力。
Read the guide →閱讀說明 →Start with a reviewed build從核對過的版本開始
Install, connect, try a small project.安裝、連線，先試一個小專案。
Desktop packages include Python and prepare the local central. Account trust and work destinations remain explicit choices.桌面包包含 Python 並準備本機中央；帳號信任與工作目的地仍由你明確選擇。
Match the package核對套件
Download Connector 0.2.8 / desktop 0.1.4 from the published preview. Check its source manifest and SHA-256 checksums.下載已發布的 Connector 0.2.8／desktop 0.1.4 預覽版，核對來源清單與 SHA-256 校驗碼。
Connect your environment連接環境
Get ready to work opens 1. Connect BAT. Paste BAT’s connection URL, check Host ID, then Verify and save host. After success, choose View sessions. Repository binding and verification commands stay collapsed until needed.準備開始工作會展開「1. 連線至 BAT」。貼上 BAT 連線網址、核對主機代號，再按「驗證並儲存主機」。成功後按「查看工作階段」；儲存庫與驗證命令需要時再展開。
Follow one result追完一份成果
Start a small PM scope, inspect its original evidence and record what still needs a decision.從小範圍 PM 工作開始，檢視原始證據，記錄仍需決定的事項。
Validate the version you use驗證你實際使用的版本
Advanced users can explicitly join an existing central. The published preview includes fixed source and checksum records. These are development validation builds, not a stable signed update channel. Closing the UI leaves central work running.進階使用者可明確加入既有中央。已發布預覽版附有固定來源與校驗紀錄。這些是開發驗證包，尚非穩定的簽章更新通道；關閉 UI 仍保留中央工作。
Entry points使用入口
One Dashboard across your screens.不同螢幕，同一份 Dashboard。
| Entry入口 | Local facilities本機能力 | Current boundary目前界線 |
|---|---|---|
| Browser瀏覽器 | Shared UI and authenticated central access共用 UI 與中央認證存取 | No native Fleet or credential vault.沒有原生 Fleet 或 credential vault。 |
| Windows x64Windows x64 | NSIS, bundled central, tray, Fleet and Credential ManagerNSIS、打包中央、系統匣、Fleet 與 Credential Manager | Unsigned validation package.未正式簽署的驗證包。 |
| Mac Apple Silicon / IntelMac Apple Silicon／Intel | DMG, bundled central, menu bar and KeychainDMG、打包中央、選單列與 Keychain | Ad-hoc signing; Windows Fleet is not ported.ad-hoc 簽署；Windows Fleet 未移植。 |
| LinuxLinux | Debian package and bundled centralDebian 套件及打包中央 | External-central native credentials are memory-only.外部中央的原生憑證只留記憶體。 |
Formal signing, Mac notarization, production updates and Linux persistent native credential storage are outside the agreed delivery.正式簽章、Mac 公證、正式更新通道與 Linux 原生憑證持久儲存，已排除於本次交付。
Ownership and recovery歸屬與恢復
Keep control and history intact.保留控制邊界，也保留歷史。
Your workspace stays yours人的工作區保持原樣
Human sessions and worktrees remain read-only through Connector. Reading a source does not grant control of it.Connector 對人工 session 與 worktree 保持唯讀；能讀來源，不代表能控制來源。
Each action has authority每個動作都有權限依據
The current principal, host policy, source access and original resource identity are checked before effects.效果執行前核對目前身分、主機政策、來源存取及原資源身分。
A lost reply is still traceable遺失回覆仍可追查
Keep the original operation and key while a result is uncertain. Query its evidence instead of dispatching another copy.結果未知時保留原 operation 與 key；查證據，避免再派一份工作。
Host isolation still matters主機隔離仍有自己的責任
Connector policy works with host accounts and confinement. It is not an operating-system sandbox.Connector 政策與主機帳號、隔離機制一起運作，本身不是作業系統 sandbox。
Current scope目前範圍
A working foundation. A lifecycle still in integration.底座已能使用，完整流程仍在整合。
Read merged code, candidate checks and real-environment acceptance as separate records.分開看已合併程式、候選驗證與實際環境驗收。
- Merged main已合併主線
- Desktop and central foundation; PM plans, quality/dependency evidence, bounded dispatch, policy-bounded repairs, BAT proposals/Follow-up and AHP read-only observation. #132 adds central Overview, discussion context and renames, register, Schedule, Dependencies and daily resource buckets; #134 adds adopted goals, recent decisions and the guided close of a resolved issue.桌面與中央底座、PM 計畫、品質／依賴證據、有界派工、政策內修復、BAT 提案／Follow-up 及 AHP 唯讀觀察。#132 補上中央總覽、討論來源與改名、登記表、時程、技術相依及每日資源桶；#134 補上採用後目標、近期決策及問題解決回報引導。
- Merged workspace已合併工作台
- Merged main at 1a5834fe (#276–278, #282, #285, October 18, 2026) supports creating Work, adopting and starting a reviewed plan, sending a second instruction to the same Work, reading fixed Results and diffs, running configured verification, publishing a PR from the same Result, and opening a PM discussion with two existing assessments. Work profiles, readiness and API/MCP parity are included. Workbench adds a full-screen mobile Work list, preserved search and position on return, and Results navigation with browser Back/Forward. Classic remains the default. Integration checks use the real Connector and disk Git with mock BAT/providers; installation and live BAT/model acceptance remain separate.已合併主線 1a5834fe（#276–278、#282、#285，2026 年 10 月 18 日）支援建立 Work、採用並開始已審閱計畫、對同一工作追加第二句、讀取固定成果與差異、執行已設定驗證、從同一成果發布 PR，以及選兩份既有評估帶入 PM 討論。工作設定檔、readiness 與 API／MCP 對等也已納入。Workbench 新增手機全螢幕工作清單，返回時保留搜尋與位置，成果面板支援瀏覽器上一頁／下一頁。Classic 仍為預設。整合測試使用真正 Connector、磁碟 Git 與 mock BAT／providers；安裝與真實 BAT／模型驗收仍須另有證據。
- Still ahead仍待完成
- General native coding, AHP create-own/write, remaining document views/slides, broader CLI support, remote usage collection and delivery-efficiency attribution. The full adopted PM v1.2 plan remains the scope.一般原生 coding、AHP 自建／寫入、其餘文件視圖／簡報、更多 CLI、遠端用量收集及交付效率歸因；範圍仍依完整 PM v1.2 計畫。
- Evidence limits驗證界線
- Package checks validate their exact source and fixtures. Screenshots use demonstration data. Published packages and installation readback do not establish owner live acceptance.套件檢查驗證精確來源與 fixture；截圖使用展示資料。已發布套件與安裝讀回不代表使用者已通過實際環境驗收。
Documentation文件
Find the next useful page.找到下一份用得上的說明。
01
Installation and PM first use ↗安裝與 PM 首次使用 ↗Installation and PM first use ↗安裝與 PM 首次使用 ↗
Packages, runtime prerequisites and one small project.套件、runtime 前提及一個小專案。
02
Windows Fleet and resources ↗Windows Fleet 與資源 ↗Windows Fleet and resources ↗Windows Fleet 與資源 ↗
Connections, profiles, startup and native facilities.連線、profiles、啟動及原生能力。
03
Progress report ↗進度報告 ↗
Merged, candidate, tested and remaining scope.已合併、候選、已驗證及剩餘範圍。
04
Development handoff ↗開發交接 ↗
Fixed versions, evidence, blockers and the next steps.固定版本、證據、阻擋與接續步驟。
05
Agent integration ↗Agent 整合 ↗
Canonical skills, MCP/CLI and central operations.共用 skills、MCP／CLI 及中央操作。
06
Source and contribution ↗原始碼與參與開發 ↗Source and contribution ↗原始碼與參與開發 ↗
Build the shared frontend and run the relevant checks.建置共用前端並執行相應檢查。
Practical questions使用前的問題
Know what to expect.先了解可以期待什麼。
Does BAT have to run on this computer?BAT 一定要在這台電腦執行嗎？
No. The Dashboard can connect to a configured central and BAT host. Coding work stays on the selected host; the browser's operating system does not determine runtime support.不必。Dashboard 可連已配置的中央與 BAT 主機；開發工作留在選定主機，瀏覽器的作業系統不決定 runtime 支援。
Will PM act on everything I say?跟 PM 說的每句話都會直接執行嗎？
Discussion creates records and proposals. Adoption, dispatch and maintenance policy are explicit product actions with their own authority and fixed scope.討論形成紀錄與提案；採用、派工及維護政策是明確的產品操作，各有權限與固定範圍。
Does it scan every CLI's tokens?已經會掃每個 CLI 的 token 嗎？
Local Codex and Claude collectors are implemented. Agents shows sourced observations, daily buckets where available and reported quota windows. Remote collection and delivery-efficiency attribution remain planned; token traffic is not a subscription quota or bill.已有 Codex 與 Claude 本機 collector。Agent 資源顯示有來源的觀測、可用的每日桶及回報配額窗；遠端收集與交付效率歸因仍待做，token 流量也不能直接當成訂閱配額或帳單。
Will optimization change my model automatically?優化會自動換掉我的模型嗎？
No usage-driven model policy is active. Future recommendations need measured delivery quality; adopted policy should apply to new owned work while preserving existing and human sessions.尚未啟用依用量自動改模型的政策。未來建議需要交付品質的實測，採用後應作用於新的自有工作，保留既有及人工 session。
Can I leave it unattended all day?可以整天放著無人值守嗎？
Only within verified capabilities and adopted bounds. Controlled fixtures do not establish readiness of your accounts, hosts or deployment targets; real-environment acceptance remains with the owner.須在已驗證能力及採用界線內使用；受控 fixture 不代表你的帳號、主機或部署目標已就緒，實際環境驗收仍由使用者處理。
Is this an official BAT product?這是 BAT 官方產品嗎？
It is an unofficial MIT-licensed companion. BAT is by TonyQ and contributors. Project Hub informs selected interaction patterns without a runtime or importer dependency.這是 MIT 授權的非官方 companion。BAT 由 TonyQ 與貢獻者開發；部分互動參考 Project Hub，沒有 runtime 或 importer 依賴。