Skip to content

docs: add opencode-simple-notify to ecosystem#24259

Closed
Yusuzhan wants to merge 4 commits into
anomalyco:devfrom
Yusuzhan:add-opencode-simple-notify
Closed

docs: add opencode-simple-notify to ecosystem#24259
Yusuzhan wants to merge 4 commits into
anomalyco:devfrom
Yusuzhan:add-opencode-simple-notify

Conversation

@Yusuzhan

@Yusuzhan Yusuzhan commented Apr 25, 2026

Copy link
Copy Markdown

Issue for this PR

Closes #

Type of change

  • Bug fix
  • New feature
  • Refactor / code improvement
  • Documentation

What does this PR do?

Added opencode-simple-notify to ecosystem document, it's a light-weight desktop notification plugin.

How did you verify your code works?

Preview in browser.

Screenshots / recordings

Checklist

  • I have tested my changes locally
  • I have not included unrelated changes in this PR

If you do not follow this template your PR will be automatically rejected.

@github-actions github-actions Bot added needs:compliance This means the issue will auto-close after 2 hours. and removed needs:compliance This means the issue will auto-close after 2 hours. labels Apr 25, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Thanks for updating your PR! It now meets our contributing guidelines. 👍

Bojun-Vvibe added a commit to Bojun-Vvibe/oss-contributions that referenced this pull request Apr 25, 2026
- charmbracelet/crush#2693 (merge-after-nits): stdio MCP server
  config 'args' weren't run through resolver.ResolveValue, so
  '$VESTIGE_DB' reached the subprocess as a literal. Fix
  threads each arg through the same resolver that already
  handles 'command'. Fallback-to-literal on resolve failure is
  a footgun for credential-bearing args — should fail loud.

- anomalyco/opencode#24259 (merge-as-is): one-line ecosystem doc
  addition for opencode-simple-notify (Linux/Mac desktop
  notifications plugin). Standard supply-chain hygiene applies
  on the maintainer side.

- OpenHands/OpenHands#14099 (merge-after-nits): branch-search
  router previously hard-rejected page!=1 with 400. Fix threads
  page through every provider's search_branches with the
  provider's native idiom (page-param for GitLab/Bitbucket,
  start-offset for BB-DC, slice for Forgejo/AzDO). GitHub uses
  cursor walk through 'after: $cursor' which is O(page) — needs
  a clamp to bound adversarial deep-page requests.

- cline/cline#10403 (request-changes): adds Abliteration.ai as
  first-class provider. Handler/proto/UI plumbing follows the
  established pattern cleanly, but maxTokens: -1 sentinel
  in the model registry will produce wrong cost/budget
  calculations downstream (no other provider uses -1), and
  supportsTools() is hardcoded true rather than reading
  model.info. Both are 1-line fixes.
Bojun-Vvibe added a commit to Bojun-Vvibe/oss-contributions that referenced this pull request Apr 25, 2026
Lede counter through-drip-38 → through-drip-40. Eight new rows
spliced into per-repo tables for openai/codex, BerriAI/litellm,
continuedev/continue, ollama/ollama, charmbracelet/crush,
anomalyco/opencode, All-Hands-AI/OpenHands, cline/cline.

PRs: openai/codex#19526, BerriAI/litellm#26495,
continuedev/continue#12206, ollama/ollama#15808,
charmbracelet/crush#2693, anomalyco/opencode#24259,
OpenHands/OpenHands#14099, cline/cline#10403.
@github-actions

Copy link
Copy Markdown
Contributor

Automated PR Cleanup

Thank you for contributing to opencode.

Due to the high volume of PRs from users and AI agents, we periodically close older PRs using automated criteria so maintainers can focus review time on the most active and community-supported contributions.

This PR was closed because it matched the following cleanup criteria:

  • The PR was created more than 1 month ago
  • The PR had fewer than 2 positive reactions
  • Positive reactions are counted as thumbs-up, heart, celebration, or rocket reactions on the PR

PRs created within the last month are not affected by this cleanup.

If you believe this PR was closed incorrectly, or if you are still actively working on it, please leave a comment explaining why it should be reopened. A maintainer can review and reopen it if appropriate.

Thanks again for taking the time to contribute.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant