Skip to main content
Archductor is in active development. This is the honest list of what is still rough, so you can decide whether it fits your workflow today.

​
Known limits

  • Terminal. Common ANSI and control redraws work; it is not a full terminal emulator. Programs that assume one may render incorrectly.
  • Review threads. Resolving and reopening GitHub review threads is CLI-only (archductor pr resolve-thread, archductor pr reopen-thread).
  • Settings. The schema and the Settings UI accept keys the daemon does not act on yet — notably every [customization.automation] lifecycle hook. The settings reference marks each key.
  • Appearance and keybindings. Repository-level view settings exist in the schema, but the desktop app reads its own per-machine preferences. Change them in Settings.
  • Agent profiles. Profile names are surfaced; profiles do not yet drive session launches.
  • Platform. Linux is the validated target. Windows compiles and packages but its runtime checklist has not passed. macOS builds and smoke-tests.
  • Packaging. Perceo-owned APT and DNF repositories are live for Linux desktop installs, and perceo-ai/homebrew-tap is live for CLI/headless installs. Official Debian, Fedora, and Homebrew/core submissions are separate human-owned processes. Flatpak is experimental pending Flathub review — arbitrary repository access needs broad filesystem permissions.
  • Approval policy. There is no product policy yet for Codex unsafe-approval or sandbox bypass. Set approval modes deliberately, per session.

​
Verify before you install

Release artifacts ship with checksum manifests. CLI artifacts are listed in SHA256SUMS; Linux desktop packages are listed in SHA256SUMS-desktop-linux.txt. The public APT and DNF repositories at https://www.perceo.ai/apt and https://www.perceo.ai/rpm are signed with fingerprint 55C0 EB36 2097 45CE D529 18FF 929C EA68 D5E8 E8D0.
If a release includes provenance or attestations, verify those before trusting the artifact.

​
Package channels

Official Debian, Ubuntu, Fedora, and Homebrew/core listings require human submission and maintainer review. Do not treat the Perceo-owned repositories as those official distribution submissions.

​
Repository references

The repository carries operational detail that does not belong in product docs:

Current progress

Short current-state source, updated as work lands.

External API

Transports, protocol envelope, MCP surface, stability policy.

Deploy and local test

Release and local verification steps.

Manual testing checklist

What gets exercised by hand before a tag.