Suggestions
How readers propose improvements to packs and how owners resolve them.
A suggestion is a text-first improvement proposal for a workflow or context pack. Anyone who can read a pack can suggest a change to it; the pack's owner reviews and resolves it. Suggestions never edit the pack directly — the proposed change lives in the suggestion text, and the owner applies it through a normal pack update.
Suggestions are separate from pack content. They let collaborators and community members improve a pack without write access, while the owner stays in control of what actually changes.
Lifecycle
Every suggestion has a status.
| Status | Meaning | Set by |
|---|---|---|
open |
Submitted, awaiting the owner's decision (initial state). | Author (create) |
applied |
Owner accepted it; the change has been made. | Owner (resolve) |
declined |
Owner decided not to act on it. | Owner (resolve) |
archived |
Set aside without a decision, to keep the inbox clean. | Owner (resolve) |
A suggestion starts open. The owner moves it to applied, declined, or archived — and can move it back to open. Resolving a suggestion only changes its status; the actual pack edit is a separate pack update.
Snapshot
When a suggestion is created, the pack's content at that moment is captured as an immutable snapshot. The suggestion stays anchored to what the author actually saw, even if the pack changes afterward. Read APIs omit the snapshot by default; request it explicitly when you need to compare against the pack's current state.
List vs get
Listing suggestions returns each one's content as a truncated preview, the same selective-fetch pattern packs use (outline first, full content on demand). Fetch a single suggestion to read its full content. On the web, suggestion lists link to a detail page that loads the full content.
Permissions
| Action | Who |
|---|---|
| Create | Anyone who can read the pack (private or public). |
| Update (title/content) | The author only. |
| Resolve (status) | The pack owner only. |
| Get / list | Anyone whose access grants read on the suggestion. |
Creating a suggestion costs 5 credits and listing costs 2 credits; reading, updating, and resolving cost 1 credit each. Each account can also create at most 20 suggestions per day.
When to use
- Propose a fix or addition to a public pack you don't own.
- Give a teammate feedback on a shared workflow without editing it yourself.
- Collect improvement ideas for a pack you maintain in one inbox, then apply the good ones.
Use a suggestion when you want to recommend a change; use a pack update when you own the pack and are making the change.