LinuxCommandLibrary

gh-agent-task

Execute a GitHub Actions agent task

TLDR

List the most recent agent tasks

$ gh [[agent|agent-task]] list
copy

Create a new agent task for the current repository
$ gh [[agent|agent-task]] create "[Improve the performance of the data processing pipeline]"
copy

Create a new agent task from a file
$ gh [[agent|agent-task]] create [[-F|--from-file]] [path/to/file]
copy

View details about a specific agent task
$ gh [[agent|agent-task]] view [session_id|pr_number|url|branch]
copy

Show the log of a specific agent task
$ gh [[agent|agent-task]] view --log [session_id|pr_number|url|branch]
copy

SYNOPSIS

gh-agent-task <task> [options] [args]

PARAMETERS

-h, --help
    Display help message and exit

--task <name>
    Specify the agent task to execute (e.g., 'setup', 'run-job')

--runner <id>
    Target runner ID for the task

--verbose
    Enable verbose logging

--dry-run
    Simulate task without execution

DESCRIPTION

The gh-agent-task command appears to be a non-standard or internal utility potentially associated with GitHub's CLI (gh) ecosystem, possibly for managing agent tasks in GitHub Actions runners or extensions. It is not part of the official GitHub CLI distribution and does not appear in standard Linux man pages or common package repositories like apt, yum, or brew for gh CLI.

Analysis indicates it may be a custom or proprietary script/binary used in self-hosted GitHub Actions environments to execute specific agent-level tasks, such as job dispatching, artifact handling, or runner diagnostics. Without official documentation, usage is speculative and risky. No public source code or man page was found. It might be invoked by GitHub Actions runner software internally.

Recommendation: Verify in your specific GitHub Enterprise or custom runner setup. Standard alternatives include gh run or runner binaries like run.sh.

CAVEATS

Not officially documented; may not exist in standard installs. Running undocumented binaries risks security issues. Check GitHub Actions runner logs or source for context. Potential for environment-specific behavior only.

SECURITY NOTE

Avoid executing unknown binaries. Verify hash against official GitHub releases.

ALTERNATIVES

Use gh workflow run for triggering Actions or ./run.sh in runner directories.

HISTORY

Likely emerged post-2020 with GitHub Actions self-hosted runners v2+. No public changelog; possibly internal to github.com/actions/runner repo.

SEE ALSO

gh(1), act(1), run.sh(8)

Copied to clipboard