Repository navigation
Inbound submissions 2026-11-10: added 1, updated 2, archived 0 - #370
Merged
Merged
Conversation
Co-authored-by: assaf.barnir <assaf.barnir@sentry.io>
This was referenced Nov 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ships the listings accepted from vetting the open submission backlog (87 issues and 29 community pull requests, all checked against the bar on 2026-11-10). As
/submitsays, an accepted listing goes live in a drop and its pull request is closed with a link rather than merged.The changelog entries are dated 2026-11-10, so they join the existing 2026-11-10 drop from the Nov 6 weekly run (#368). Its intro now says 88 additions instead of 87.
The title deliberately doesn't start with "Weekly drop": that prefix sets the next weekly run's research window, which should stay anchored on the 2026-11-06 drop.
TO ADD (1)
sage-agent-platformDrafted from Sage's own README and its Server HTTP API reference, not copied from the pull request, which described v2.0.0; the current README leads with the RSI harness. Access is
apiwithbearerauth: the server'sPOST /api/agentstreams AG-UI events, and external runs and A2A take a Bearer API key. The setup guide link is the Server guide, confirmed byverify-setup-fields.ts. The icon is Sage's own brand logo from its repo (iconUrl) rather than the owner's personal GitHub avatar.UPDATED (2)
screenpipepackages/screenpipe-mcp,npx -y screenpipe-mcp@latest), documented at docs.screenpipe.com/mcp-serverclifyGET /searchanswers 200 with JSONOnly the access methods change. The rest of what those pull requests propose (descriptions, tags, skills, auth, verified) isn't one of the factual changes an update covers, so those listings otherwise stay as they are.
Validation
npx tsx scripts/validate-content.ts: content valid, 996 agents (380 official, 235 vendors), 22 categories, 975 icons, 27 drops, 7 stacks, 38 tasks, 13 comparisons, 0 violations. Published 985 → 986.Compared with
origin/main (1c9040b): 1 listing added, 0 archived, 2 edited.New listings
sage-agent-platformNeeds a look
sage-agent-platform.Elsewhere on the site
renoolab.here-now,claude-code,google-ax,gbrain,sage-agent-platformandscalable-capital-mcp(werehere-now,claude-code,google-ax,gbrain,scalable-capital-mcpandmeltwater-mcp).The one item under "Needs a look" is expected: Sage's API is a self-hosted server that each user runs, so there's no public base URL, and the page links the setup guide instead.