task-bg

Launch and monitor Factory Droid background tasks via background-manager.py.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/qazz92/oh-my-droid --skill task-bg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-bg
Source: https://github.com/qazz92/oh-my-droid/tree/main/oh-my-droid/skills/task-bg
Command: npx skills add https://github.com/qazz92/oh-my-droid --skill task-bg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Task-bg enables parallel execution of droid tasks by manual background management, addressing the lack of built-in run_in_background support in the Factory Droid CLI.

Core Features & Use Cases

  • Launch droids as background tasks via background-manager.py
  • Track, monitor, and collect outputs
  • Clean up completed tasks and handle orphaned ones
  • Use cases include long-running builds, test suites, and parallel orchestration of multiple droids

Quick Start

Launch a background task with a brief description and prompt, then monitor progress and retrieve outputs as needed.

Frequently Asked Questions about task-bg

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run parallel droid tasks in the background when the CLI lacks native support?

You can run parallel droid tasks by manually launching them as background processes via a background manager, which tracks execution in ~/.factory/.omd/background-tasks and collects outputs.

What is the best way to manage long-running builds and test suites with Factory Droid?

Managing long-running builds and test suites is best handled by launching droids as background tasks, allowing you to monitor progress and collect outputs without blocking the CLI.

How do I track and clean up orphaned background tasks on my machine?

You can track and clean up orphaned background tasks using the background manager, which monitors active processes in ~/.factory/.omd/background-tasks and handles cleanup for completed or abandoned runs.

Does Factory Droid support concurrent orchestration of multiple droids?

Concurrent orchestration of multiple droids is supported by manually managing parallel background processes, enabling you to launch, monitor, and retrieve outputs for simultaneous tasks.

Why do my long-running droid tasks block the CLI instead of running asynchronously?

Long-running droid tasks block the CLI because it lacks built-in run_in_background support, requiring a manual background process manager to enable asynchronous execution and output collection.

Can I collect outputs from multiple parallel droid executions after they finish?

You can collect outputs from parallel droid executions through the background manager, which tracks each task in ~/.factory/.omd/background-tasks and allows you to retrieve results upon completion.