Merge pull request #2 from githubnext/install-autoloop

Install Autoloop

Author: mrjf

.github/ISSUE_TEMPLATE/autoloop-program.md

@@ -0,0 +1,49 @@
+---
+name: Autoloop Program
+about: Create a new Autoloop optimization program
+title: ''
+labels: autoloop-program
+---
+
+<!-- AUTOLOOP:ISSUE-PROGRAM -->
+<!-- This issue defines an Autoloop program. The format is identical to program.md files. -->
+<!-- Autoloop will discover this issue by its label and run iterations automatically. -->
+<!-- After each run, a status comment will be posted/updated with links and results. -->
+
+---
+schedule: every 6h
+# target-metric: 0.95  ← uncomment and set to make this a goal-oriented program that stops when reached
+---
+
+# Program Name
+
+## Goal
+
+<!-- Describe what you want to optimize. Be specific about what 'better' means. -->
+<!-- Choose one of the following program types: -->
+<!-- • Goal-oriented: Has a finish line. Set target-metric above and describe the target here. -->
+<!--   Example: "Increase test coverage to at least 95%." -->
+<!-- • Open-ended: Runs forever, always seeking improvement. Leave target-metric commented out. -->
+<!--   Example: "Continuously improve algorithm performance." -->
+
+REPLACE THIS with your optimization goal.
+
+## Target
+
+<!-- List files Autoloop may modify. Everything else is off-limits. -->
+
+Only modify these files:
+- `REPLACE_WITH_FILE` -- (describe what this file does)
+
+Do NOT modify:
+- (list files that must not be touched)
+
+## Evaluation
+
+<!-- Provide a command and the metric to extract. -->
+
+```bash
+REPLACE_WITH_YOUR_EVALUATION_COMMAND
+```
+
+The metric is `REPLACE_WITH_METRIC_NAME`. **Lower/Higher is better.** (pick one)

.github/agents/agentic-workflows.agent.md

@@ -19,6 +19,7 @@ This is a **dispatcher agent** that routes your request to the appropriate speci
 - **Creating shared components**: Routes to `create-shared-agentic-workflow` prompt
 - **Fixing Dependabot PRs**: Routes to `dependabot` prompt — use this when Dependabot opens PRs that modify generated manifest files (`.github/workflows/package.json`, `.github/workflows/requirements.txt`, `.github/workflows/go.mod`). Never merge those PRs directly; instead update the source `.md` files and rerun `gh aw compile --dependabot` to bundle all fixes
 - **Analyzing test coverage**: Routes to `test-coverage` prompt — consult this whenever the workflow reads, analyzes, or reports on test coverage data from PRs or CI runs
+- **CLI commands and triggering workflows**: Routes to `cli-commands` guide — consult this whenever the user asks how to run, compile, debug, or manage workflows from the command line, or when they need the MCP tool equivalent of a `gh aw` command
 
 Workflows may optionally include:
 
@@ -129,6 +130,17 @@ When you interact with this agent, it will:
 - "Analyze coverage trends over time"
 - "Add a coverage gate that blocks PRs below a threshold"
 
+### CLI Commands Reference
+**Load when**: The user asks how to run, compile, debug, or manage workflows from the command line; needs the MCP tool equivalent of a `gh aw` command; or is in a restricted environment (e.g., Copilot Cloud) without direct CLI access.
+
+**Reference file**: https://github.com/github/gh-aw/blob/main/.github/aw/cli-commands.md
+
+**Use cases**:
+- "How do I trigger workflow X on the main branch?"
+- "What's the MCP equivalent of `gh aw logs`?"
+- "I'm in Copilot Cloud — how do I compile a workflow?"
+- "Show me all available gh aw commands"
+
 ## Instructions
 
 When a user interacts with you:
@@ -147,6 +159,10 @@ gh aw init
 # Generate the lock file for a workflow
 gh aw compile [workflow-name]
 
+# Trigger a workflow on demand (preferred over gh workflow run)
+gh aw run <workflow-name>             # interactive input collection
+gh aw run <workflow-name> --ref main  # run on a specific branch
+
 # Debug workflow runs
 gh aw logs [workflow-name]
 gh aw audit <run-id>
@@ -174,4 +190,7 @@ gh aw compile --validate
 - Workflows must be compiled to `.lock.yml` files before running in GitHub Actions
 - **Bash tools are enabled by default** - Don't restrict bash commands unnecessarily since workflows are sandboxed by the AWF
 - Follow security best practices: minimal permissions, explicit network access, no template injection
+- **Network configuration**: Use ecosystem identifiers (`node`, `python`, `go`, etc.) or explicit FQDNs in `network.allowed`. Bare shorthands like `npm` or `pypi` are **not** valid. See https://github.com/github/gh-aw/blob/main/.github/aw/network.md for the full list of valid ecosystem identifiers and domain patterns.
 - **Single-file output**: When creating a workflow, produce exactly **one** workflow `.md` file. Do not create separate documentation files (architecture docs, runbooks, usage guides, etc.). If documentation is needed, add a brief `## Usage` section inside the workflow file itself.
+- **Triggering runs**: Always use `gh aw run <workflow-name>` to trigger a workflow on demand — not `gh workflow run <file>.lock.yml`. `gh aw run` handles workflow resolution by short name, input parsing and validation, and correct run-tracking for agentic workflows. Use `--ref <branch>` to run on a specific branch.
+- **CLI commands reference**: For a complete guide on all `gh aw` commands and their MCP tool equivalents (for restricted environments), see https://github.com/github/gh-aw/blob/main/.github/aw/cli-commands.md

.github/mcp.json

@@ -0,0 +1,11 @@
+{
+  "mcpServers": {
+    "github-agentic-workflows": {
+      "command": "gh",
+      "args": [
+        "aw",
+        "mcp-server"
+      ]
+    }
+  }
+}