convez.ai
MCP ServerAutomaçãoIntermediário
RohitYajee8076

Backburner — Tarefas em Segundo Plano para Agentes IA

RohitYajee8076/backburner

Execute tarefas longas em background sem travar seu agente IA

Ver no GitHub
InicialPluginScore · de 0 a 100

MCP server que permite agentes de IA executar comandos shell de longa duração como tarefas em background, liberando o agente para continuar trabalhando enquanto a tarefa é processada. Funciona sem infraestrutura externa (SQLite + subprocess), sobrevive a reinicializações, e oferece controle via policies de comando.

Instalação

$npx convez-ai RohitYajee8076/backburner

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
2
Forks
0
Acompanhando
0
Saúde
42%
Último commit
há 3 meses
Versão
v1.0.0
Issues abertas
0
Contribuidores
1

Casos de uso

  • Executar testes automatizados enquanto o agente continua analisando código
  • Disparar builds, scrapes ou batch jobs que demoram minutos/horas
  • Monitorar progresso de tarefas em tempo real com peek de output
  • Gerenciar múltiplas operações paralelas com segurança e timeouts

Veredito

Solução prática e bem-testada para o problema real de agentes bloqueados em operações longas. Implementação minimalista (sem dependências pesadas) com suporte a cancellation real, crash recovery e policy de segurança — exatamente o que a spec Tasks do MCP formaliza.

README

A tradução para o português deste README ainda está na fila.

Put your AI agent's slow work on the back burner. Keep cooking.

Background Tasks  ◦  Zero Infrastructure  ◦  Survives Restarts  ◦  Windows & Unix

📦 PyPI  •  🗂️ MCP Registry  •  🐛 Issues  •  📄 MIT


📢 Updates

  • v0.2.1 — output with non-ASCII characters (✓, emoji, any non-English text) no longer crashes tasks on Windows.
  • v0.2.0 — exit_code is no longer reported for cancelled/timed-out tasks (it was an artifact of the kill, not a real result); new animated demo below.
  • v0.1.x — first release: 5 tools, task timeouts, command allow/deny policy. Listed on the official MCP Registry as io.github.RohitYajee8076/backburner.

backburner is an MCP server that gives any AI assistant (Claude, and any other MCP client) the ability to run long shell commands as background tasks — start a test suite, a build, a scrape, a batch job — then keep working and check back for the results, instead of sitting frozen until it finishes.

backburner demo

🔥 Why

AI agents are bad at waiting. A tool call that takes 10 minutes blocks the whole conversation — or times out and loses the work entirely. The MCP specification is formalizing a Tasks pattern for exactly this problem (extension finalized in the 2026-07-28 spec release); backburner brings that workflow to every client today via plain tools, with first-class Tasks-extension support on the roadmap.

🧰 Tools

ToolWhat it does
start_task(command, cwd?, timeout_seconds?)Run a shell command in the background, returns a task id immediately
task_status(task_id)working / completed / failed / cancelled / timed_out / interrupted
task_result(task_id, tail_lines?)Captured output — works mid-run too, so you can peek at progress
cancel_task(task_id)Kill the task and its whole process tree
list_tasks(limit?)Recent tasks, newest first

✨ Features

  • Survives restarts — tasks are tracked in SQLite under ~/.backburner/; output is captured to per-task log files. If the server dies mid-task, orphaned tasks are honestly marked interrupted, never silently lost.

  • Real cancellation — kills the full process tree (worker processes included), on Windows and Unix.

  • Peek at live progress — task_result on a running task returns the output so far.

  • Timeouts — pass timeout_seconds and a runaway task is killed and honestly marked timed_out instead of hanging forever.

  • Command policy — restrict what the AI may run with environment variables (regexes, comma-separated; deny always wins):

    BACKBURNER_ALLOW="^pytest,^npm (test|run build)"   # only these may run
    BACKBURNER_DENY="rm -rf,shutdown,format"           # these never run
    
  • Zero infrastructure — stdlib only (SQLite, subprocess, threads). No Redis, no Celery, no Docker.

  • Tested — a pytest suite covers the full job lifecycle: completion, failure, cancellation, timeouts, crash recovery, and the command policy.

🚀 Install

pip install backburner-mcp

Claude Code

claude mcp add backburner -- python -m backburner.server

Claude Desktop / other clients

{
  "mcpServers": {
    "backburner": {
      "command": "python",
      "args": ["-m", "backburner.server"]
    }
  }
}

🔒 Security note

backburner executes the shell commands the AI sends it, with your user's permissions. That is its job — but treat it like giving your agent a terminal. Run it only with clients whose tool-use you review/approve, prefer permission modes that require confirmation for start_task, and use BACKBURNER_ALLOW / BACKBURNER_DENY to scope what may run.

🗺️ Roadmap

  • Task timeouts and max-runtime limits
  • Allowlist/denylist for commands
  • PyPI release — pip install backburner-mcp
  • Listed on the official MCP Registry
  • MCP Tasks extension support (spec 2026-07-28) — native tasks/get, tasks/cancel alongside the plain tools
  • Local web dashboard — watch tasks live in the browser
  • Structured progress reporting (parse % / step markers from output)

📄 License

MIT

Ver o original no GitHub

Bom para

Relacionados