Skip to content

feat: Autonomous task continuation with task-based checkpoints and rollback #19384

Closed as not planned

Description

@aegntic

Summary

Add autonomous task continuation capability to OpenCode that enables:

  1. Task-based checkpoints - Snapshots created on task completion, not time-based
  2. Automatic continuation - Suggested next steps become the next prompt automatically
  3. Rollback capability - Revert to any checkpoint when things go wrong

Motivation

Currently, OpenCode sessions require manual intervention between tasks. Users must:

  1. Complete a task
  2. Manually identify the next task
  3. Enter the next prompt

This feature enables a more autonomous workflow where:

  • Checkpoints are created automatically when tasks complete
  • The next suggested step becomes the next prompt
  • Users can rollback to any previous state if something breaks

Proposed Solution

Add a built-in autonomous mode that:

  • Creates checkpoints on task/tool completion
  • Maintains a queue of pending tasks
  • Enables automatic continuation to next task
  • Provides rollback to any checkpoint

Use Cases

  1. Long-running development sessions - Build complex features without constant manual prompting
  2. CI/CD pipelines - Automate multi-step development tasks
  3. Batch operations - Process multiple related tasks sequentially

Implementation Approach

The feature could be implemented as:

  • Built-in OpenCode command (/autonomous)
  • Task queue management
  • Checkpoint system using workspace snapshots + git state
  • Rollback commands

Checklist

  • This PR references an existing issue
  • I have tested this feature
  • Documentation will be updated

Activity

  1. added
    coreAnything pertaining to core functionality of the application (opencode server stuff)
    on Mar 27, 2026
  2. github-actions commented on Mar 27, 2026

    @github-actions
    Contributor

    This issue doesn't fully meet our contributing guidelines.

    What needs to be fixed:

    • The title does not start with [FEATURE]: as required for feature requests
    • The checklist included is a PR checklist, not the feature request verification checkbox required by the feature request template
    • Please use the official Feature Request issue template, which requires a verification checkbox confirming the feature hasn't been requested before

    Please edit this issue to address the above within 2 hours, or it will be automatically closed.


    This issue might be a duplicate of existing issues. Please check:

    If you believe this was flagged incorrectly, please let a maintainer know.

  3. added a commit that references this issue on Mar 27, 2026
    1c46a09
  4. github-actions commented on Mar 27, 2026

    @github-actions
    Contributor

    This issue has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.

    Feel free to open a new issue that follows our issue templates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

coreAnything pertaining to core functionality of the application (opencode server stuff)

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions