naisys 1.6.1 → 3.0.0-beta.4

package/README.md

@@ -1,25 +1,21 @@
-## NAISYS (Node.js Autonomous Intelligence System)
+## NAISYS (Networked Agents Interface System)
+
+[← Back to main README](../../README.md)
 
 NAISYS allows any LLM you want to operate a standard Linux shell given your instructions. You can control how much
 to spend, the maximum number of tokens to use per session, how long to wait between commands, etc.. Between each command
-NAISYS will wait a few seconds to accept any input you want to put in yourself in case you want to colllaborate with the
-LLM, give it hints, and/or diagnose the session. Once the LLM reaches the token max you specified for the sesssion it
+NAISYS will wait a few seconds to accept any input you want to put in yourself in case you want to collaborate with the
+LLM, give it hints, and/or diagnose the session. Once the LLM reaches the token max you specified for the session it
 will wrap things up, and start a fresh shell for the LLM to continue on its work.
 
 NAISYS tries to be a minimal wrapper, just helping the LLM operate in the shell 'better'. Making commands 'context friendly'. For instace if a command is long running, NAISYS will interrupt it, show the LLM the current output, and ask the LLM what it wants to
-do next - wait, kill, or send input. The custom command prompt helps the LLM keep track of its token usage during the session. The 'comment' command helps the LLM think out loud without putting invalid commands into the shell.
+do next - wait, kill, or send input. The custom command prompt helps the LLM keep track of its token usage during the session. The 'ns-comment' command helps the LLM think out loud without putting invalid commands into the shell.
 
 Some use cases are building websites, diagnosing a system for security concerns, mapping out the topology of the local
 network, learning and performing arbitrary tasks, or just plain exploring the limits of autonomy. NAISYS has a built-in
-system for inter-agent communiation. You can manually startup mulitple instances of NAISYS with different roles, or
+system for inter-agent communication. You can manually startup multiple instances of NAISYS with different roles, or
 you can allow agents to start their own sub-agents on demand with instructions defined by the LLM itself!
 
