Support overnight research tasks and continuation after restarting

Open
#141 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@prajwal-svm is already working on this.

Since Sep 8, 2026.

Assessment

This issue has not been assessed yet.

Description

area/agents enhancement

Follow-up to #84.

Oleafly 0.4.0 has a saved research-task queue, isolated project copies, cancellation, retry and review before applying results. These tasks run while Oleafly is running. Quitting stops active work, and interrupted runs are recovered for review or retry. Retry starts a new run rather than continuing the previous agent session. Each ACP prompt currently has a 30-minute deadline.

That covers research work alongside the editor, but not the requested overnight or scheduled workflows.

  • Add an explicit way to schedule a research task for later.
  • Define and expose how an unattended run stays active when the app closes, including ownership of a local worker or connected Gateway.
  • Resume an interrupted run from its saved agent session and execution workspace when the backend supports it. If it cannot resume, say so and offer a new run.
  • Support extended runs with visible progress, cancellation and configurable limits; preserve protection against stalled agents.
  • Preserve task dependencies, approvals and project isolation across reconnects or restarts. Never apply manuscript changes without review.
  • Verify an extended run, app restart, agent disconnect and cancellation without duplicate execution or lost results.

Current implementation: task shutdown, retry and interruption recovery, and ACP deadlines.

Dominant language
TypeScript
Stars
838
Forks
50
Avg merge
17h 11m
Merged PRs (30d)
75

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Oleafly/Oleafly

All issues in Oleafly/Oleafly

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.