bgshell-job

Manage detached background shell jobs with on-disk state tracking.

8|Updated Jun 18, 2026
One-click install
npx skills add https://github.com/vhqtvn/vh-solara --skill bgshell-job
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bgshell-job
Source: https://github.com/vhqtvn/vh-solara/tree/main/.opencode/skills/bgshell-job
Command: npx skills add https://github.com/vhqtvn/vh-solara --skill bgshell-job

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill removes the pain of losing long-running local shell work to session timeouts, compaction, or one-shot command limits. It gives you a durable way to launch, inspect, stop, and resume repo-local background jobs.

Core Features & Use Cases

  • Detached job launch: Start a command in the background and keep its state on disk.
  • Live monitoring: Check job status, process state, timestamps, and recent logs.
  • Stop and recover: Terminate jobs cleanly or forcefully, then resume interrupted or finished work later.
  • Session-aware tracking: Tie jobs to an OpenCode session alias and recover them after context loss.
  • Use case: Helpful for builds, releases, maintenance scripts, and other non-GPU tasks that may outlive a single shell call.

Quick Start

Ask the AI to launch my long-running local shell command as a background job and keep it monitorable, using the bgshell-job workflow.

Frequently Asked Questions about bgshell-job

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

FAQPage Schema
How do I run long shell commands without session timeouts stopping the process?

To prevent session timeouts from stopping long shell commands, launch them as detached background jobs with on-disk state tracking. This ensures persistent monitoring and recovery, allowing local builds and maintenance tasks to outlive a single shell call.

What is the best way to monitor and resume background jobs after a context loss?

The best way to monitor and resume background jobs after context loss is using session-aware tracking. It ties jobs to an OpenCode session alias, keeping process state and logs on disk so you can inspect status and recover interrupted work later.

Can I cleanly stop a background shell job and recover its state later?

Yes, you can cleanly or forcefully stop a background shell job and recover its state later. Process-group handling ensures jobs are terminated safely while on-disk tracking preserves the session state for future resumption or inspection.

Does background job management work for repo-local builds and releases?

Yes, background job management works for repo-local builds and releases. It provides durable launch, live monitoring, and resume operations specifically designed for non-GPU workflows like maintenance scripts that outlive a single OpenCode session.

When should I not use detached background jobs for shell automation?

You should not use detached background jobs for GPU workflows or tasks that complete within a single shell call. This approach is specifically designed for non-GPU repo-local builds and maintenance tasks requiring persistent monitoring and recovery.