Skip to content

Inbound submissions 2026-11-10: added 1, updated 2, archived 0 - #370

Merged
assafbar2 merged 1 commit into
mainfrom
cursor/inbound-submissions-2026-11-10-8d76
Nov 10, 2026
Merged

assafbar2 merged 1 commit into
mainfrom
cursor/inbound-submissions-2026-11-10-8d76

Conversation

@assafbar2

Copy link
Copy Markdown
Owner

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 /submit says, 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)

Listing Slug Signal (verified 2026-11-10) Source
Sage, an open-source agent harness that runs, evaluates and improves agents from task feedback sage-agent-platform 1,214★ on its own repo (MIT, created 2025-05-25, pushed 2026-11-10), 115 forks, 27 contributors; releases v2.0.0 to v2.1.1 in October 2026 From #192 by @ZHangZHengEric

Drafted 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 api with bearer auth: the server's POST /api/agent streams AG-UI events, and external runs and A2A take a Bearer API key. The setup guide link is the Server guide, confirmed by verify-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)

Listing Field From → To Evidence Source
screenpipe accessMethods cli, api → cli, api, mcp Screenpipe's repo ships an MCP server (packages/screenpipe-mcp, npx -y screenpipe-mcp@latest), documented at docs.screenpipe.com/mcp-server From #111 by @louis030195
clify accessMethods mcp → api, mcp Clify's homepage documents a keyless public JSON API with a curl example; GET /search answers 200 with JSON From #232 by @ToukoUrsin

Only 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

Listing Task pages Try this first Alternatives Icon Use it now
sage-agent-platform fits 2, outside their top 12 3 8, page yes setup guide

Needs a look

  • API with no base URL, so the page links its docs (1): sage-agent-platform.

Elsewhere on the site

  • Alternatives pages: 800 → 802. 1 new listing gets one. 1 existing listing gains one: renoolab.
  • 62 existing listings' alternatives pages change, and 38 existing listings show different Related Agents (4 now include a new listing).
  • Homepage slots, in order: here-now, claude-code, google-ax, gbrain, sage-agent-platform and scalable-capital-mcp (were here-now, claude-code, google-ax, gbrain, scalable-capital-mcp and meltwater-mcp).
  • The build makes 3 more pages, each with its share card.

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.

Co-authored-by: assaf.barnir <assaf.barnir@sentry.io>
@assafbar2
assafbar2 merged commit 19434a9 into main Nov 10, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants