Ahundt Autorun
ahundt-autorun is a Claude Code plugin for the Operate phase that keeps AI sessions running with persistence policies, stronger planning, and document extraction until tasks complete.
by ahundt · github.com/ahundt/autorun
Install autorun when you need Claude Code or Gemini CLI sessions to persist, follow policies, plan longer jobs, and keep executing—including PDF-to-markdown extraction—until work actually finishes.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install ahundt-autorun@ahundt/autorunBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:ahundt/autorun") and the paste-ready config with skillselion.get_install_config("plugin:ahundt/autorun").
What it does
ahundt-autorun is a small but ambitious automation pack—two plugins—built to keep AI coding sessions alive, structured, and safer across Claude Code and Gemini CLI. Solo builders fighting stop-and-start agents install it when tasks span multiple steps: ingesting PDFs into markdown, executing a plan to completion, or preserving session state when networks or context windows fluctuate. The keyword set emphasizes autonomous policies, persistence, backend document extraction, and a basket of PDF libraries rather than a single happy-path converter. Journey-wide placement fits because the triggers are procedural—run until done, plan better, protect data—usable during validation research, build implementation, ship checklists, and operate iterations alike. It complements planning skills by handling runtime discipline; it is not a replacement for human review of extracted content or security-sensitive PDFs. Expect intermediate setup: policies, session behavior, and extractor dependencies must align with your environment.
Highlights
- Claude Code plugin and Gemini CLI extension in one autorun bundle (2 catalog plugins).
- Autonomous automation with persistence policies so agents keep running toward completion instead of stalling early.
- PDF and document extraction toolchain keywords: docling, markitdown, pymupdf4llm, pdfplumber, pdfminer, pdftotext, and r
- Session support and policy controls aimed at planning better and keeping data safe during long agent jobs.
- Backend-oriented document creation and extraction for knowledge-ingestion workflows.
Why builders use it
Long agent jobs stall, lose context, or quit before deliverables exist—especially when PDF ingestion and multi-step plans need uninterrupted execution.
After installing autorun you get policy-backed persistent sessions on Claude Code or Gemini CLI that continue working through plans and PDF extraction pipelines until the job is done.
At a glance
- Type - Plugin in Automation.
- Adoption - 0 installs, 6 stars, 0 votes.
FAQ
Who is ahundt-autorun for?
Solo developers who rely on long-running Claude Code or Gemini CLI jobs and need persistence, policies, and document extraction without constant manual restarts.
When should I use ahundt-autorun?
Use it whenever a task must survive interruptions—multi-step builds, PDF markdown pipelines, or autonomous plans that should run until completion.
How do I add ahundt-autorun to my agent?
Install the autorun marketplace plugins in Claude Code (and the Gemini CLI extension if you use that stack), configure session and policy settings per the repo README, then enable the PDF extractor plugin you need.
Comments
Share how you use ahundt-autorun, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.