Three defects reported from real-machine testing, all rooted in the same few conflicting CSS blocks, so they are fixed together — separating them would leave intermediate states that render worse than either end. The action buttons showed wrapped vertical text inside a 2rem box. styles.css already defined .message-action-label, a clip-rect screen-reader-only class clearly written for these buttons, but nothing in the tree ever used it: ChatPanel rendered a bare span. Wire the class up so the buttons are icon-only, and drop the border so they read as plain icons rather than pills. .chat-message-actions and its buttons were defined five times across the stylesheet, three of those styling them as bordered pills that the final block then partially overrode. Remove .chat-message-actions button from the three pill rule groups and the small-screen grid rule, leaving one definition next to .message-action-icon. .chat-runtime-actions and .chat-stop-button keep the pill treatment; they are different controls. The avatar rendered below its bubble instead of beside it. .chat-message-row used align-items: flex-end, and .chat-message-content is taller than the bubble because the action bar reserves a row, so the avatar was pinned to the bottom of that taller box. Align to the top. Removing visibility: hidden from the hidden action bar also closes F-40 (audit P2-24): visibility removed the buttons from the tab order, so :focus-within could never fire and a keyboard user could never reveal them. Opacity alone keeps them focusable. Verified against the real stylesheet in a browser: avatar and bubble tops differ by 0px, the button computes to 34x34 with 0px border, the label measures 1x1, and focusing a button takes the bar from opacity 0 to 1. 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 | ||
| 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.