暂无描述
查找文件
YokiiroBW 0fadc699e2 fix(net): reject one profile occupying both runtime slots
probe_connection_slot never consulted the slot assignment table, so the
same profile could be activated into both runtime slots at once. That
bypasses the ProfileAlreadyAssigned policy the database enforces, and
both slots then race to overwrite the same sticky_session_id.

Enforce it in three places. The runtime invariant lives inside
activate_slot's claim phase, so it also covers startup auto-connect,
which calls activate_slot directly and would bypass a command-layer
check. The command adds a cross-check against connection_slots. And the
operations switch guard now covers probe and disconnect, not just slot
assignment.

Both rules are deliberately negative — they ask whether the profile is
bound to the *other* slot, never whether it is bound to this one.
auto_connect_configured_slots activates from profile.auto_connect_slot
and never writes connection_slots, so a positive rule would break
reconnect for every auto-connected profile. For the same reason the
probe guard only refuses a change of profile, so reconnecting the
profile the operations slot already holds still works during a task.

The operations guard has no production writer yet (F-74, audit P3-7),
so it is inert at runtime. It ships with a test that flips the guard
directly rather than as an unexercised branch.

Refs: F-19 (audit P2-4).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-27 00:16:33 +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 fix(astrbot): scope stream event ids and fix the transport layer 2026-07-26 23:12:56 +08:00
docs docs(acceptance): record r1/r2 gate closure and pending hardware steps 2026-07-27 00:06:17 +08:00
src fix(pet): restore prettier formatting in the sprite error branch 2026-07-27 00:00:33 +08:00
src-tauri fix(net): reject one profile occupying both runtime slots 2026-07-27 00:16:33 +08:00
tests refactor(ui): complete desktop frontend redesign 2026-07-22 00:27:06 +08:00
.editorconfig chore(repo): initialize repository and ignore rules 2026-07-18 20:22:52 +08:00
.gitignore chore(repo): initialize repository and ignore rules 2026-07-18 20:22:52 +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 docs(changelog): repair keep-a-changelog structure 2026-07-27 00:02:51 +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
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): add stable desktop rendering and context menu 2026-07-20 20:50: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.