Document container config DB, on-wake restarts, and CLI scope#289
Open
mintlify[bot] wants to merge 1 commit into
Open
Document container config DB, on-wake restarts, and CLI scope#289mintlify[bot] wants to merge 1 commit into
mintlify[bot] wants to merge 1 commit into
Conversation
Generated-By: mintlify-agent
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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.
Summary
Reflects three v2.0.46–v2.0.48 changes from
qwibitai/nanoclaw:groups/<folder>/container.jsonto the newcontainer_configstable in the central DB. The file is materialized at spawn time as a snapshot for the container runner. Existing filesystem configs are backfilled on startup.ncl groups restart --id <group-id> [--rebuild] [--message <text>]. The newon_wakeflag onmessages_inlets a fresh container's first poll claim the wake message, eliminating the race with a dying container in its SIGTERM grace period. Self-mod approval handlers (install_packages,add_mcp_server) use the same mechanism.cli_scopesetting on container config (disabled/group/global, defaultgroup) controls what an agent can access vianclfrom inside its container. Owner agent groups default toglobal. Escalation from group-scoped agents is blocked, and post-handler result filtering prevents cross-group data leaks.Pages updated
concepts/containers.mdx— DB-backed config, MCP/package CLI commands, explicit restart + on-wake sectionconcepts/groups.mdx— agent group definition,additional_mountssource, new "CLI scope" sectionapi/configuration.mdx— per-group runtime config moved to central DBapi/group-management.mdx—container_configsrow in schema table, new "Admin CLI (ncl groups)" sectionadvanced/container-runtime.mdx— spawn flow readscontainer_configs,killContaineronExitcallback, "Explicit restart and on-wake messages" sectionfeatures/customization.mdx— mount config moved toadditional_mountscolumnchangelog/index.mdx— added v2.0.45 and v2.0.48 release entrieschangelog/docs-updates.mdx— documentation update entry for this PRmint validateandmint broken-linksboth pass.