Submit your plugin changedplugins/submit
Nearest release: v2.1.283, published under an hour before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 25 Sep 2026 18:59 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 25 Sep 2026 19:07 UTC.
Upstream edited
Recorded here
Lines+27added
Lines−2removed
From line
16
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits5to this page, all time
### Connect your GitHub account ## Submit from a private repository
The whole hunk
from line 16, old and new numbered
/
from line 16
1616
1717You need the following to submit from the developer portal on claude.ai:
1818
19* **A GitHub repository that holds the plugin.** The directory reads plugins from repositories on github.com, and the repository must be public before the listing goes live. If the portal shows **Couldn’t find that repository, branch or tag**, check that the repository and the branch or tag exist
19* **A GitHub repository that holds the plugin, and your GitHub account connected on claude.ai.** The directory reads plugins from repositories on github.com. The portal checks that your connected GitHub account can push to the repository, so [connect it first](#connect-your-github-account). The repository can stay private while you validate and submit, and must be public before the listing goes live. See [Submit from a private repository](#submit-from-a-private-repository)
2020* **A plan and role that can submit.** See [who can submit to the directory](/docs/directory/publish#confirm-you-can-submit-to-the-directory)
2121
2222Every plugin in the directory must comply with the [Anthropic Software Directory Terms](https://support.claude.com/en/articles/13145338-anthropic-software-directory-terms) and the [Anthropic Software Directory Policy](https://support.claude.com/en/articles/13145358-anthropic-software-directory-policy).
from line 91
9191
9292If another organization has already submitted the same repository and folder, the portal refuses **Submit for review** with **Already submitted by another organization**. If your organization owns the repository, email `[email protected]`.
9393
94### Connect your GitHub account
95
96The portal checks your GitHub access before it lets you create a submission, submit it, publish the plugin, [relist](#withdraw-or-delist-a-plugin) it, or turn on [auto-publish](#publish-a-passing-version). It uses the GitHub account you connected to claude.ai in the organization you're submitting from, and asks GitHub whether that account can push to the repository. A GitHub connection you made in another Claude organization doesn't carry over. If the portal can't confirm push access, the action stops and you see one of these messages:
97
98* **GitHub isn’t connected for this Claude organization**: select **Connect GitHub** in the message to connect your account, then try again
99* **The connected GitHub account can’t push to this repository**: ask an admin of the repository to give your GitHub account write access, then try again
100
101Validating a public repository doesn't run this check, so **Validate** can pass before you've connected GitHub; the check happens when you create or submit.
102
103## Submit from a private repository
104
105You can validate and submit a plugin while its repository is private, so review can start before you publish your code. The directory scans it while it's private. Publishing and relisting still need the repository to be public.
106
107The portal reads a private repository only when these conditions hold:
108
109* **Your connected GitHub account can push to the repository.** This is the same check as [Connect your GitHub account](#connect-your-github-account)
110* **You agree to the source upload.** The portal shows **This repository is private.** and asks you to confirm that the repository's source is uploaded to Anthropic for automated scanning and is visible to Anthropic reviewers
111* **The Claude GitHub App is installed on the repository** and connected to your Claude organization. If it isn't, the portal shows **The Claude GitHub App can’t reach this repository** with an **Install the Claude GitHub App** link. Install it, then validate again
112
113Before you've agreed to the source upload, **Validate** shows only **Couldn’t find that repository, branch, tag, or commit** while your GitHub account isn't connected, can't see the repository, or can't push to it. The portal doesn't confirm that a private repository exists to someone who can't see it.
114
115When you're ready to publish, make the repository public on GitHub, then select **Check for new commits** on the plugin's page. Until then, the page shows **Publishing needs a public repository**.
116
94117## After you submit a plugin
95118
96119When you select **Submit for review**, the directory scans the newest commit on the tracked branch or tag. Each scan validates the plugin against the directory's rules again and runs a security scan. [Prepare for the security scan](/docs/plugins/pre-submission-checklist#prepare-for-the-security-scan) describes what the security scan looks for.
from line 153
130153
131154## Update a published plugin
132155
133To release a new version, push to the tracked branch. You don't submit the form again. If the submission follows a tag, release a new version by changing the tag, as described in [Change the tracked branch or tag](#change-the-tracked-branch-or-tag).
156After the first submission, you keep the listing current by releasing the way you already do. Merge to the tracked branch, and the directory picks up the commit, checks it, and publishes it. You don't return to the portal unless a version is held or you want to change a setting. If the submission follows a tag, release a new version by changing the tag, as described in [Change the tracked branch or tag](#change-the-tracked-branch-or-tag).
134157
135158The directory checks the tracked branch for new commits on a schedule. If you set up the GitHub push webhook, the directory also checks when you push, without waiting for the schedule.
136159
137160* **To set up the webhook after you submit:** select **Set up** under **Updates** on the plugin's **Settings** tab
138161* **To check right away:** open the plugin from **Submissions** in the [developer portal](https://claude.ai/directory/manage) and select **Check for new commits**
162
163The repository doesn't have to be dedicated to the plugin. If the plugin is one folder in a larger repository, give that folder as the plugin path when you submit; the directory reads and scans only that folder.
139164
140165A new version that passes is published according to the plugin's [publish setting](#publish-a-passing-version). The listing keeps serving the last published version until a new version is published, including when a new version doesn't pass or is held for a reviewer. If the security scan flags or fails a new version, later versions also wait until an Anthropic reviewer clears the plugin.
141166
No line in this hunk matches that.