Skip to main content

​
Overview

​
Tool Name

config_manager

​
Purpose

The config_manager tool group centralizes environment configuration for Genesis Data Agents. It controls user-facing settings like knowledge sources, harvester parameters, refresh intervals, and auto-harvest policies so teams can govern behavior consistently across workspaces and agents.

​
Key Features & Functions

Centralized settings

Read and update environment settings in a single place

Scoped configuration

Apply settings at GLOBAL, WORKSPACE, or BOT scope.

Safe updates

Use dry-run and diff previews to validate changes before applying.

Governance alignment

Enforce enterprise defaults and guardrails.

​
Input Parameters for Each Function

​
_config_manager

This tool exposes a single entry point with sub-actions. Exact parameters may vary by deployment; the structure below reflects common usage patterns.
Parameters
NameDefinitionFormat
actionOperation to perform. Common values: LIST, GET, UPDATE.String
scopeTarget scope for configuration. e.g., GLOBAL, WORKSPACE, BOT.String
keyConfiguration key to read/update (e.g., knowledge.enabled, harvester.refresh_interval_min).String
valueNew value to set (for UPDATE). JSON-serializable.Any / JSON
bot_idTarget agent when scope=BOT.String
workspace_idTarget workspace when scope=WORKSPACE.String
dry_runIf true, show the planned change without applying.Boolean
commentChange note for audit history.String
Use dry_run: true with action: "UPDATE" to preview diffs before committing changes.

​
Use Cases

  1. Enable/disable auto-harvest globally with standard refresh intervals
  2. Toggle knowledge search for a particular data agent
  3. Set conservative harvester schedules for large warehouses
  4. Apply temporary overrides during maintenance windows

​
Workflow/How It Works

  1. Read current values at the intended scope (LIST/GET).
  2. Propose updates and run with dry_run=true for a preview.
  3. Apply changes (UPDATE) with an audit comment.
  4. Validate downstream behavior (e.g., harvest summaries, tool outputs).

​
Integration Relevance

  • Harvester Tools: Align inclusions/exclusions and refresh schedules.
  • Project Manager Tools: Centralized governance for data agent behaviors used across missions.
  • System Manager Tools: System-wide controls for stability and maintenance.

​
Configuration Details

  • Prefer WORKSPACE scope for team-level adjustments; use GLOBAL sparingly.
  • Use dry_run to view diffs before applying changes.
  • Document rationale in comment for compliance and rollbacks.
Scope precedence typically follows BOT > WORKSPACE > GLOBALA data agent-level setting overrides workspace/global defaults.

​
Limitations or Notes

  • Some settings may be immutable in a managed deployment.
  • Invalid keys/scopes or insufficient permissions will be rejected.

​
Output

  • LIST / GET: Current settings at the requested scope
  • UPDATE: Change confirmation with before/after diff (when available)
  • Errors: Detailed messages for invalid keys, scopes, or permission violations
⌘I