implementation-queue.md:129 requires an authorization prompt, a frequency limit, and a privacy switch to exist before screenshots or window summaries are wired to anything. None of the three existed anywhere in the repository, so this is them, plus ADR-0008 recording what the authoritative documents actually permit. The ADR corrects a mis-reading that would have decided the feature the wrong way. 01_Architecture_Design.md:250-261 is titled 「不应放在前端的 能力」, so the 「原始截图捕获」 at :259 forbids screenshot capture in React — it is not a product-level ban, which is how an earlier audit read it before concluding screen reading was out of scope. The product affirmatively permits 「用户授权的单次窗口截图」 (:739) and, for phase 7, 「手动和低频截图」 (:1424). What it does exclude is 「实时全双工语音」, 「唤醒词」 and 「高频视频分析」 (:1349-1351). The module owns all three gates so none of them depends on the frontend being correct. Reading takes a closure, so the window handle never leaves the module and there is no accessor that skips the switch, the session, the expiry check, or the budget. The switch defaults to off and clearing it drops live sessions, so flipping it mid-capture stops the next read rather than only preventing new authorizations. `now` is a parameter to the budget rather than read inside it, which is what makes the interval testable without sleeping. Two decisions worth naming. The pixel interval defaults to two seconds with a 500ms floor no caller can lower — three orders of magnitude away from a video frame rate, because high-frequency video analysis is out of scope and what phase 7 asks for is manual, low-frequency capture. And a session cannot be bound to the operations slot at all, refused at creation rather than at each read, because :1077 says the operations slot does not automatically receive game screenshots, window state, or game events — and a session is exactly that automatic delivery. The slot rule is a free function so it is asserted directly rather than through a live window. Also recorded, not worked around: capture.rs uses PrintWindow over GDI, which does not capture a hardware-accelerated game surface. Game companionship needs Windows.Graphics.Capture before it works on the case it exists for, and a black frame delivered to the model would be worse than an error. Rust tests 101 -> 110. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .forgejo/workflows | ||
| assets | ||
| crates | ||
| docs | ||
| src | ||
| src-tauri | ||
| tests | ||
| .editorconfig | ||
| .gitignore | ||
| .node-version | ||
| .npmrc | ||
| .prettierignore | ||
| AGENTS.md | ||
| AstrBot_Desktop_Codex_Forgejo_Predevelopment_Workflow.md | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CHANGELOG.md | ||
| eslint.config.js | ||
| index.html | ||
| package.json | ||
| pet.html | ||
| playwright.config.ts | ||
| pnpm-lock.yaml | ||
| pnpm-workspace.yaml | ||
| README.md | ||
| rust-toolchain.toml | ||
| tsconfig.app.json | ||
| tsconfig.json | ||
| tsconfig.node.json | ||
| vite.config.ts | ||
AstrBot Desktop
AstrBot Desktop is a Windows companion and local-assistance client built with Tauri 2, React, TypeScript, Vite, and Rust.
The MVP supports two isolated active AstrBot connection slots:
companionfor chat, proactive messages, voice, and game companionship;operationsfor user-authorized, policy-controlled diagnostics and recoverable file operations.
Security boundaries
- Credentials remain in Windows secure storage and are never exposed to React.
- Server tool requests are proposals; the Rust policy layer makes the final decision.
- The application does not provide arbitrary PowerShell, CMD, or shell execution.
- NAS transfers use
plan -> dry run -> copy -> verify -> commitand preserve source files on failure.
Current phase
The repository is in the P00 bootstrap and high-risk Spike phase. See docs/implementation-plan.md and docs/progress.md.
Authoritative documents
AGENTS.mddocs/01_Architecture_Design.mddocs/02_Codex_Implementation_Tasks.mdAstrBot_Desktop_Codex_Forgejo_Predevelopment_Workflow.md
Development prerequisites
- Windows 11
- Node.js and pnpm
- Rust stable with the MSVC target
- Visual Studio 2022 Build Tools with Desktop development with C++
- WebView2 Evergreen Runtime
Local commands
pnpm install --frozen-lockfile
pnpm check:frontend
pnpm test:e2e
pnpm rust:fmt
pnpm rust:clippy
pnpm rust:test
pnpm rust:check
pnpm tauri:dev
pnpm tauri:build
On Windows, Cargo build output can be redirected away from a NAS workspace:
$env:CARGO_TARGET_DIR = "$env:LOCALAPPDATA\Temp\AstrBot-Desktop-target"
The 30-minute connection soak and the controlled Windows UIA/capture smoke are ignored by the normal suite and must be invoked explicitly as documented in tests/README.md. The UIA/capture smoke opens only a generated, non-sensitive standard dialog and never writes captured pixels to disk.
P00 results and unresolved environment boundaries are recorded in docs/spikes and docs/progress.md.