grip status - Grip AI

Overview

The grip status command displays a comprehensive overview of your Grip AI system, including configuration details, workspace status, active sessions, memory usage, and provider information.

Usage

grip status

Output Example

$ grip status

╭─ grip Status ────────────────────────────────────╮
│                                                  │
│  Provider          Anthropic (claude-sonnet-4-6) │
│  Model             claude-sonnet-4-6             │
│  Max Tokens        4096                          │
│  Temperature       0.7                           │
│  Tool Iterations   10                            │
│  Memory Window     50                            │
│                                                  │
│  Workspace         /home/user/grip/workspace     │
│  Workspace Status  Initialized                   │
│  Sessions          3                             │
│  MEMORY.md         45.2 KB                       │
│  HISTORY.md        128.7 KB                      │
│                                                  │
│  Sandbox Mode      Disabled                      │
│  Shell Timeout     60s                           │
│  MCP Servers       2                             │
│                                                  │
│  Channels          telegram (enabled)            │
│                    discord (disabled)            │
│                    slack (disabled)              │
│                                                  │
│  Heartbeat         Every 60min                   │
│                                                  │
│  Providers         openai (key set)              │
│                    anthropic (key set)           │
│                    openrouter (no key)           │
╰──────────────────────────────────────────────────╯

Information Sections

Model Configuration

Shows the active AI model settings:

Provider - Display name and model identifier
Model - Full model path (e.g., anthropic/claude-sonnet-4-6)
Max Tokens - Maximum response length
Temperature - Randomness setting (0.0 = deterministic, 1.0 = creative)
Tool Iterations - Maximum tool calling loops
Memory Window - Number of recent interactions to retain

Example:

Provider          Anthropic (claude-sonnet-4-6)
Model             claude-sonnet-4-6
Max Tokens        4096
Temperature       0.7
Tool Iterations   10
Memory Window     50

Workspace Status

Shows workspace location and health:

Workspace - Absolute path to workspace directory
Workspace Status - Initialized or Not initialized
Sessions - Number of active session files
MEMORY.md - Long-term memory file size
HISTORY.md - Conversation history file size

Example:

Workspace         /home/user/grip/workspace
Workspace Status  Initialized
Sessions          3
MEMORY.md         45.2 KB
HISTORY.md        128.7 KB

Status meanings:

Initialized - Workspace directory exists with required structure
Not initialized - Workspace needs setup (run grip agent to initialize)

File sizes:

Shown in B (bytes), KB (kilobytes), or MB (megabytes)
not created - File doesn’t exist yet (normal for new installations)

Tool Configuration

Shows security and tool settings:

Sandbox Mode - Whether file access is restricted to workspace
Shell Timeout - Maximum seconds for shell command execution
MCP Servers - Number of configured Model Context Protocol servers

Example:

Sandbox Mode      Disabled
Shell Timeout     60s
MCP Servers       2

Sandbox modes:

Enabled - File operations restricted to workspace directory only
Disabled - File access based on trust mode settings

Channel Status

Shows messaging platform integration status:

telegram - Telegram bot connection state
discord - Discord bot connection state
slack - Slack bot connection state

Example:

Channels          telegram (enabled)
                  discord (disabled)
                  slack (disabled)

States:

enabled (green) - Channel is configured and active
disabled (dim) - Channel is not configured or turned off

Heartbeat Service

Shows autonomous agent check-in settings: Example:

Heartbeat         Every 60min

States:

Every Xmin - Heartbeat is enabled with interval
Disabled - Heartbeat service is turned off

Configured Providers

Lists all providers with API key status: Example:

Providers         openai (key set)
                  anthropic (key set)
                  openrouter (no key)

Key status:

key set (green) - Provider has API key configured
no key (dim) - Provider exists but no API key

Interpreting Status

Healthy System

╭─ grip Status ────────────────────────────────────╮
│  Provider          OpenAI (gpt-4o)               │
│  Workspace Status  Initialized                   │
│  Sessions          5                             │
│  MEMORY.md         67.3 KB                       │
│  Providers         openai (key set)              │
╰──────────────────────────────────────────────────╯

Indicators:

✓ Provider configured with API key
✓ Workspace initialized
✓ Sessions exist (agent has been used)
✓ Memory files created

New Installation

╭─ grip Status ────────────────────────────────────╮
│  Provider          Anthropic (claude-sonnet-4-6) │
│  Workspace Status  Not initialized               │
│  Sessions          0                             │
│  MEMORY.md         not created                   │
│  HISTORY.md        not created                   │
╰──────────────────────────────────────────────────╯

Next steps:

Run grip agent to initialize workspace
Start a conversation to create memory files

Missing Configuration

╭─ grip Status ────────────────────────────────────╮
│  Provider          openrouter                    │
│  Providers         openrouter (no key)           │
╰──────────────────────────────────────────────────╯

Action needed:

grip config set providers.openrouter.api_key YOUR_API_KEY

Use Cases

Quick Health Check

grip status

Verify system is properly configured before starting.

Debugging Issues

$ grip agent
Error: Workspace not initialized

$ grip status
Workspace Status  Not initialized

$ grip agent
# Workspace will be created automatically

Checking Session Count

$ grip status | grep Sessions
Sessions          12

Monitor active sessions for cleanup.

Verifying Provider Configuration

$ grip status | grep -A3 "Providers"
Providers         openai (key set)
                  anthropic (key set)

Confirm API keys are configured.

Monitoring Memory Usage

$ grip status | grep -E "MEMORY|HISTORY"
MEMORY.md         2.3 MB
HISTORY.md        5.7 MB

Track memory file growth over time.

