anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 18:25:32 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[PR #6726] docs: RFC - restructure plugin documentation #12067

New Issue
Closed
opened 2026-02-16 18:17:00 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 18:17:00 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/anomalyco/opencode/pull/6726

State: closed
Merged: No

Summary

Proposing a restructure of the plugin documentation. Looking for feedback on direction before investing more time.

Changes

  • Split plugin docs into a dedicated "Plugin Development" page
  • Reorganized content into three sections: Events, Hooks, and Providers
  • Added detailed examples for events (session, message, file, system)

Context

Started this while working on improving the anthropic auth plugin flow, noticed the plugin docs could use some reorganization. Before polishing the examples and verifying all the details, wanted to check if this direction is useful.

Questions for maintainers

  1. Is this level of detail/structure helpful, or is it overkill?
  2. Does the Events/Hooks/Providers organization make sense?
  3. Any preferences on how event examples should be formatted?

Happy to iterate based on feedback or close if this isn't a priority.

**Original Pull Request:** https://github.com/anomalyco/opencode/pull/6726 **State:** closed **Merged:** No --- ## Summary Proposing a restructure of the plugin documentation. Looking for feedback on direction before investing more time. ## Changes - Split plugin docs into a dedicated "Plugin Development" page - Reorganized content into three sections: Events, Hooks, and Providers - Added detailed examples for events (session, message, file, system) ## Context Started this while working on improving the anthropic auth plugin flow, noticed the plugin docs could use some reorganization. Before polishing the examples and verifying all the details, wanted to check if this direction is useful. ## Questions for maintainers 1. Is this level of detail/structure helpful, or is it overkill? 2. Does the Events/Hooks/Providers organization make sense? 3. Any preferences on how event examples should be formatted? Happy to iterate based on feedback or close if this isn't a priority.
yindo added the pull-request label 2026-02-16 18:17:00 -05:00
yindo closed this issue 2026-02-16 18:17:00 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#12067
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?