Can LibreTask work without staying open?
Task state is persisted, and the execution model is designed to survive application interruptions. The current preview is validating recovery across real workflow boundaries before making broader availability claims.
When does it stop for a human decision?
The task contract defines required checkpoints. LibreTask can also pause at ambiguity, an external side effect, a policy boundary, a failure, or a budget threshold.
Does every result include evidence?
The delivery package is designed to include the result, acceptance checks, execution history, source evidence, and unresolved questions. A final chat response alone is not treated as a complete delivery.
Is everything stored only on my device?
Task state is local-first. Some external capabilities may send data to an approved destination when the task contract allows it. The capability and boundary are visible before invocation.
Which tools and models can it use?
The architecture supports MCP, OpenAPI, CLI, and local adapters through capability contracts. Availability in the private preview is intentionally narrower than the long-term architecture.
Can I sync tasks across devices?
Cross-device synchronization and collaboration are roadmap items. The first product prioritizes one reliable local execution loop before cloud dependencies are introduced.