Changelog¶

1.3.0 (2026/08/26)¶

This release is a feature release, with the following main updates:

New Features¶

• CLI: Added a global --conf parameter to explicitly select a configuration file; configuration display and writes will follow the selected file.
• CLI: Added registry.insecure_skip_verify and registry.request_timeout configurations for controlled development environments and long-running data queries; TLS verification is disabled by default, request timeout defaults to 150 seconds.
• Registry: Added unified OAuth Broker site routing and token issuer/audience validation; the target AI API is determined by the server-side allowlist.
• Center MCP: Can now directly expose static tools and exclude specific tools based on configuration; the default facade tool is still used by default.
• Registry: Added OpenAI Apps challenge endpoint; remains closed and returns 404 when no token is configured.
• Added a local deployment helper for Registry, which can configure remote AI API and S3 services.

Bug Fixes / Optimizations¶

• Preserve unauthorized responses from the OAuth upstream so callers can correctly identify credential issues.
• The limit parameter of owl.data.simple_query_file is now validated to be between 1 and 10000 before execution.
• Data query tool timeout adjusted to 130 seconds; Registry client default timeout adjusted to 150 seconds and made configurable.
• Registry image now includes version and revision information; added regression tests to the release pipeline to improve traceability of build artifacts.

Compatibility Changes¶

• Existing CLI commands and default configuration paths remain unchanged; --conf is a new entry point, TLS verification is disabled by default.
• MCP still exposes facade tools by default; site routing and OpenAI Apps challenge must be explicitly configured to be enabled.
• The Agent Protocol (including owl agent --stdio) is not yet fully designed and is not included in this release.

1.2.1 (2026/08/07)¶

This release is a hotfix release, with the following updates:

Bug Fixes¶

