Skip to content

AGENTS.md

Latest commit

 

History

History
63 lines (44 loc) · 2.44 KB

AGENTS.md

File metadata and controls

63 lines (44 loc) · 2.44 KB
Raw

opencodeR Agent Workflow

Automatic repo issue tracking

At the start of each session and every 30 minutes, the agent:

  1. Checks github.com/grave0x/opencodeR for open issues via gh issue list
  2. Compares against the current TODO list
  3. Adds any new issues as pending tasks with tag github-issue-#N
  4. Reports summary

Cron schedule

A recurring cron task fires every 30 minutes (*/30 * * * *, id: 1247c3bf) and runs:

  1. gh issue list -R grave0x/opencodeR → sync new issues into the TODO list (tag github-issue-#N)
  2. scripts/check-upstream-updates.sh (7-day window) → report relevant upstream PRs + drafts

Manage it with:

  • List: /tasks or CronList
  • Cancel: CronDelete 1247c3bf
  • Modify: CronCreate with new schedule, then CronDelete the old one

Manual trigger

Run /check-issues or invoke the check-repo-issues skill directly.

Upstream watch (local automation)

scripts/check-upstream-updates.sh watches merged PRs on the upstream opencode repo (anomalyco/opencode) and maps relevant ones to opencodeR touchpoints:

  • Default: last 7 days of merged PRs; --days N to change the window
  • Classifies by area (mcp, plugin, provider, permission, storage, llm, shell) and maps each to the affected crates/* files
  • Flags stub touchpoints (e.g. crates/plugin/src/lib.rs)
  • Writes spec'd issue drafts to .upstream-updates/; --publish files them as GitHub issues (labels bug/enhancement — both must exist in the target repo)
  • --cargo also summarizes cargo update --dry-run

Run it alongside the issue check (/check-issues) at session start.

Launching a kimi terminal

scripts/start-kimi.sh starts Kimi Code in the opencodeR workspace with this workflow loaded. Default is a new session; -c resumes the most recent session (keeps the session-scoped cron), -s [id] resumes a specific one, -a <agent> / -m <model> set the starting agent/model, and -- passes extra flags through. -p "<prompt>" runs non-interactively (no TUI).

Task conventions

  • Each TODO list item maps to one deliverable
  • Tags: github-issue-#N for repo issues, feature-#N for roadmap features
  • Status transitions: pending → in_progress → done
  • Blocked items note the blocker in the title

Release workflow

Tag pushes (v*) trigger .github/workflows/release.yml which:

  • Builds for Linux x86_64, Linux ARM64, Windows x86_64
  • Creates .deb, .rpm, and Arch packages
  • Uploads all artifacts to the GitHub Release