docs: correct what eve extensions can contribute (channels/schedules/subagents ARE allowed) - #26
Merged
Merged
Conversation
Extensions can contribute channels, schedules, and subagents (eve >=0.41, per eve's docs/extensions.md) — this was previously stated as excluded in several places. The actual exclusions at the extension root are: sandbox, agent config, and nested extensions. Fixes CLAUDE.md (two spots) and the same repeated claim in packages/eve-extension/AGENTS.md, packages/eve-extension/README.md, and packages/eve/README.md.
CahidArda
approved these changes
Aug 25, 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.
CLAUDE.md stated in two places that eve extensions cannot contribute channels, schedules, or subagents. That's wrong as of eve >=0.41 (per eve's docs/extensions.md): extensions can contribute all of tools, channels, connections, skills, schedules, subagents, instruction fragments, and hooks. The only things actually excluded at the extension root are sandbox, agent config, and nested extensions (a contributed subagent may still own its own config/sandbox).
This fixes both spots in CLAUDE.md and the same incorrect claim repeated in packages/eve-extension/AGENTS.md, packages/eve-extension/README.md, and packages/eve/README.md — the latter two previously used the false "extensions can't carry channel/sandbox config" framing to justify the eve vs eve-extension package split, now reworded around the real reasons (sandbox backend can't live at an extension root; rate-limit auth and defineCachedTool are just pieces you compose into your own tree).
Built by upstash-tag · mission
fe0f5b94-ea6d-4611-bdac-60d6c2aebcf6·docs/fix-eve-extension-contributions→main· $1.58