tkmind_go/documentation/docs/guides/logs.md

title, sidebar_label, sidebar_position

title	sidebar_label	sidebar_position
goose Logging System	Logging System	65

goose uses a unified storage system for conversations and interactions. All conversations and interactions (both CLI and Desktop) are stored locally in the following locations:

Type	Unix-like (macOS, Linux)	Windows
Command History	~/.config/goose/history.txt	%APPDATA%\Block\goose\data\history.txt
Session Records	~/.local/share/goose/sessions/sessions.db	%APPDATA%\Block\goose\data\sessions\sessions.db
System Logs	~/.local/state/goose/logs/	%APPDATA%\Block\goose\data\logs\

:::info Privacy goose is a local application and all log files are stored locally. These logs are never sent to external servers or third parties, ensuring that all data remains private and under your control. :::

Command History

goose stores command history persistently across chat sessions, allowing goose to recall previous commands.

Command history logs are stored in:

• Unix-like: ~/.config/goose/history.txt
• Windows: %APPDATA%\Block\goose\data\history.txt

Session Records

goose maintains session records that track the conversation history and interactions for each session. Sessions are stored in an SQLite database at:

• Unix-like: ~/.local/share/goose/sessions/sessions.db
• Windows: %APPDATA%\Block\goose\data\sessions\sessions.db

:::info Session Storage Migration Prior to version 1.10.0, goose stored session records in individual .jsonl files under ~/.local/share/goose/sessions/. When you upgrade to v1.10.0 or later, your existing sessions are automatically imported into the database. Legacy .jsonl files remain on disk but are no longer managed by goose. :::

This database contains all saved session data including:

• Session metadata (ID, name, working directory, timestamps)
• Conversation messages (user commands, assistant responses, role information)
• Tool calls and results (IDs, arguments, responses, success/failure status)
• Token usage statistics
• Extension data and configuration

Session IDs are named using YYYYMMDD_<COUNT> format, for example: 20250310_2. goose CLI outputs the session ID at the start of each session. To get session IDs, use goose session list command to see all available sessions.

Also see Session Management for details about searching sessions.

System Logs

Main System Log

The main system log locations:

• Unix-like: ~/.local/state/goose/logs/goose.log
• Windows: %APPDATA%\Block\goose\data\logs\goose.log

This log contains general application-level logging including:

• Session file locations
• Token usage statistics as well as token counts (input, output, total)
• LLM information (model names, versions)

When prompt injection detection is enabled, logs also include:

• Security findings with unique IDs (format: SEC-{uuid})
• User decisions (allow/deny) associated with finding IDs

Desktop Application Log

The desktop application maintains its own logs:

• macOS: ~/Library/Application Support/Goose/logs/main.log
• Windows: %APPDATA%\Block\goose\logs\main.log

The Desktop application follows platform conventions for its own operational logs and state data, but uses the standard goose session records for actual conversations and interactions. This means your conversation history is consistent regardless of which interface you use to interact with goose.

CLI Logs

CLI logs are stored in:

• Unix-like: ~/.local/state/goose/logs/cli/
• Windows: %APPDATA%\Block\goose\data\logs\cli\

CLI session logs contain:

• Tool invocations and responses
• Command execution details
• Session identifiers
• Timestamps

Extension logs contain:

• Tool initialization
• Tool capabilities and schemas
• Extension-specific operations
• Command execution results
• Error messages and debugging information
• Extension configuration states
• Extension-specific protocol information

Server Logs

Server logs are stored in:

• Unix-like: ~/.local/state/goose/logs/server/
• Windows: %APPDATA%\Block\goose\data\logs\server\

The Server logs contain information about the goose daemon (goosed), which is a local server process that runs on your computer. This server component manages communication between the CLI, extensions, and LLMs.

Server logs include:

• Server initialization details
• JSON-RPC communication logs
• Server capabilities
• Protocol version information
• Client-server interactions
• Extension loading and initialization
• Tool definitions and schemas
• Extension instructions and capabilities
• Debug-level transport information
• System capabilities and configurations
• Operating system information
• Working directory information
• Transport layer communication details
• Message parsing and handling information
• Request/response cycles
• Error states and handling
• Extension initialization sequences