Current Status
There is no first-class Tasks command group in the current CLI implementation.
Tasks are the shared progress and error model for long-running Firestruct
operations, but the terminal does not yet expose task list, task show, or
retry commands. Use the GUI Tasks module when an operation needs monitoring
beyond a single command response.
GUI-Only Coverage Today
Use the macOS Tasks module for:
- active task queue monitoring
- progress and counters
- failed task details
- retry controls
- long-running operation diagnostics
The task queue is especially important for imports, exports, transfers, recursive deletes, deploys, seed applies, migration runs, and large Storage operations. Those workflows can outlive the initiating click or command, so users need status, counters, duration, logs, and actionable errors after work has started.
For CLI planning, every future long-running command should return a task ID when it cannot complete synchronously. Follow-up commands should be able to inspect that ID, print structured status, and retry only when the underlying operation supports safe retry semantics.
Future CLI Shape
Expected future commands:
task list
task show <task-id>
task retry <task-id>
task cancel <task-id>
Cancellation, if added, must be explicit about what has already changed. Some Firebase operations cannot be rolled back once a partial batch has completed.
Source Anchors
Sources/FirestructCore/TaskOrchestrator.swift