Repository navigation
Conversation
Refs nextlevelbuilder/dewee#1145 Claude-Session: https://claude.ai/code/session_01U7fAD28S3opBrTMEUbYckx Co-authored-by: Claude <noreply@anthropic.com>
…#18) Claude-Session: https://claude.ai/code/session_01A4d1XjDSugCig7t9Gcjc8V Co-authored-by: Claude <noreply@anthropic.com>
The roles section now says the per-agent check covers WebSocket and HTTP chat, scheduling, and reading or editing an agent; that a channel's allowed senders grant chat on a predefined agent; that editing context files needs ownership or an admin/operator share; and which callers skip the check. Claude-Session: https://claude.ai/code/session_016nmNAA4j1sHbNi4qniJHQN Co-authored-by: Claude <noreply@anthropic.com>
Owners and admins reach every agent; other members need the default agent, ownership or a share, except for the workspace Super Agent, which every member can chat with. Refs nextlevelbuilder/dewee#1190 Claude-Session: https://claude.ai/code/session_01HVW5BkRvMah5CL5RjwLtdy Co-authored-by: Claude <noreply@anthropic.com>
…uns (#24) Agent shares are now use, edit, manage or admin; editing context files needs edit or above. Scheduled jobs are not re-checked when they fire, so the page says to disable a job when its share is revoked. Claude-Session: https://claude.ai/code/session_016nmNAA4j1sHbNi4qniJHQN Co-authored-by: Claude <noreply@anthropic.com>
Explain grant levels on skills, MCP servers, packages, providers, hooks and agents, open and restricted mode, run-time enforcement and its limits, the activity feed, and where grants are managed. Link it from the security, CLI and concept pages in both languages.
* docs(console): say only owners and admins change hooks Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01E5Ev2annTBN72tswwiLbtB * docs(console): correct hook activity permission and grant wording Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01E5Ev2annTBN72tswwiLbtB --------- Co-authored-by: Claude <noreply@anthropic.com>
Adds DEWEE_SELFHOST_APP_URL so `docker compose exec dewee dewee selfhost status` reaches the control panel, and a 45s stop grace period so the gateway finishes its SIGTERM cleanup.
This branch was successfully deployed
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
1 participant
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.
Promotes
devtomain(dewee.sh).Self-install
DEWEE_SELFHOST_APP_URLsodocker compose exec dewee dewee selfhost statusworks, plus a 45s stop grace period. It also clears the dewee release workflow's website drift check.Docs
The commits that exist only on
mainare merge commits from earlier promotions. There is no file difference betweendevandmainapart from the changes above.