droost_config_status

Droost: Config Status

droost_config_status Read-only

Module: Droost core

Sync status of configuration: what differs between active config and the sync directory, and whether an import/export is pending. Check it before config-heavy work on a site with a config workflow.

Example call

{
    "tool": "droost_config_status",
    "arguments": {}
}

Example response — captured live on this site

{
    "success": true,
    "message": "624 config object(s) differ between active and sync.",
    "data": {
        "note": "Relative to a config import (sync → active): only_in_sync would be created, only_in_active would be deleted, different would be updated.",
        "only_in_sync": [],
        "only_in_active": [
            "ai.external_moderation",
            "ai.settings",
            "announcements_feed.settings",
            "automated_cron.settings",
            "automatic_updates.settings",
            "autosave_form.messages",
            "autosave_form.settings",
            "block.block.claro_breadcrumbs",
            "block.block.claro_content",
            "block.block.claro_local_actions",
            "block.block.claro_messages",
            "block.block.claro_page_title",
            "block.block.claro_primary_local_tasks",
            "block.block.claro_secondary_local_tasks",
            "block.block.droost_tailwind_main",
            "block.block.droost_tailwind_menu",
            "block.block.droost_tailwind_messages",
            "block.block.droost_tailwind_tabs",
            "block.block.gin_breadcrumbs",
            "block.block.gin_content",
            "block.block.gin_local_actions",
            "block.block.gin_messages",
            "block.block.gin_page_title",
            "block.block.gin_primary_local_tasks",
            "block.block.gin_sec
… (truncated — run it yourself for the rest)

Reports configuration drift between active config and the sync directory. No argument: lists what differs. With "name": that single config object's status (and both versions). Read-only.

Input schema (JSON Schema)

{
    "type": "object",
    "properties": {
        "name": {
            "type": "string",
            "description": "A single config object name, e.g. \"system.site\"."
        },
        "limit": {
            "type": "integer",
            "description": "Max names per category when listing (default 200)."
        }
    }
}