• Fixed an issue where the ID of result files generated by data-type tools was too long; new files now use a 22-character URL-safe random ID, reducing the risk of overly long filenames and paths from long parameters, and making it easier for the Agent to reference in subsequent commands. (#8)
• Fixed an issue where owl.data.simple_query and owl.data.simple_query_file only validated the parameter schema but not the auto-generated DQL; now an equivalent DQL is constructed and validated via the Registry's DQL validation capability before execution, intercepting invalid query fragments early. (#7)

Enhancements¶

• When simple query generated DQL validation fails, structured generated_dql / dql.builderError are returned, making it easier for the Agent to locate and fix parameters such as where_clause, select_clause, and group_by_clause. (#7)

Compatibility Changes¶

• The data file index format and stable queryKey remain unchanged; existing indexes and result files can still be read; only the ID and filename of newly generated files are shorter. (#8)
• Valid simple query invocation methods and remote execution paths remain unchanged; only invalid DQL will fail earlier before the request is sent. (#7)

1.2.0 (2026/08/05)¶

This release is a feature release, with the following main updates:

New Features¶

• CLI: Added owl validate, owl tool validate, and owl capabilities commands to validate parameter schemas and tool-specific syntax without executing the target tool, returning structured results for the Agent to evaluate and fix. (#6)
• Added account workspace and local profile management capabilities, including workspace listing, access key retrieval, workspace switching, and current context viewing; profiles manage workspace credentials and current context, cache and data files continue to use the configured shared path. (3da3e8e)
• Added same-organization workspace discovery, and data queries can now specify same_org_workspace_uuids to query multiple workspaces in the same organization, enabling cross-workspace Trace retrieval. (71fa73e)
• owl exec now includes version update notifications: the CLI throttles checking for new versions based on the update channel, and indicates upgrades in the notice field of JSON output without affecting existing parsing. (7c7113c)
• Added mdsearch document retrieval and SLO listing capabilities to the public tool catalog. (135c8ff, 18f87b0)
• Added Studio Notes V2 note listing, creation, modification, and deletion capabilities to the public tool catalog. (a72af5f)
• Added data forwarding rule discovery and asynchronous query capabilities to the public tool catalog. (6c37c93, c6dcd80)
• Added Dashboard listing capability to the public tool catalog. (6c98f0b)
• Added an OSS auto-release pipeline for five platforms (Linux, macOS, Windows); after passing test channel validation, the same build artifact can be promoted to the production channel. (9fba8e2)

Bug Fixes¶

• Fixed an issue where the HTTP tool's upstream client error caused the Registry to lose the original status and error message; the CLI now obtains more accurate and actionable failure reasons. (e1267e0)
• Fixed an issue where large Dashboard results were still returned via the text path; related tools now use data files to save results, avoiding large payloads consuming Agent context. (68cac16)
• Fixed an issue where data forwarding query results were still returned via the text path; query results are now written to data files. (30aa6fc)
• Fixed an issue where account information could be confused during workspace credential switching and display; configuration output hides the secret by default, only showing the raw secret upon explicit request. (3da3e8e)
• Streamable MCP sessions now complete authentication before being established; unauthorized requests do not create session state. (2a5d8e9)

Enhancements¶

• Unified parameter parsing and pre-check logic for owl exec and owl validate, supporting returning all parameter issues at once; normal first-use or cache expiry auto-sync is performed before validation; if tool_not_found is still returned, run owl sync explicitly and retry. (#6)
• CLI operations now carry a stable operation ID and propagate tracing information between Registry requests and upstream failures, aiding cross-layer issue identification. (386abc0)
• Sensitive tokens in logs are now partially masked, retaining only the first and last characters for correlation, ensuring complete credentials do not appear in logs. (6a6d0ad)

Compatibility Changes¶

• Existing short commands such as list, show, exec, schema and the tool / tools namespace remain compatible; validate and capabilities are new entry points. (#6)
• Old configurations token, auth.token, workspaces.<name>.token, and auth.token_file are still readable; new credentials are written uniformly as api-key, and old configurations are not actively deleted. (3da3e8e)
• PromQL mode of owl.data.query does not enter the DQL validator; existing valid queries and MCP tool invocation methods remain unchanged. (#6)

1.0.11 (2026/05/25)¶

This release is an iterative release, with the following main updates:

New Features¶

• Added a CLI-only tool owl.data.simple_query_file in the data category; after syncing the latest public tool catalog, the CLI can call the existing simple query backend via simple query parameters and save results using the existing data file lifecycle.
• owl.data.simple_query_file maintains a separate exposure surface from the MCP tool owl.data.simple_query, avoiding large results being returned via the MCP text/context path.

Enhancements¶

• Added real public config regression tests covering CLI visibility, MCP invisibility, outputType: data, authentication, and parameter schema for owl.data.simple_query_file.

Compatibility Changes¶

• The existing MCP tool owl.data.simple_query retains its outputType: text and MCP-only exposure behavior unchanged.

1.0.10 (2026/05/18)¶

This release is a hotfix release, with the following updates:

Bug Fixes¶

• Fixed an issue where configuring registry.endpoint with a trailing slash caused the CLI to generate double slashes when constructing Registry API paths, resulting in a 404 error from nginx for owl sync.
• The Registry Client now normalizes the endpoint during construction, so http://testing-owl-api.dataflux.cn/ and http://testing-owl-api.dataflux.cn are treated as the same Registry address.

Enhancements¶

• Added regression tests for the Registry Client and SyncAll, covering category sync paths with trailing-slash endpoints to prevent future URL concatenation degradation.

Compatibility Changes¶

• User configuration format is unchanged; existing endpoints without trailing slashes behave as before, and endpoints with trailing slashes are now also compatible.

1.0.9 (2026/05/12)¶

This release is an iterative release, with the following main updates:

New Features¶

• Added owl.logging.cluster_task.create to the data category; after syncing the latest public tool catalog, the CLI can create asynchronous log clustering analysis tasks.
• Added owl.logging.cluster_task.get to the data category; the asynchronous log clustering analysis result can be queried using the task_id returned by create.
• Log clustering tasks support passing a complete query, or letting the backend assemble the query via namespace, conditions, timeRange, analysisField, and indexes.

Enhancements¶

• Updated the data category description and version, clarifying that the public catalog now includes log clustering task creation and query capabilities.
• Added regression tests for the loader and Registry server, covering log clustering task schema parsing, required parameter validation, and REST execution forwarding.

Compatibility Changes¶

• This change adds new tools and does not alter the invocation of existing owl.logging.list, owl.data.query, or other data category tools.

1.0.8 (2026/05/07)¶

This release is an iterative release, with the following main updates:

New Features¶

• Added owl.logging.list and owl.billing.list to the data category discovery pipeline; after syncing the latest public tool catalog, the CLI can directly discover sources and fields for logs and cloud billing.
• owl.metric.list now supports mode=tag to discover metric tag keys, and supports filtering field or tag results via source.
• Data result filenames now retain a readable prefix and append a UUID, avoiding filename collisions from repeated queries or concurrent sessions.
• Data file indexes now include a stable queryKey to identify the same query, while maintaining compatibility with the old index.json format.

Bug Fixes¶

• Fixed an issue where the discovery tool schema did not declare the source parameter, causing owl exec ... --source ... to be rejected by local parameter validation.
• Fixed an issue where the AIAPI discovery list returned a success:false business error, but the Registry REST and MCP HTTP tools could still incorrectly report success.
• Fixed an issue where after specifying a custom Owl directory via the installer (--owl-dir / -OwlDir), a subsequent owl config show could still fall back to the default configuration directory.

Enhancements¶

• Updated README and usage documentation with data discovery examples, adding invocation methods for mode=field, mode=tag, owl.logging.list, and owl.billing.list.
• Adjusted public catalog sync messages to avoid potentially misleading Scope: public catalog output when public catalog is hit.
• owl data clean now defaults to cleaning files older than 1 day; --days 0 or negative values are treated as 1 day.
• owl data clean only cleans files registered in the index; orphaned files are not actively scanned and deleted.
• Linux/macOS and Windows installers now record the .owldir path next to the installation target, and clean up old records when not using a custom directory or during uninstallation, allowing the CLI to locate custom configuration, cache, and data directories without the OWL_DIR environment variable.
• Added regression tests for loader, executor, Registry REST, and MCP discovery schema and business errors.
• Added regression tests for CLI configuration parsing and installer custom directory, covering .owldir record reading, config show path display, and directory target after installation.

Compatibility Changes¶

• owl exec parameter forms remain unchanged, still supporting --key value, key=value, -p JSON, and --stdin.
• Non-metric discovery tools only allow mode=source|field; mode=tag is only applicable to owl.metric.list.

1.0.7 (2026/04/29)¶

This release is an iterative release, with the following main updates:

New Features¶

• CLI: Added the tool namespace, with tools preserved as an alias; this entry serves as a secondary form for top-level commands such as list, show, exec, and schema, improving fault tolerance when the Agent guesses command forms.
• category now has categories as an alias, making it easier for the Agent to discover categories through natural command guessing.

Bug Fixes¶

• Fixed an issue where help topics like owl help tool and owl help categories could not be resolved.
• Fixed an issue where some --help calls triggered configuration initialization or Registry dependencies prematurely; help commands can now be returned directly in an unconfigured environment.

Enhancements¶

• Added regression tests for help topics, confirming that querying help by topic (e.g., owl help tool) and by command (e.g., owl tool --help) return consistent information.
• Updated the tool viewing command examples in the README to include the tool namespace usage.

Compatibility Changes¶

• Existing top-level commands such as list, show, exec, and schema remain the primary usage methods and continue to be compatible, avoiding breaking existing scripts.
• Some example tools and Skill configurations that are no longer published have been cleaned up.

1.0.6 (2026/04/28)¶

This release is an iterative release, with the following main updates:

New Features¶

• Added the owl update command, which downloads and executes the platform-specific installation script according to the update channel recorded by the installer.
• Linux/macOS installation scripts now support --upgrade, and Windows installation scripts support -Upgrade, for upgrading the local CLI only when a newer remote version is available.
• The installer writes update.base_url and update.channel into the configuration, providing the update source for subsequent owl update commands.

Bug Fixes¶

• Fixed an issue where the upgrade could not reliably locate the existing installation path; the upgrade process now reads the binpath from the Owl directory first, then falls back to owl in PATH.
• Fixed an issue where the upgrade could still overwrite the installation even when the local version was not lower than the remote version; the binary replacement is now skipped, and only the update channel configuration is refreshed.

Enhancements¶

• The installer now includes semantic version comparison logic, comparing the local owl --version with the remote channel version before upgrading.
• The update process executes the installation script synchronously on Linux/macOS, and launches the installer as a separate PowerShell process on Windows, reducing the risk of replacing a running binary.

1.0.5 (2026/04/28)¶

This release is a hotfix release, with the following updates:

Bug Fixes¶

• Fixed an issue where the Linux/macOS installer reported bad substitution when performing checksum comparison under macOS's built-in Bash 3.2.
• Replaced Bash 4 syntax ${var,,} with tr '[:upper:]' '[:lower:]', which is available in POSIX toolchains, to ensure checksum case normalization is compatible with older Bash.

Enhancements¶

• Rebuilt the CLI packages for 5 platforms, ensuring the release directory version, manifest version, and owl --version output within the package are consistent.
• Retained both skill.md and skill.en.md Skill documentation, continuing to support bilingual Agent Skill distribution.

1.0.4 (2026/04/27)¶

This release is an installer channel release, with the following main updates:

New Features¶

• Released skill.en.md, completing the English Agent Skill description file.
• Published installer support files supporting temporary code installation and custom Owl directories to the 1.0.4 channel directory.

Bug Fixes¶

• Fixed an issue where the previous production channel installation script lacked support for OWL_DIR / OwlDir.
• Avoided overwriting the same version release when an existing 1.0.3 channel was affected by sync cache; used a new channel directory to host the corrected installation entry.

1.0.3 (2026/04/27)¶

This release is an iterative release, with the following main updates:

New Features¶

• The installer now supports OWL_TEMP_CODE, which derives the ai-api address from OWL_REGISTRY_ENDPOINT and exchanges the temporary code for a real token via /api/v1/account/accesskey/exchange.
• Added skill.md, providing a Skill description distributed with the channel for Agent integration scenarios.

Bug Fixes¶

• Fixed an issue where reading BASH_SOURCE[0] could fail under the bash -c "$(curl .../install.sh)" entry point; changed to script entry parsing with $0 fallback.
• Fixed an issue where unexpected newline formatting appeared in the inline installer helper, making the released install.sh closer to a directly executable self-contained script.

Enhancements¶

• When exchanging a temporary code for a token, the installer now checks whether OWL_TOKEN matches the exchange result; if not, installation is aborted immediately.
• The OWL_TEMP_CODE request now bypasses the local proxy by default, reducing the likelihood of proxy configuration interfering with temporary credential exchange.

1.0.2 (2026/04/24)¶

This release is an iterative release, with the following main updates:

New Features¶

• CLI and installer support custom Owl working directory: added OWL_DIR, --owl-dir, -OwlDir.
• Installer supports OWL_OWNER / --owl-owner, making it convenient to hand over the configuration directory to a service user after cloud-init or root installation.
• After installation, the binary path is recorded in the binpath file under the Owl directory, for use by subsequent upgrades and Agent runtime location.

Bug Fixes¶

• Fixed an issue where the installer persisted registry.endpoint and auth.token to the current user's home directory; now it writes to the specified Owl directory.
• Fixed an issue where config show displayed an incorrect directory in custom directory scenarios.

Enhancements¶

• README now includes cloud-init / systemd service user installation instructions, clarifying the recommended usage of OWL_DIR and OWL_OWNER.
• Uninstall prompts, configuration directory initialization, and path recording logic in the installation script now uniformly use the resolved Owl directory.

1.0.1 (2026/04/23)¶

This release is a hotfix release, with the following updates:

New Features¶

• CLI: Added first-use auto-sync capability: when the local cache is empty or the cache exceeds registry.sync_interval, commands such as list, show, exec, schema, and category automatically trigger owl sync.
• Added sync.auto configuration option to disable auto-sync.

Bug Fixes¶

• Fixed an issue where the owl binary in the 1.0.0 Linux/macOS tar package lacked executable permissions.
• Fixed an issue where owl sync incremental sync did not clean up the cache for categories that had been deleted on the remote side.
• Fixed an issue where the installation script could exit prematurely due to set -u in environments without HOME (cloud-init / systemd / container).

Enhancements¶

• When auto-sync fails, the behavior distinguishes between first-time sync and cache refresh: first-time sync failure returns an error, while cache refresh failure retains the old cache and outputs a warning.
• The release directory restored and tracked 1.0.0 and 1.0.1 channel artifacts, added installer regression tests and CRLF/LF audit.

1.0.0 (2026/04/13)¶

This release is the initial release, with the following main updates:

New Features¶

• Released the first channel version of the Owl CLI, providing packages for 5 platforms: Linux, macOS, and Windows.
• Provided install.sh, install.ps1, owl-install.ps1, and SHA256SUMS, supporting remote channel installation, version-specific installation, local package installation, and checksum verification.
• CLI supports initial configuration, login with token writing, tool catalog sync, category viewing, tool viewing, tool execution, OpenAI function schema output, cache management, and data file management.

Enhancements¶

• The release directory includes README and USAGE documents, explaining test/production channel installation, runtime configuration, offline installation, uninstallation, and common commands.
• The build pipeline supports cross-platform cross-compilation, and records the current version, historical versions, release time, commit, and platform list via the version manifest.

Known Issues¶

• The owl binary in the Linux/macOS tar package has permissions set to 0644, making it non-executable after extraction; this issue is fixed in 1.0.1.