- What is fissible/verdict-console used for in Laravel?
- It is the Artisan console companion and human-in-the-loop approval runtime for Laravel AI agents governed by Fissible Verdict. It lets operators inspect and manage paused, Verdict-gated tool calls instead of allowing an agent to execute them autonomously. It is not a standalone approval system; it depends on laravel/ai and fissible/verdict.
- Do I need fissible/verdict and laravel/ai installed before using this package?
- Yes. It is the third layer in a chain: laravel/ai provides the agent runtime, fissible/verdict provides governance and authorization, and this package adds the approval pause and operator console. Without upstream agents that execute tools and Verdict gating, it has no standalone value.
- How do I install fissible/verdict-console?
- Install it with Composer using composer require fissible/verdict-console. Because it is described as a standard Laravel package, expect a service provider, configuration, and migrations for conversation persistence; confirm the exact publish and migrate commands in the README. You should also satisfy the host contracts before expecting approvals to resume correctly.
- Which Laravel and laravel/ai versions does fissible/verdict-console support?
- The assessment does not document a stable compatibility matrix. The package is pre-1.0 and tightly coupled to laravel/ai internals such as ChatService, ChatTurn, ChatEntry, and approval-resume behavior, and laravel/ai 1.0 already changed approval-resume behavior once. Check composer.json and the README, then run integration tests against your exact Laravel and laravel/ai versions.
- How does the human approval pause work for a Verdict-gated tool call?
- A Verdict-gated pause surfaces as a ToolApprovalRequest: a receipt is issued and the tool is not executed. The console owns this pause geometry and the operator decision boundary, while identity resolution, agent reconstruction, and version tokens are delegated to the host application. Approval resumes only after the host supplies a compatible agent version for that pause.
- What must my Laravel app implement to use fissible/verdict-console?
- Your host must implement ResumableAgents::versionFor(string $key): ?string and bind a ConversationParticipants implementation. If you use streaming, you also need an adapter that drains ChatStream to exhaustion rather than stopping early. Correctness of identity resolution and version-token consistency is entrusted to your host resolver, not enforced by the console.
- Why does a paused approval disappear when streaming an agent response?
- Console ingestion and conversation persistence land only when the stream iterator is exhausted, while the approval receipt is issued at the pause event. If an adapter breaks early because of a client disconnect, timeout, worker kill, or backpressure, you can get an issued receipt with no console record and no persisted conversation. Treat consume-to-completion as a hard requirement and run resumption with reliable queue workers.
- How are approval version tokens validated when resuming a paused tool call?
- Version tokens are opaque and host-supplied, and they are compared by exact equality within the same key only. Null is incomparable, and the package makes no verified equivalence, ordering, or compatibility claim. The invariant that tokens track what resolve would currently rebuild is prose rather than an enforced contract, so a subtly wrong host resolver can resume a pause against an agent configuration the human did not approve.
- Is fissible/verdict-console production ready?
- It is pre-1.0 with breaking minors: v0.12.0 broke ResumableAgents and the project states that in the 0.x line the minor is the breaking release boundary. The assessment notes at least 12 minors, 0 stars, 0 dependents, and no documented commercial support. Governance enforcement for approval resumes now lives in this package, so any path that bypasses the console loses that enforcement. Treat version bumps as migrations and test approval integrity before production use.
- Does the verdict-console operator UI support authentication, tenancy, and audit logging?
- The assessment says the operator UI is the least-documented surface and does not state whether it uses Blade, Livewire, Inertia, or Vue. It also does not document its authorization model, tenancy behavior, or audit story. For a package whose value is human approval, that is the largest unknown; inspect the source and documentation and add host-level access controls before relying on it.