暂无描述
查找文件
YokiiroBW b6a21a70ec
一些检测仍在等待运行
ci / Portable quality checks (push) Waiting to run
ci / Windows Tauri build (push) Waiting to run
feat(awareness): let the companion read one authorized window
Wires the window-awareness modules to the product for the first time.
uia.rs and capture.rs were fully written and had no Tauri command at all;
their only caller anywhere was an #[ignore]d smoke test, so nothing in a
shipped build could reach them.

Six commands, all behind the ADR-0008 policy: the privacy switch, the
session list, start and stop, a window frame, and the window's UI
Automation text. The read takes a closure so the window handle never
leaves the policy module — there is no accessor that skips the switch, the
session lookup, the expiry check, or the rate limit.

Starting a session has an interaction problem worth naming: reading the
foreground window is the only selection mechanism these modules have, and
at the moment the user clicks the button, the foreground window is this
application. So the button gives them a few bounded seconds to bring the
target forward, and a window belonging to this process is refused rather
than captured — which is the most likely outcome if the delay elapses
while they are still on the settings page.

The panel sends either the window's text or its picture to the companion
slot. Text first in the UI order, deliberately: it is far less revealing
than a screenshot and usually enough to answer "what am I looking at".

The indicator in the shell is ADR-0008 item 5, which no project document
required. Reading someone's screen with no visible sign is
indistinguishable from spyware from the outside, and a stop control the
user has to go looking for is not a stop control. It polls rather than
waiting to be told, because an authorization can lapse on its own — and
when it cannot read the status it renders nothing, claiming neither that a
capture is live nor that one is not.

The app's own commands need no capability entries: only plugin commands go
through the ACL, which the existing commands working under `core:default`
alone already demonstrates.

Rust tests 110 -> 113, frontend 43 -> 47.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-27 06:29:54 +08:00
.forgejo/workflows ci(forgejo): add portable and windows quality workflows 2026-07-18 20:43:20 +08:00
assets feat(p00): add Tauri desktop spike foundation 2026-07-18 20:34:47 +08:00
crates feat(chat): carry voice and other non-image attachments end to end 2026-07-27 06:16:55 +08:00
docs feat(policy): gate screen reading behind consent, a rate limit, and a switch 2026-07-27 06:22:15 +08:00
src feat(awareness): let the companion read one authorized window 2026-07-27 06:29:54 +08:00
src-tauri feat(awareness): let the companion read one authorized window 2026-07-27 06:29:54 +08:00
tests feat(chat): give the conversation the height the header was using 2026-07-27 03:59:29 +08:00
.editorconfig chore(repo): initialize repository and ignore rules 2026-07-18 20:22:52 +08:00
.gitignore chore(git): ignore machine-local claude config 2026-07-27 00:59:55 +08:00
.node-version feat(p00): add Tauri desktop spike foundation 2026-07-18 20:34:47 +08:00
.npmrc feat(p00): add Tauri desktop spike foundation 2026-07-18 20:34:47 +08:00
.prettierignore chore(prettier): ignore machine-local claude settings 2026-07-27 00:00:48 +08:00
AGENTS.md docs(project): add architecture and implementation specifications 2026-07-18 20:21:19 +08:00
AstrBot_Desktop_Codex_Forgejo_Predevelopment_Workflow.md docs(project): add architecture and implementation specifications 2026-07-18 20:21:19 +08:00
Cargo.lock feat(desktop): complete Q9 chat and stability increment 2026-07-21 14:43:14 +08:00
Cargo.toml feat(desktop): complete Q9 chat and stability increment 2026-07-21 14:43:14 +08:00
CHANGELOG.md fix(pet): read stored preferences and stop the pet from stealing focus 2026-07-27 05:25:27 +08:00
eslint.config.js feat(p00): add Tauri desktop spike foundation 2026-07-18 20:34:47 +08:00
index.html feat(p00): add Tauri desktop spike foundation 2026-07-18 20:34:47 +08:00
package.json feat(desktop): complete Q9 chat and stability increment 2026-07-21 14:43:14 +08:00
pet.html fix(pet): read stored preferences and stop the pet from stealing focus 2026-07-27 05:25:27 +08:00
playwright.config.ts test(p00): add frontend browser rust and windows checks 2026-07-18 20:42:40 +08:00
pnpm-lock.yaml feat(p00): add Tauri desktop spike foundation 2026-07-18 20:34:47 +08:00
pnpm-workspace.yaml feat(p00): add Tauri desktop spike foundation 2026-07-18 20:34:47 +08:00
README.md docs(p00): record spike results and unresolved boundaries 2026-07-18 21:00:49 +08:00
rust-toolchain.toml feat(p00): add Tauri desktop spike foundation 2026-07-18 20:34:47 +08:00
tsconfig.app.json feat(p00): add Tauri desktop spike foundation 2026-07-18 20:34:47 +08:00
tsconfig.json feat(p00): add Tauri desktop spike foundation 2026-07-18 20:34:47 +08:00
tsconfig.node.json feat(p00): add Tauri desktop spike foundation 2026-07-18 20:34:47 +08:00
vite.config.ts fix(pet): read stored preferences and stop the pet from stealing focus 2026-07-27 05:25:27 +08:00

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:

  • companion for chat, proactive messages, voice, and game companionship;
  • operations for 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 -> commit and 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.md
  • docs/01_Architecture_Design.md
  • docs/02_Codex_Implementation_Tasks.md
  • AstrBot_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.