Adding an AstrBot connection asked for eleven fields. Three of them reach nothing: the SSE URL has no consumer anywhere in networking (the desktop transport builds its own endpoint and AstrBot never reads it), the certificate fingerprint is stored but TLS pinning is not implemented, and the role only decides a word in the profile list. The form is now the four things an activation actually requires — server address, adapter id, API key, slot — with everything else behind a collapsed advanced section. The adapter id is the remote username. It was previously entered twice, once in the profile form and again in the credential card, and it is what keeps two slots on one server from sharing a conversation, so the field now says that. Three values are derived rather than asked for. The display name falls back to identity@host. The role follows the chosen slot. The insecure HTTP approval appears only for an http:// address and is required there, because normalize_url rejects such an address without it — showing it unconditionally invited enabling it for an https:// endpoint that never needed it. Choosing a slot now does the whole job: it assigns the slot, sets the role, and points startup auto-connect at it, replacing a separate slot card interaction and a separate auto-connect slot dropdown that could disagree with each other. The API key is enrolled in the same submit. Both steps need the profile to exist, so they run after the save and report their own failures rather than failing the save. Verified in a browser against the real stylesheet: four fields plus a collapsed advanced section, the insecure checkbox appears only for http:// and carries required, and the display name placeholder resolves to identity@host. 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.