Channel Status Check

$ grip status | grep -A3 "Channels"
Channels          telegram (enabled)
                  discord (disabled)
                  slack (disabled)

Verify which channels are active.

Workspace Files

The status command checks these workspace files:

Directory Structure

~/grip/workspace/
├── memory/
│   ├── MEMORY.md      # Long-term facts and context
│   └── HISTORY.md     # Recent conversation history
├── sessions/
│   ├── cli:interactive.json
│   ├── telegram:123456.json
│   └── api:user_789.json
└── tools/
    └── (tool-specific data)

MEMORY.md

Stores long-term agent memory:

User preferences
Important facts
Project context
Custom instructions

Size indicators:

< 100 KB - Normal for casual use
100 KB - 1 MB - Moderate usage
1 MB - Heavy usage, consider periodic cleanup

HISTORY.md

Stores recent conversation history:

Last 50 interactions (configurable via memory_window)
Message summaries
Tool execution results

Size indicators:

< 200 KB - Normal
200 KB - 1 MB - Active usage
1 MB - Very active, auto-compacts during conversations

Sessions

Each session file contains:

Message history
Agent state
Tool call records
Model configuration

Session count:

0 - New installation or no usage
1-5 - Normal usage
10+ - Multiple users or channels

Scripting with Status

Extract Specific Values

# Get workspace path
WORKSPACE=$(grip status | grep "Workspace " | awk '{print $2}')
echo $WORKSPACE

# Get session count
SESSIONS=$(grip status | grep "Sessions" | awk '{print $2}')
echo "Active sessions: $SESSIONS"

# Check if workspace is initialized
if grip status | grep -q "Workspace Status  Initialized"; then
  echo "Workspace ready"
else
  echo "Workspace needs initialization"
fi

Monitor System Health

#!/bin/bash
# health-check.sh

echo "=== Grip AI Health Check ==="
grip status

# Check for issues
if ! grip status | grep -q "key set"; then
  echo "⚠️  Warning: No API keys configured"
fi

if ! grip status | grep -q "Initialized"; then
  echo "⚠️  Warning: Workspace not initialized"
fi

echo "✓ Health check complete"

Session Cleanup Script

#!/bin/bash
# cleanup-old-sessions.sh

WORKSPACE=$(grip status | grep "Workspace " | awk '{print $2}')
SESSIONS_DIR="$WORKSPACE/sessions"

echo "Current sessions: $(grip status | grep Sessions | awk '{print $2}')"

# Remove sessions older than 30 days
find "$SESSIONS_DIR" -name "*.json" -mtime +30 -delete

echo "After cleanup: $(grip status | grep Sessions | awk '{print $2}')"

View Configuration

grip config show

See full configuration with all settings.

Modify Settings

grip config set agents.defaults.temperature 0.3
grip config set agents.defaults.max_tokens 8192

Change values shown in status.

Check Config Path

grip config path

Locate the configuration file.

Test Provider Connection

grip agent -m "test"

Verify provider is working.

Troubleshooting

Workspace Not Initialized

$ grip status
Workspace Status  Not initialized

Solution:

grip agent
# Workspace will be created automatically

No API Key Configured

$ grip status
Providers         openai (no key)

Solution:

grip config set providers.openai.api_key YOUR_KEY
# or
export OPENAI_API_KEY="YOUR_KEY"

Large Memory Files

$ grip status
MEMORY.md         5.2 MB
HISTORY.md        12.8 MB

Solution:

# Compact in interactive mode
grip agent
> /compact

# Or manually edit files
vim ~/grip/workspace/memory/MEMORY.md

Many Old Sessions

$ grip status
Sessions          47

Solution:

# Remove old session files
find ~/grip/workspace/sessions/ -mtime +30 -delete

# Check again
grip status

grip config - View and modify configuration
grip agent - Start using the agent
grip gateway - Start full platform
grip onboard - Initial setup wizard

REST API

CLI Commands

Built-in Tools

​Overview

​Usage

​Output Example

​Information Sections

​Model Configuration

​Workspace Status

​Tool Configuration

​Channel Status

​Heartbeat Service

​Configured Providers

​Interpreting Status

​Healthy System

​New Installation

​Missing Configuration

​Use Cases

​Quick Health Check

​Debugging Issues

​Checking Session Count

​Verifying Provider Configuration

​Monitoring Memory Usage

​Channel Status Check

​Workspace Files

​Directory Structure

​MEMORY.md

​HISTORY.md

​Sessions

​Scripting with Status

​Extract Specific Values

​Monitor System Health

​Session Cleanup Script

​Related Commands

​View Configuration

​Modify Settings

​Check Config Path

​Test Provider Connection

​Troubleshooting

​Workspace Not Initialized

​No API Key Configured

​Large Memory Files

​Many Old Sessions

​Related Commands

Build docs developers (and LLMs) love

Overview

Usage

Output Example

Information Sections

Model Configuration

Workspace Status

Tool Configuration

Channel Status

Heartbeat Service

Configured Providers

Interpreting Status

Healthy System

New Installation

Missing Configuration

Use Cases

Quick Health Check

Debugging Issues

Checking Session Count

Verifying Provider Configuration

Monitoring Memory Usage

Channel Status Check

Workspace Files

Directory Structure

MEMORY.md

HISTORY.md

Sessions

Scripting with Status

Extract Specific Values

Monitor System Health

Session Cleanup Script

Related Commands

View Configuration

Modify Settings

Check Config Path

Test Provider Connection

Troubleshooting

Workspace Not Initialized

No API Key Configured

Large Memory Files

Many Old Sessions

Related Commands