Date: 2026-06-06
Scope: options for reliable PM → Development → Testing autonomous work cycles for the obot-claw GitHub portfolio.
obot-claw.github.io issue: Copilot cloud agent if available; otherwise Codex/Claude through GitHub third-party agent support if enabled.| Pattern | Seen in | Why it matters for obot |
|---|---|---|
| Issue/task assignment creates a run | GitHub Copilot cloud agent, Jules, Paperclip, Devin | Maps directly to our Project / Requirement / Task issue model. |
| Run/session record stores status | OpenClaw tasks, Paperclip heartbeats, Devin sessions | Prevents the exact failure we hit: invisible or missing work being reported as active. |
| Agent works in isolated environment | Codex cloud, Copilot cloud agent, Jules, Devin, OpenHands | Reduces dirty worktree risk and makes outputs reviewable as PRs. |
| Human review remains terminal authority | GitHub Copilot, Jules, Devin, Codex | Matches Jeremy's preference: agents can build; humans decide/merge. |
| Explicit logs/session playback | GitHub Copilot session logs, Devin shell/IDE/browser, OpenClaw sessions/tasks | Required for reliable status and failure diagnosis. |
Best near-term fit
OpenClaw already has a background task ledger for ACP runs, subagents, cron jobs, and CLI operations. Tasks move through queued/running/terminal states and can become lost if backing state disappears. OpenClaw sessions also expose stored session rows and trajectory export/tail commands.
Pros: already installed; aligns with Telegram/heartbeat; keeps local privacy; lowest migration cost.
Cons: current Telegram runtime did not expose the right first-class session tools, and the CLI fallback hit sandbox permission problems. Needs configuration/tooling repair before true autonomous cycles are safe.
Use it for: immediate supervision, liveness checks, cron/TaskFlow-backed work blocks, and status reporting.
Best strategic path if available
GitHub Copilot cloud agent can research, plan, make code changes, and open or update pull requests from issues, GitHub.com, VS Code, or automations. GitHub also documents third-party coding agents such as Claude and Codex that can be assigned to issues or mentioned on PRs.
Pros: issue-to-PR lifecycle is built in; session logs live where review happens; branch/PR/review is native; custom agents can specialize; security controls are documented.
Cons: availability depends on GitHub/Copilot plan and org settings; third-party agent access may require GitHub App enablement; task updates after assignment may need to happen on the PR, not only the issue.
Use it for: routine GitHub implementation tasks once obot-claw org settings support it.
Promising but needs sandbox pilot
Paperclip describes agents as workers that wake for heartbeats, run an adapter such as Claude Code CLI, check assignments, claim tasks, update status, and store run results for audit/debugging. It also has explicit agent identity, session persistence, and status states.
Pros: very close to our desired PM/Dev/Testing agent model; not tied to one agent runtime; gives us org structure, tasks, budgets, approvals, status, and run records.
Cons: newer system; likely operational overhead; would need careful privacy/security review; should not be wired into production obot until a small repo pilot proves it is stable.
Use it for: an experiment coordinating PM/Dev/Testing agents around a toy or low-risk public repo.
Useful execution engine, not full coordinator
OpenAI's Codex CLI is a local coding agent. OpenAI also describes Codex cloud tasks as running in secure isolated containers with repo-provided code and dependencies. Codex usage is tracked across local and cloud clients through OpenAI's compliance/usage surfaces.
Pros: we already use Codex-style local development effectively; strong coding model; compatible with AGENTS.md; can be wrapped by OpenClaw/cron/Paperclip.
Cons: local CLI is not itself a durable multi-agent scheduler; our current sandbox blocked OpenClaw CLI fallback writes; cloud access and GitHub integration need explicit setup.
Use it for: coding execution inside a better run manager, not as the run manager.
Viable alternatives by use case
Claude Code GitHub Actions can respond to mentions on issues/PRs and create PRs through GitHub Actions. OpenHands provides a self-hostable agent SDK, CLI, local GUI, REST API, and cloud option. Devin and Jules are hosted asynchronous software engineering agents that emphasize parallel backlog tasks, PRs, and human review.
Pros: mature async development patterns; better out-of-box session visibility than our current ad hoc loop.
Cons: varying cost, vendor lock-in, setup, and repo access implications. Some are hosted systems, so private context and credentials need strict review.
Use it for: comparison pilots after GitHub-native availability is checked.
Do not start here
OpenAI Agents SDK, Microsoft Agent Framework, LangGraph, CrewAI, and AutoGen-style systems are useful when building an application that orchestrates agents. They offer patterns such as handoffs, agents-as-tools, graph workflows, checkpointing, and human-in-the-loop controls.
Pros: flexible; strong for custom workflows and PM/research/planning agents.
Cons: they do not automatically provide GitHub issue assignment, PR creation, code sandboxing, session logs, or deployment checks. We would still need to build those operational pieces.
Use it for: later, if we need a custom PM planner or evaluator loop after adopting a proven execution substrate.
obot-claw: Copilot cloud agent, third-party Codex/Claude agents, required plans/settings/GitHub Apps.| Path | Reliability | Setup cost | GitHub fit | Privacy/control | Recommendation |
|---|---|---|---|---|---|
| OpenClaw + PR #26 | Medium now; high after tooling repair | Low | Medium | High | Use immediately as guardrail. |
| GitHub-native agents | High if enabled | Medium | High | Medium | Pilot next. |
| Paperclip | Unknown but architecturally relevant | Medium/high | Medium | Medium/high if self-hosted | Research pilot only. |
| Codex CLI wrapper | Medium | Low/medium | Medium | High local | Use as execution engine, not scheduler. |
| OpenHands | Medium/high | Medium/high | Medium | High if self-hosted | Consider after GitHub-agent pilot. |
| Devin/Jules | Medium/high | Low/medium | High | Lower, hosted | Useful benchmark, not first choice. |
| Agents SDK/LangGraph/CrewAI/MS Agent Framework | Depends on implementation | High | Low without extra work | High if self-built | Do not use for dev execution yet. |
PR #26 should be treated as a minimum viable safety layer, not the final orchestration platform. It should prevent false status reports while we evaluate better off-the-shelf execution/control planes. If a GitHub-native or Paperclip-like control plane wins, the #26 ledger can either become a compatibility adapter or be retired.