Skip to content

Managing your QuickAgents

The Publisher section of your dashboard is where you look after the QuickAgents you publish. It has two parts:

  • QuickAgents lists every QuickAgent in your namespace, public and private, with the actions to manage them.
  • Earnings, where the registry runs Publisher Earnings, is where you join the program and see what your public QuickAgents earned.

An organization's QuickAgents are on the QuickAgents page of its console (the header's Organization button). It is the same list. Every member sees it, and only the organization's admins see the actions that change who can see a QuickAgent, or retire or delete it.

Agentry Desktop has the same list and actions in its Publisher section (The desktop app).

Find a QuickAgent

The list works like Browse. Search matches a QuickAgent's name and summary. Narrow the list by:

  • Visibility: public or private;
  • State: active, or retired;
  • Forks: only forks, or no forks.

A retired QuickAgent is always private, so public and retired together list nothing. Sort the list by newest, most installed over the last 30 days, last submission, or name. Each view has its own address, so you can bookmark one.

Each row shows the QuickAgent's name and summary, then its installs over the last 30 days and when a version was last submitted, then its recent activity. Its badges say what is unusual about it:

Badge Meaning
Private Only you (or the organization's members) and anyone you grant can open it.
Retired You retired it: it is private and takes no new versions.
Fork It is a fork of someone else's QuickAgent, named on the Fork of line under it. It stays private for good, so it has no Make public.
Quarantined or Blocked Agentry staff took it out of use after a finding.

What you can do with each one

Every row has Settings. A row that is not retired also has Edit, which opens it in the Builder, and Publish, which submits one of its repository's tags as a new version. The other actions are below. Each takes one click except Delete, and each tells you at the top of the page what happened, or what stopped it.

Make private, Make public

Make private takes a public QuickAgent out of Browse and search. Anyone who installed it keeps their copy, but cannot update it or install it again. Hosted runs by other people are refused.

Make public puts a private QuickAgent in Browse for everyone. Only a version that passed the gate is ever public, so the registry refuses this while the QuickAgent has a version admitted without a scan, or still admits them. Yank those versions on its Versions page, and turn off admitting unscanned submissions in its Settings, first.

On Standard, a namespace holds up to 10 private QuickAgents. Past that, Make private is refused until you make one public, retire one, or upgrade.

Retire, Restore

Retire puts a QuickAgent away without losing it. A retired QuickAgent:

  • turns private, so it leaves Browse and search;
  • is labelled Retired in your list;
  • takes no new versions;
  • does not count toward your private-QuickAgent limit.

Its versions stay as they were. Restore brings it back with the visibility it had when you retired it. A QuickAgent that was public goes back to Browse, under the same rule as Make public. One that was private takes a place under your private limit again.

Delete

Delete is the red button. It asks you to type the QuickAgent's name first, because it cannot be undone.

  • A QuickAgent with no version yet, such as one left behind when a first submission was refused, is removed with its repository. Its name is free to use again.
  • A QuickAgent with versions is deleted for good: every version is yanked, and its page, its downloads and its runs are gone for everyone, you included. People who installed it keep their copy on their computer, but nothing more reaches them.

When a QuickAgent with versions is deleted, its name is held: no QuickAgent in that namespace can take the name again. Someone who installed you/name must never get a different QuickAgent under the same name later.

The registry refuses to delete a QuickAgent while one of its versions is still being scanned or reviewed: wait for the verdict, then delete it. It also refuses while a trust & safety record stands against it: an advisory, an abuse report, a quarantine or a block. Those records outlive the QuickAgent, so the people who installed it keep the warning.

If you only want a QuickAgent out of sight, Retire it instead. You can change your mind later.

Who can do what

In your own namespace, you can do all of it. In an organization's namespace:

  • every member sees the list, with Edit, Publish and Settings;
  • only the organization's admins can Make private or public, Retire, Restore and Delete. The registry refuses these to anyone else, and the list shows them to admins only.

Edit, Publish and the QuickAgent's Settings each check your role on the QuickAgent when you open them.