-[NPM](https://www.npmjs.com/package/naisys) | [Website](https://naisys.org) | [Discord](https://discord.gg/JBUPWSbaEt) | [Demo Video](https://www.youtube.com/watch?v=Ttya3ixjumo)
-
-```bash
-npm install -g naisys
-```
-
 #### Node.js is used to create a simple proxy shell environment for the LLM that
 
 - Helps the LLM keep track of its current context size
@@ -28,120 +24,29 @@ npm install -g naisys
 - Prevent the context from being polluted by catching common errors like output that includes the command prompt itself
 - Allows debugging by way of a 'debug' prompt after each run of the LLM
 - A custom 'mail' system for context friendly inter-agent communication
-- A browser called 'llmynx' that uses a separate LLM to reduce web page size as well as make links unique across the context
+- A browser called 'ns-lynx' that paginates web pages and makes links unique across the context
 - Cost tracking and cost limits that must be set in the config
 - Support for multiple LLM backends, configurable per agent - OpenAI, Google, Anthropic, and self-hosted LLMs
 
 ## Getting Started
 
-- See notes for Windows users at the bottom of this file
-- Install Node.js, NAISYS has been tested with version 20
-- Install lynx using `apt install lynx`
-- Run `npm install -g naisys`
-- Create a `.env` file:
+- Create a `.env` file based off the `.env.example` file
 
-```bash
-# Agent home files and NAISYS specific databases will be stored here
-NAISYS_FOLDER="/var/naisys"
-
-# The folder where the website and logs are served from (if not defined then logs put in the naisys folder)
-WEBSITE_FOLDER="/var/www"
-
-# Leave api keys/url blank if not using the service
-OPENAI_API_KEY="xxx"
-GOOGLE_API_KEY="yyy"
-ANTHROPIC_API_KEY="zzz"
-
-LOCAL_LLM_URL="http://localhost:1234/v1"
-LOCAL_LLM_NAME="minstral instruct v0.2"
-
-# Custom global vars for use in agent configurations here
-WEBSITE_URL="http://localhost:8080/"
-```
-
-- Create an agent configuration file `smith.yaml`:
+- Create an agent configuration file — see [`agents/template.yaml`](../../agents/template.yaml) for all available options and supported models. A minimal example:
 
 ```yaml
-# Used to identify the agent on the prompt, logs, home dir, mail, etc..
 username: smith
-
-# How other agents will understand the role of this agent
 title: Software Engineer
-
-# The model to use for console interactions
-# (gpt4turbo, gpt4turbo, gemini-pro, claude3sonnet, claude3opus, local)
-shellModel: gpt4turbo
-
-# Only used between sessions to provide guidance for the next session (use a more powerful model for this)
-# defaults to the shellModel if omitted
-dreamModel: claude3opus
-
-# The model to use for llmynx, pre-processing websites to fit into a smaller context (use a cheaper model)
-# defaults to the shellModel if omitted
-webModel: claude3haiku
-
-# The model used by the 'genimg' command. If not defined then the genimg command is not available to the LLM
-# Valid values: dalle2-256, dalle2-512, dalle2-1024, dalle3-1024, dalle3-1024-HD
-imageModel: dalle3-1024
-
-# A system like prompt explaining the agent's role and responsibilities
-# You can use config variables in this string
+shellModel: claude4sonnet
 agentPrompt: |
-  You are ${agent.username} a ${agent.title} with the job of creating a Neon Genesis Evangelion fan website.
-  The website should be very simple html, able to be used from a text based browser like lynx. Pages should be relatively short.
-  The location of the website files should be in ${env.WEBSITE_FOLDER} 
-  The website can be tested with 'llmynx open ${env.WEBSITE_URL}' to see how it looks in a text based browser.
-  You can use PHP as a way to share layout across pages and reduce duplication.
-  Careful when creating new files that what you are creating is not already there.
-
-# The number of tokens you want to limit a session to, independent of the LLM token max itself
-# A lower max relies more on the LLM ending the session with good enough notes to not get lost when the session restarts
-# A higher max allows the LLM to do more without losing track, but is more expensive
-tokenMax: 5000
-
-# The number of seconds to pause after each console interaction for debugging and rate limiting
-# No value or zero means wait indefinitely (debug driven)
+  You are ${agent.username} a ${agent.title} with the job of building a website.
+tokenMax: 50000
 debugPauseSeconds: 5
-
-# If true, regardless of the debugPauseSeconds, the agent will wake up on messages
-# Useful for agents with long debugPauseSeconds, so that they can wake up and reply quickly
-wakeOnMessage: false
-
-# The maximum amount to spend on LLM interactions
-# Once reached the agent will stop and this value will need to be increased to continue
-spendLimitDollars: 2.00
-
-# Command Protection: Useful for agents you want to restrict from modifying the system
-#   None: Commands from the LLM run automatically, this is the default setting as well if the value is not set
-#   Manual: Every command the LLM wants to run has to be approved [y/n]. Not very autonomous.
-#   Auto: All commands are run through the separate LLM instace that will check to see if the command is safe
-commandProtection: "none"
-
-# The max number of subagents allowed to be started and managed. Leave out to disable.
-# Costs by the subagent are applied to the host agent's spend limit
-# Careful: Sub-agents can be chatty, slowing down progress.
-subagentMax: 0
-
-# Run these commands on session start, in the example below the agent will see how to use mail and a list of other agents
-initialCommands:
-  - llmail users
-  - llmail help
-  - cat ${env.NAISYS_FOLDER}/home/${agent.username}/PLAN.md
-# Additional custom variables can be defined here and/or in the agent config to be loaded into the agent prompt
+spendLimitDollars: 5.00
 ```
 
-- Run `naisys <path to yaml or directory>`
-  - If a yaml file is passed, naisys will start a single agent
-  - If a directory is passed, naisys will start a tmux session with the screen split for each agent
-
-#### Creating a persistent agent run website (on Digital Ocean for example)
-
-- Create new VM using the [LAMP stack droplet template](https://marketplace.digitalocean.com/apps/lamp)
-- Login to the droplet using the web console
-- Run `apt install npm`
-- Install `nvm` using the `curl` url from these [instructions](https://github.com/nvm-sh/nvm?tab=readme-ov-file#installing-and-updating)
-  - Run `nvm install/use 20` to set node version to 20
-- Follow the general install instructions above
+- Run `naisys <path to agent yaml or directory> [options]`
+  - Pass a directory to run all agent yamls in that folder
 
 ## Using NAISYS
 
@@ -154,7 +59,6 @@ initialCommands:
   - Pause on the debug prompt for that many seconds
   - Pause indefinitely
   - Pause until a new message is received from another agent
-- Agents logs are written as html to `{WEBSITE_FOLDER or NAISYS_FOLDER}/logs`
 
 #### Console Colors Legend
 
@@ -167,62 +71,38 @@ initialCommands:
 
 - NAISYS tries to be light, acting as a helpful proxy between the LLM and a real shell, most commands should pass right though to the shell
 - Debug Commands
-  - `cost` - Prints the current total LLM cost
-  - `context` - Prints the current context
-  - `exit` - Exits NAISYS. If the LLM tries to use `exit`, it is directed to use `endsession` instead
-  - `talk` - Communicate with the local agent to give hints or ask questions (the agent itself does not know about talk and is directed to use `comment` or `llmail` for communication)
+  - `ns-cost` - Prints the current total LLM cost
+  - `ns-context` - Prints the current context
+  - `ns-talk` - Communicate with the local agent to give hints or ask questions (the agent itself does not know about talk and is directed to use `ns-comment` or `ns-mail` for communication)
+  - `exit` - Exits NAISYS in debug mode. If the LLM tries to use `exit`, it is directed to use `ns-session compact/complete` instead
 - Special Commands usable by the LLM as well as by the debug prompt
-  - `comment "<note>"` - The LLM is directed to use this for 'thinking out loud' which avoids 'invalid command' errors
-  - `endsession "<note>"` - Clear the context and start a new session.
-    - The LLM is directed to track it's context size and to end the session with a note before running over the context limit
-  - `pause <seconds>` - Can be used by the debug agent or the LLM to pause execution for a set number of seconds
+  - `ns-comment "<note>"` - The LLM is directed to use this for 'thinking out loud' which avoids 'invalid command' errors
+  - `ns-session` - Session management commands:
+    - `ns-session wait <seconds>` - Pause execution for a set number of seconds
+    - `ns-session trim <indexes>` - Remove prompts by index to save tokens (e.g., "1-5, 8")
+    - `ns-session compact` - Compact the context and restart the session with that
+    - `ns-session complete "<result>"` - Mark task as complete and exit (for sub-agents: notifies lead agent)
 - NAISYS apps
-  - `llmail` - A context friendly 'mail system' used for agent to agent communication
-  - `llmynx` - A context friendly wrapping on the lynx browser that can use a separate LLM to reduce the size of a large webpage into something that can fit into the LLM's context
-  - `genimg "<description>" <filepath>` - Generates an image with the given description, save at the specified fully qualified path
-  - `subagent` - A way for LLMs to start/stop their own sub-agents. Communicating with each other with `llmail`. Set the `subagentMax` in the agent config to enable.
-
-## Running NAISYS from Source
-
-#### Getting started locally
-
-- Install Node.js, NAISYS has been tested with version 20
-- Clone the NAISYS repository from Github
-- Run `npm install` to install dependencies
-- Create a `.env` from the example above
-- Run `npm run compile`
-- Configure your agent using the examples in the `./agents` folder
-- Run `node dist/naisys.js <path to agent yaml file>`
-
-#### Notes for Windows users
-
-- To use NAISYS on Windows you need to run it locally from source (or from within WSL)
-- Use the above instructions to install locally, and then continue with the instructions below
-- Install WSL (Windows Subsystem for Linux)
-- Install a Linux distribution, Ubuntu can easily be installed from the Microsoft Store
-- Make sure to the checked out code perserves the original line endings
-  - Files in the /bin folder should have LF endings only, not CRLF
-- The `NAISYS_FOLDER` and `WEBSITE_FOLDER` should be set to the WSL path
-  - So `C:\var\naisys` should be `/mnt/c/var/naisys` in the `.env` file
-
-#### Notes for MacOS users
-
-- The browser llmynx requires `timeout` and `lynx`. Run these commands to install them:
-  - `brew install coreutils`
-  - `brew install lynx`
-
-#### Using NAISYS for a website
-
-- Many frameworks come with their own dev server
-  - PHP for example can start a server with `php -S localhost:8000 -d display_errors=On -d error_reporting=E_ALL`
-- Start the server and put the URL in the `.env` file
+  - `ns-mail` - A context friendly 'mail system' used for agent to agent communication
+  - `ns-lynx` - A context friendly wrapping on the lynx browser that can use a separate LLM to reduce the size of a large webpage into something that can fit into the LLM's context
+  - `ns-genimg "<description>" <filepath>` - Generates an image with the given description, save at the specified fully qualified path
+  - `ns-agent` - A way for LLMs to start/stop their own sub-agents. Communicating with each other with `ns-mail`.
 
 ## Changelog
 
+- 3.0: ERP and Desktop Control
+- 2.2: NAISYS cross machine support enabled by a new hub process
+- 2.1: Monorepo architecture, allowing Supervisor to run in-process
+- 2.0: Agent multiplexing in the same process
+- 1.7: Prompt caching, ns-lynx pagination, complete task command
 - 1.6: Support for long running shell commands and full screen terminal output
 - 1.5: Allow agents to start their own parallel `subagents`
-- 1.4: `genimg` command for generating images
-- 1.3: Post-session 'dreaming' as well as a mail 'blackout' period
+- 1.4: `ns-genimg` command for generating images
+- 1.3: Post-session session compaction as well as a mail 'blackout' period
 - 1.2: Created stand-in shell commands for custom Naisys commands
 - 1.1: Added command protection settings to prevent unwanted writes
 - 1.0: Initial release
+
+## License
+
+MIT

package/bin/naisys

@@ -10,62 +10,17 @@ SCRIPT_DIR=$(dirname "$SCRIPT")/..
 if [ $# -eq 0 ]; then
   # get version from package.json
   VERSION=$(node -e "console.log(require('${SCRIPT_DIR}/package.json').version)")
-  echo "NAISYS: Node.js Autonomous Intelligence System"
+  echo "NAISYS: Networked Agents Interface System"
   echo "  Version: $VERSION"
-  echo "  Usage: naisys <path to agent config yaml, or directory>"
-  echo "  Note: If a folder is passed then all agents will be started in a tmux session"
+  echo "  Usage: naisys <path to agent yaml or directory> [options]"
+  echo "  Options:"
+  echo "    --integrated-hub    Start Hub in the same process"
+  echo "    --supervisor        Start Supervisor web UI (requires --integrated-hub)"
+  echo "    --erp               Start ERP web app (requires --supervisor)"
+  echo "    --hub <url>         Connect to a remote Hub server"
+  echo ""
+  echo "  Pass a directory to run all agent yamls in that folder."
   exit 1
 fi
 
-# if path is a yaml file then start a single agent
-if [ -f "$1" ]; then
-  if [[ "$1" == *".yaml" ]]; then
-    echo "Starting single agent..."
-    node $SCRIPT_DIR/dist/naisys.js "$1"
-    exit 0
-  else
-    echo "Invalid file type. Please provide a .yaml file."
-    exit 1
-  fi
-fi
-
-# TODO: In the future should implement a max agents per window in the session
-# Will require an outer loop to create new windows
-# How many agents per window
-# AGENTS_PER_WINDOW=4
-
-# Directory containing agent files
-AGENT_DIR="$1"
-TEAM_NAME=$(basename "$AGENT_DIR")
-
-# Start a new tmux session detached
-tmux new-session -d -s $TEAM_NAME
-
-# Get a list of agent paths
-AGENT_FILES=($(find $AGENT_DIR -type f)) # This will list all files in the directory
-
-# Split the window into panes and start agents
-for ((i = 0; i < ${#AGENT_FILES[@]}; i++)); do
-  echo "Starting agent $((i + 1)) of ${#AGENT_FILES[@]}..."
-  sleep $((i == 0 ? 3 : 1)) # Sleep longer for the first agent
-  
-  # For the first agent, no split is needed
-  if [ $i -eq 0 ]; then
-    tmux send-keys -t $TEAM_NAME:0.0 "node $SCRIPT_DIR/dist/naisys.js '${AGENT_FILES[i]}'" C-m # Quote the path
-  else
-    # Determine pane split direction based on odd/even pane index
-    if [ $((i % 2)) -eq 0 ]; then
-      tmux split-window -v -t $TEAM_NAME:0
-    else
-      tmux split-window -h -t $TEAM_NAME:0
-    fi
-    tmux send-keys "node $SCRIPT_DIR/dist/naisys.js '${AGENT_FILES[i]}'" C-m # Quote the path
-    tmux last-pane # Move focus back to the last pane to ensure correct targeting in the next iteration
-  fi
-done
-
-# Optionally, you can balance the panes if you want
-tmux select-layout -t $TEAM_NAME tiled
-
-# Attach to the session
-tmux attach-session -t $TEAM_NAME
+node $SCRIPT_DIR/dist/naisys.js "$@"

package/bin/ns-comment.ps1

@@ -0,0 +1,2 @@
+# ./src/command/commandHandler.ts has the same message
+Write-Host "Comment noted. Try running commands now to achieve your goal. ."

package/bin/ns-genimg

@@ -0,0 +1,3 @@
+#!/bin/bash
+
+echo "'ns-genimg' cannot be used with other commands on the same prompt."

package/bin/ns-genimg.ps1

@@ -0,0 +1 @@
+Write-Host "'ns-genimg' cannot be used with other commands on the same prompt."

package/bin/ns-lynx

@@ -0,0 +1,3 @@
+#!/bin/bash
+
+echo "'ns-lynx' cannot be used with other commands on the same prompt."

package/bin/ns-lynx.ps1

@@ -0,0 +1 @@
+Write-Host "'ns-lynx' cannot be used with other commands on the same prompt."

package/bin/ns-mail

@@ -0,0 +1,3 @@
+#!/bin/bash
+
+echo "'ns-mail' cannot be used with other commands on the same prompt."

package/bin/ns-mail.ps1

@@ -0,0 +1 @@
+Write-Host "'ns-mail' cannot be used with other commands on the same prompt."

package/bin/ns-session

@@ -0,0 +1,3 @@
+#!/bin/bash
+
+echo "'ns-session' cannot be used with other commands on the same prompt."

package/bin/ns-session.ps1

@@ -0,0 +1 @@
+Write-Host "'ns-session' cannot be used with other commands on the same prompt."

package/bin/pg-query

@@ -0,0 +1,79 @@
+#!/bin/bash
+
+# pg-query: A script to run SQL queries against a remote PostgreSQL database 
+# with smart display limits to prevent blowing out the context
+
+# Unlike the other files in this directory, this must be moved to your ~/.local/bin directory
+# and made executable with `chmod +x' to use. Also the agent needs to be made aware it exists.
+
+# Config
+HOST=""
+PORT=""
+USER=""
+PASSWORD=""
+DATABASE=""
+
+# Default display limit
+DEFAULT_LIMIT=20
+
+smart-query() {
+    local query="$1"
+    local display_limit=${2:-$DEFAULT_LIMIT}
+    local check_limit=$((display_limit + 1))  # Get one extra row to detect truncation
+    
+    if [[ $query =~ ^[[:space:]]*SELECT|^[[:space:]]*select ]]; then
+        # Always enforce our display limit, even if query has existing LIMIT
+        local temp_file=$(mktemp)
+        
+        # Check if query already has LIMIT clause
+        if [[ $query =~ LIMIT|limit ]]; then
+            echo "Query has existing LIMIT - enforcing display limit of $display_limit rows"
+        else
+            echo "Checking for truncation (display limit: $display_limit rows)..."
+        fi
+        
+        # Add our LIMIT to get one more than we want to display (overrides any existing LIMIT)
+        local check_query="SELECT * FROM ($query) AS subquery LIMIT $check_limit"
+        
+        PAGER="" PGPASSWORD="$PASSWORD" psql -h "$HOST" -p "$PORT" -U "$USER" -d "$DATABASE" --pset=pager=off -A -c "$check_query" > "$temp_file"
+        
+        local total_lines=$(wc -l < "$temp_file")
+        local data_lines=$((total_lines - 2))  # Subtract psql headers (usually 2 lines)
+        
+        if [ "$data_lines" -eq "$check_limit" ]; then
+            echo "⚠️  Results truncated: showing first $display_limit rows (more data available)"
+            echo "---"
+            head -$((display_limit + 2)) "$temp_file"  # +2 for headers
+            echo "---"
+            echo "Note: Additional rows exist beyond what is displayed above, page the query to see more, or query more strategically."
+        else
+            echo "✓ Complete result: all $data_lines rows shown"
+            echo "---"
+            cat "$temp_file"
+        fi
+        
+        rm "$temp_file"
+    else
+        # Non-SELECT query (INSERT, UPDATE, DELETE, etc.)
+        echo "✓ Executing non-SELECT query"
+        PAGER="" PGPASSWORD="$PASSWORD" psql -h "$HOST" -p "$PORT" -U "$USER" -d "$DATABASE" --pset=pager=off -A -c "$query"
+    fi
+}
+
+# Main function - can be called as remote-pg
+remote-pg() {
+    local query="$1"
+    local limit="$2"
+    
+    if [ -z "$query" ]; then
+        echo "Usage: $(basename "$0") \"SQL_QUERY\" [DISPLAY_LIMIT]"
+        echo "Example: $(basename "$0") \"SELECT * FROM users\" 50"
+        echo "Default limit: $DEFAULT_LIMIT rows"
+        exit 1
+    fi
+    
+    smart-query "$query" "$limit"
+}
+
+# Execute the function with command line arguments
+remote-pg "$@"

package/dist/agent/agentConfig.js

@@ -0,0 +1,137 @@
+import { sanitizeSpendLimit } from "@naisys/common";
+import table from "text-table";
+import { agentConfigCmd } from "../command/commandDefs.js";
+import { valueFromString } from "../utils/utilities.js";
+export function createAgentConfig(localUserId, { globalConfig }, userService) {
+    let fullAgentConfig = loadConfig();
+    function loadConfig() {
+        const user = userService.getUserById(localUserId);
+        if (!user) {
+            throw new Error(`User with ID ${localUserId} not found`);
+        }
+        return buildFullAgentConfig(user.config);
+    }
+    function buildFullAgentConfig(config) {
+        // Sanitize spend limits
+        const spendLimitDollars = sanitizeSpendLimit(config.spendLimitDollars);
+        const spendLimitHours = sanitizeSpendLimit(config.spendLimitHours);
+        // Validate if spend limit is defined on the agent or .env
+        if (spendLimitDollars === undefined &&
+            globalConfig().spendLimitDollars === undefined) {
+            throw `Agent config: Error, 'spendLimitDollars' needs to be defined in the .env file or agent config`;
+        }
+        // Resolve model configs
+        const shellModel = resolveConfigVars(config.shellModel);
+        const imageModel = config.imageModel
+            ? resolveConfigVars(config.imageModel)
+            : undefined;
+        function resolveConfigVars(templateString) {
+            let resolvedString = templateString;
+            resolvedString = resolveTemplateVars(resolvedString, "agent", config);
+            resolvedString = resolveTemplateVars(resolvedString, "env", globalConfig().variableMap);
+            return resolvedString;
+        }
+        function resolveTemplateVars(templateString, allowedVarString, mappedVar) {
+            const pattern = new RegExp(`\\$\\{${allowedVarString}\\.([^}]+)\\}`, "g");
+            return templateString.replace(pattern, (_match, key) => {
+                const value = valueFromString(mappedVar, key);
+                if (value === undefined) {
+                    throw `Agent config: Error, ${key} is not defined`;
+                }
+                return value;
+            });
+        }
+        return {
+            ...config,
+            spendLimitDollars,
+            spendLimitHours,
+            shellModel,
+            imageModel,
+            resolveConfigVars,
+            mailEnabled: !!config.mailEnabled,
+            chatEnabled: !!config.chatEnabled,
+            webEnabled: !!config.webEnabled,
+            completeSessionEnabled: !!config.completeSessionEnabled,
+            wakeOnMessage: !!config.wakeOnMessage,
+            initialCommands: config.initialCommands ?? [],
+            commandProtection: config.commandProtection ?? "none",
+            debugPauseSeconds: config.debugPauseSeconds === undefined ? 0 : config.debugPauseSeconds,
+            multipleCommandsEnabled: !!config.multipleCommandsEnabled,
+            workspacesEnabled: !!config.workspacesEnabled,
+        };
+    }
+    function updateConfigField(field, value) {
+        const user = userService.getUserById(localUserId);
+        if (!user) {
+            throw new Error(`User with ID ${localUserId} not found`);
+        }
+        // Convert value to appropriate type
+        let typedValue = value;
+        if (value === "true")
+            typedValue = true;
+        else if (value === "false")
+            typedValue = false;
+        else if (!isNaN(Number(value)) && value.trim() !== "")
+            typedValue = Number(value);
+        if (!(field in user.config)) {
+            throw new Error(`Config field '${field}' does not exist`);
+        }
+        // set field
+        user.config[field] = typedValue;
+        // Update in-memory only (not persisted)
+        fullAgentConfig = buildFullAgentConfig(user.config);
+    }
+    function handleCommand(cmdArgs) {
+        const args = cmdArgs.trim().split(/\s+/).filter(Boolean);
+        const config = fullAgentConfig;
+        if (args.length === 0) {
+            // Show all config values as a table
+            const rows = Object.entries(config)
+                .filter(([, value]) => typeof value !== "function")
+                .map(([key, value]) => {
+                const displayValue = typeof value === "object" ? JSON.stringify(value) : String(value);
+                return [key, displayValue];
+            });
+            return table([["Name", "Value"], ...rows], { hsep: " | " });
+        }
+        else if (args.length === 1) {
+            // Show specific config value
+            const name = args[0];
+            const value = config[name];
+            if (value === undefined) {
+                return `Config field '${name}' not found`;
+            }
+            if (typeof value === "function") {
+                return `Config field '${name}' is a function and cannot be displayed`;
+            }
+            return typeof value === "object"
+                ? JSON.stringify(value, null, 2)
+                : String(value);
+        }
+        else {
+            // Update config value (session-only, not persisted)
+            const name = args[0];
+            const value = args.slice(1).join(" ");
+            try {
+                updateConfigField(name, value);
+                return `Config field '${name}' updated to '${value}' (session only, not persisted)`;
+            }
+            catch (error) {
+                return `Failed to update config: ${error instanceof Error ? error.message : String(error)}`;
+            }
+        }
+    }
+    const registrableCommand = {
+        command: agentConfigCmd,
+        handleCommand,
+    };
+    return {
+        ...registrableCommand,
+        agentConfig: () => fullAgentConfig,
+        reloadAgentConfig: () => {
+            fullAgentConfig = loadConfig();
+        },
+        updateConfigField,
+    };
+}
+//# sourceMappingURL=agentConfig.js.map