Activity, over time
Daily observations from the public event archive.
Attention
Daily stars & forks
Star accumulation
Cumulative stars
Pull requests
Daily opens & merges
Conversations
Daily issues & comments
Community
Daily accounts & reviews
Releases
Daily releases
Trending history
Daily top 10 · last 90 days · UTC
Mentions
Stars
Forks
Contributors
Latest stargazers
The last 10 distinct accounts we observed this year.
Most active participants
PR, issue, comment & review events in the past year.
Packages
Scan pending.
README badges
Embed a badge in your README or website.
Live mentions · last 30 days
Mentions
Open Connector contributor 破百了！ oomol-lab/open-connector t.co
Build a Muse tailored to your business. Your agent + your workflows + OpenConnector for app access. Add memory, scheduling and approvals around it. We’re building the connector layer. What would your own Muse do? oomol-lab/open-connector
@ataiiam For custom builds, I’d keep app credentials and action policies behind a connector runtime, separate from each agent harness. I’m involved with OpenConnector; it exposes app actions via MCP/HTTP: oomol-lab/open-connector
@mattlam_ I’d use API actions for supported SaaS tasks and keep supervised computer use for web-only forms. That avoids some autofill friction without giving up takeover. I’m involved with OpenConnector: oomol-lab/open-connector