Skip to main content
This walkthrough is written for analysts and coordinators who just want the official task templates in their workspace—no coding required.
The command group is now task library. Older instructions may still reference task builtins; the CLI accepts both names but gently nudges you toward the new one.

​
Step 1 · Refresh the library index

Run this whenever you want to check for updates. It takes only a moment. 
autocleaneeg-pipeline task library update
  • Working offline? Add --no-network. The CLI will skip the Internet check and use the last snapshot it stored locally.
  • Behind a firewall? If the request fails the CLI will tell you once and remember the reason so you know you are using cached templates.

​
Step 2 · See what is available

autocleaneeg-pipeline task library list --show-paths
Read the table like this:
  • Status shows whether the template is already in your workspace.
  • Source tells you where the file came from (local download = GitHub, bundled snapshot = shipped with the app).
  • Add --refresh to combine step 1 and 2 in a single command.

​
Step 3 · Copy a template into your workspace

autocleaneeg-pipeline task library install RestingEyesQuickCheck
What happens:
  1. The file is downloaded (or taken from the bundled snapshot if you are offline).
  2. A copy is placed in your workspace tasks/ folder so you can edit it safely.
  3. Running task library list again now shows the status badge up to date and the source local download.
Need to replace an older copy? Add --force to overwrite it, or install with a new filename.

​
Step 4 · Make it your own

Open the file in your preferred editor: 
autocleaneeg-pipeline task edit RestingEyesQuickCheck
When you are ready to test it, set it as the active task: 
autocleaneeg-pipeline task set RestingEyesQuickCheck
You can now run the pipeline as usual (autocleaneeg-pipeline process …).

​
Troubleshooting

  • “Missing” template in the list? Run task library list --refresh to clear the GitHub cache and try again.
  • Slow or blocked network? The CLI automatically falls back to the bundled snapshot. A banner will say “Working offline” with the time of the last successful check.
  • Legacy scripts that still call task builtins continue to work. Update them when convenient so everyone uses the same wording.

​
Next steps