Long work.
Still moving.

Name: opencode-loopd
Author: Duy Trinh

Run background goals in OpenCode while your chat stays free.

Install the plugin See how it works

OpenCode plugin for server and TUI. AGPL-3.0-or-later.

Use the models already available in OpenCode

OpenCode

Anthropic OpenAI

DeepSeek

Gemini

One scroll.
The whole system.

Follow one goal from its first prompt through safe parallel work to a verified handoff. Scroll to move the system.

loopd control roomgoal created

Model routing

goal ↗Worker session CHost checks

OpenCode starts a dedicated worker. Parent chat stays available.

File tickets: parallel, not overlapping

Asrc/auth/session.tsclaimed

Bsrc/ui/profile.tsxclaimed

Disjoint files safe parallel work

!src/auth/session.tsheld, waiting

Workers claim exact files. Conflicts wait for release instead of overwriting work.

Queue, release, wake

Worker B, waiting on file ticket

Parked with await_quiescence, no retry loop

Worker A, ticket released

Workspace becomes available

↗ Worker B resumes with release evidence

A release wakes parked work with evidence. No polling, no spinning.

A worker takes the long task.

Create a goal in plain language. OpenCode gives it a dedicated child session while your main conversation stays open.

See the quick start ↗

File tickets keep edits apart.

Each worker claims the exact files it needs. Different files can move in parallel; overlapping claims name the holder and fail safely.

Read the ownership rules ↗

Waiting work wakes on release.

When a ticket is busy, workers park instead of spinning. Releasing the workspace wakes them with context about what changed.

See how coordination works ↗

One session steers many repos.

Register projects, start goals in each, then inspect or steer them from one manager. State and checks stay in the target project.

Explore management mode ↗

More control.
Less babysitting.

Completion is checked

Configured checks run before a goal can report success. Workers must show evidence, not just claim they finished.

Long tasks keep going

Leases, bounded retries, continuation steering, schedules, and recovery help goals progress without manual re-prompting.

Long commands stay usable

Run installs, builds, and dev servers as background command sessions with a fullscreen terminal and explicit stop controls.

Switch models mid-run

Move a goal to another available model while keeping its worker session and progress.

See the whole queue

Use the Loop Dashboard to inspect goals, commands, blocked work, and managed projects without polluting chat.

A real run, not a mock.

Watch an agent create two goals, claim separate files, and coordinate workers through completion.

Two goals, separate file tickets

Good questions.

What is opencode-loopd?

An OpenCode plugin that supervises background goals. OpenCode runs worker sessions; loopd manages goals, checks, budgets, schedules, coordination, and the dashboard.

Do I need to know how to code?

You can create a goal in plain language. OpenCode still needs to be installed and configured with a model and agent.

How do workers avoid editing the same file?

Workers claim exact file paths before editing. Disjoint claims can run concurrently; conflicts return owner and path details. Read-only goals do not reserve source files.

Can I manage goals in other projects?

Yes. Register target directories, create goals with a directory, then inspect and steer across projects from one manager session.

How do I install it?

Add @bojackduy/opencode-loopd to the OpenCode server and TUI plugin settings, restart OpenCode, then run /goal or open /loop.

Let the goal
keep going.

Install the OpenCode plugin, describe the work, and keep your main conversation moving.

Install opencode-loopd ↗ View on GitHub

Long work.Still moving.

One scroll.The whole system.