Known issues (beta)

Known issues (beta)

Track: Jarvis v0.3.0-beta.1 and subsequent beta tags
Updated: 2026-07-21
Bug path: https://git.sovereign-society.org/libertaria/Jarvis/issues

Before filing a bug, check this list. Workarounds keep pilots unblocked; they are not permanent design.


Packaging & install

ID Issue Impact Workaround / status
KI-01 Binary is glibc-linked (Phase A), not musl fully static Copy-anywhere “any Linux” is limited to glibc hosts Use Debian/Ubuntu/Fedora/Arch-class hosts; Phase B = musl static if pilots need it
KI-02 Forgejo Actions runners may be empty Tag push may not build/publish assets Maintainers run ./scripts/release-binary.sh then scripts/ci-publish-release.sh
KI-03 Release tarball can lag local EE image Glass endpoints missing if tarball predates Wave 5 Prefer image built with USE_LOCAL=1 after current release-binary; re-publish release when tagging
KI-04 AUR jarvis-bin may be local PKGBUILD only yay/public AUR not guaranteed until maintainer publish cd packaging/aur/jarvis-bin && makepkg -si against a release asset
KI-05 EE image is Debian Trixie, not pure Wolfi Larger base than distroless ideal Accept for beta; Wolfi needs Phase B static/musl entrypoint
KI-06 EE container first-run setup.toml missing jarvis doctor reports NOT READY inside fresh volume Run jarvis setup --home $JARVIS_HOME once in the volume (or podman exec); host CE setup is independent

Setup & doctor

ID Issue Impact Workaround / status
KI-10 First model reply needs a reachable preset (Ollama/OpenAI/etc.) Setup READY ≠ chat works offline jarvis setup --preset ollama with local server, or --preset openai + key
KI-11 jarvis doctor sections may show warn when Podman is down Sandbox falls back / host path Install/start rootless Podman; or explicit JARVIS_SANDBOX=host for debug only
KI-12 jarvis version / --version missing on v0.3.0-beta.1 stage tarball G7 version string awkward Use Glass GET /health version field, or rebuild from main (Wave 6 adds version / --version / -V; override with JARVIS_VERSION)

Cockpit (TUI)

ID Issue Impact Workaround / status
KI-20 TUI requires a real TTY No Cockpit over dumb pipes Use a terminal; Glass for remote observe
KI-21 SPEC-023 not 15/15 Some luxury slash UX still missing Beta checklist is chat/model/approvals/fleet strip, not full parity

Glass (WebUI)

ID Issue Impact Workaround / status
KI-30 Public /app defaults to Preview (simulated) Looks “live” without your harnessd Badge preview · simulated; set Settings API base + token for real data
KI-31 Glass is read-only in beta Cannot approve/deny from PWA Use CLI/TUI for mutations
KI-32 Glass PEP may show cap/default, not full ledger Incomplete policy picture in UI Trust CLI doctor/policy for authority; Glass is observe
KI-33 Token scope mistakes (admin env reused) Over-privileged observer Prefer dedicated read token; send X-Jarvis-Scope: read
KI-34 No public shared demo token Marketing cannot hit a shared fleet Preview mockup is intentional; private demo only after scrubbed home

Containers & sandbox

ID Issue Impact Workaround / status
KI-40 Agent sandbox from inside container needs host Podman socket Nested Podman painful Mount host socket per container docs; or run agent sandboxes on host CE binary
KI-41 Host Podman storage warnings Noisy ops, rare flakes Host hygiene; not product P0
KI-42 Ambient home is denied for agent boxes by default Scripts expecting $HOME configs fail Pass project files; S3 allowlist for explicit extra paths

Out of beta (not bugs)

These are deferred scope, not regressions:

  • Full SPEC-023 Cockpit parity
  • Signal / Matrix chat platforms (Telegram: Wave C6 MVP)
  • Factory full auto / --auto as default
  • SPEC-015 elastic remote sandbox provider
  • Host MAC (AppArmor/SELinux) S5
  • Multi-tenant SaaS

Version check

jarvis --version

Cite the string and install method in every issue report.