Status and limitations
Agent Majlis is experimental and unreleased. There is no supported release line, support SLA or hosted service. Expect breaking changes between development builds.
Harness compatibility
Section titled “Harness compatibility”No harness version has been verified yet. A version is listed as supported only after contract tests against that exact version pass and the fixture hashes are recorded in tests/fixtures/.
| Harness | Versions tested | Status |
|---|---|---|
| Claude Code | none | Unverified. CLI and observe-only fallback until contracts pass. |
| Codex | none | Unverified. CLI and observe-only fallback until contracts pass. |
| Muse | none | CLI-only until versioned contract tests prove each capability. |
| OpenCode | none | CLI-only until versioned contract tests prove each capability. |
| Qwen Code | none | CLI-only until versioned contract tests prove each capability. |
| Junie | none | CLI-only until versioned contract tests prove each capability. |
| Antigravity | none | CLI-only until versioned contract tests prove each capability. |
Untested versions get a visible compatibility warning and observe-only fallback. Experimental parsing never enables strict admission and never marks delivery confirmed.
What Majlis cannot do
Section titled “What Majlis cannot do”- Leases coordinate cooperating agents through hooks. They do not stop a write already in progress, a writer bypassing hooks, an unrelated process, or arbitrary semantic conflicts.
- One daemon and one database serve one OS user. Same-user processes can impersonate one another. Majlis provides no security boundary between them.
- Event history is inspectable, not tamper-proof against the same OS user.
- A missing hook completion means the outcome is unknown. The resource is quarantined, and recovery goes to a fresh worktree, never a destructive reset of the abandoned checkout.
warngaps are best-effort diagnostics. Strictblockandaskmodes deny on outage rather than silently downgrading.- Unknown cost stays unknown. Token counts are never presented as measured dollars.
- Checkpoints are best-effort file states, not atomic filesystem snapshots. Secret redaction is imperfect and exclusion reasons stay visible. Automatic recovery needs a verified, non-uncertain
majlis.checkpoint/v2manifest; v1 manifests are display-only. majlis finishneeds a readable Git worktree and an artifact fingerprint. It fails before running verification when that identity is unavailable.
Platform notes
Section titled “Platform notes”On Windows, file ownership, permission-bit and link-count verification are unavailable in the dependency-free build; binding tokens remain the authentication. majlis doctor lists the exact platform gaps.
Checkpoint retention
Section titled “Checkpoint retention”Bounded maintenance keeps checkpoints for 7 days for accepted or done tasks and 30 days otherwise, measured from capture time, with a 1 GiB logical content target. Pinned, uncertain and last usable copies stay protected, so retained content can exceed that target. Physical Git disk usage is not measured. A failed cleanup needs explicit operator review before retry.