Skip to content

Changelog

1.2.1 (2026/08/07)

This hotfix release includes the following changes.

Bug Fixes

  • Fixed overly long result-file IDs generated by data tools. New files use 22-character URL-safe random IDs, reducing long-file-name and path risks and making IDs easier for agents to reference. (#8)
  • Fixed owl.data.simple_query and owl.data.simple_query_file validating only their parameter schemas. The CLI now constructs equivalent DQL and calls the Registry DQL validator before execution, rejecting invalid query fragments early. (#7)

Improvements

  • Generated-DQL validation failures return structured generated_dql / dql.builderError issues so agents can correct parameters such as where_clause, select_clause, and group_by_clause. (#7)

Compatibility

  • The data-file index format and stable queryKey are unchanged. Existing indexes and result files remain readable; only newly generated IDs and file names are shorter. (#8)
  • Valid simple-query calls and the remote execution path are unchanged. Only invalid DQL now fails earlier, before the request is sent. (#7)

1.2.0 (2026/08/05)

This feature release includes the following changes.

New Features

  • Added owl validate, owl tool validate, and owl capabilities. Agents can validate a parameter schema and tool-specific syntax without executing the selected tool, and negotiate support through a structured capability response. (#6)
  • Added account-workspace and local-profile management, including workspace listing, access-key retrieval, workspace switching, and current-context display. Profiles manage workspace credentials and the current context, while cache and data files continue to use the configured shared paths. (3da3e8e)
  • Added same-organization workspace discovery and the same_org_workspace_uuids data-query parameter for cross-workspace queries such as Trace retrieval. (71fa73e)
  • Added update notices to owl exec. The CLI checks its configured update channel on a throttled schedule and adds a notice field to JSON output without breaking existing parsers. (7c7113c)
  • Added mdsearch document retrieval and SLO listing to the public catalog. (135c8ff, 18f87b0)
  • Added public tools for listing, creating, modifying, and deleting Studio Notes V2 notes. (a72af5f)
  • Added public tools for data-forwarding rule discovery and asynchronous queries. (6c37c93, c6dcd80)
  • Added Dashboard listing to the public catalog. (6c98f0b)
  • Added an OSS release pipeline for five Linux, macOS, and Windows platform packages. The same artifact tested in the test channel can be promoted to production. (9fba8e2)

Bug Fixes

  • Fixed Registry dropping the original status and error details for HTTP tool upstream client errors. The CLI now receives more accurate and actionable failures. (e1267e0)
  • Fixed large Dashboard results using the text path. Dashboard tools now save results as data files to avoid consuming agent context with large payloads. (68cac16)
  • Fixed data-forwarding query results using the text path. Query results are now written to data files. (30aa6fc)
  • Fixed account information being confused while switching or displaying workspace credentials. Configuration output masks keys by default and reveals raw secrets only when explicitly requested. (3da3e8e)
  • Streamable MCP requests now authenticate before session creation, so unauthorized requests do not allocate session state. (2a5d8e9)

Improvements

  • Unified parameter parsing and preflight checks between owl exec and owl validate, reporting all parameter problems together. Normal first-use or cache-expiry auto-sync runs before validation; if it still returns tool_not_found, run owl sync explicitly and retry. (#6)
  • Added a stable operation ID to CLI operations and propagated tracing metadata through Registry requests and upstream failures for cross-layer troubleshooting. (386abc0)
  • Masked sensitive log tokens while retaining their leading and trailing characters for correlation, preventing complete credentials from entering logs. (6a6d0ad)

Compatibility

  • Existing top-level commands such as list, show, exec, and schema, plus the tool / tools namespaces, remain compatible. validate and capabilities are additive. (#6)
  • Legacy token, auth.token, workspaces.<name>.token, and auth.token_file settings remain readable. Newly written credentials use api-key, and legacy settings are not removed automatically. (3da3e8e)
  • PromQL mode for owl.data.query does not invoke the DQL validator. Existing valid queries and MCP tool invocation forms are unchanged. (#6)

1.0.11 (2026/05/25)

This iterative release includes the following changes.

New Features

  • Added the CLI-only owl.data.simple_query_file tool to the data category. After syncing the latest public catalog, CLI users can call the existing simple-query backend through simplified parameters and save results through the established data-file lifecycle.
  • Kept owl.data.simple_query_file separate from the MCP tool owl.data.simple_query, preventing large results from being returned through MCP text/context paths.

Improvements

  • Added real public-config regression coverage for CLI visibility, MCP invisibility, outputType: data, authentication, and parameter-schema behavior.

Compatibility

  • The existing MCP tool owl.data.simple_query remains MCP-only and keeps outputType: text.

1.0.10 (2026/05/18)

This hotfix release includes the following changes.

Bug Fixes

  • Fixed Registry API paths containing a double slash, which could cause an nginx 404 during owl sync when registry.endpoint ended with /.
  • Registry Client now normalizes the endpoint during construction, treating http://testing-owl-api.dataflux.cn/ and http://testing-owl-api.dataflux.cn equivalently.

Improvements

  • Added Registry Client and SyncAll regression coverage for category synchronization with trailing-slash endpoints.

Compatibility

  • The configuration format is unchanged. Existing endpoints without a trailing slash keep their behavior, and endpoints with a trailing slash are now supported.

1.0.9 (2026/05/12)

This iterative release includes the following changes.

New Features

  • Added owl.logging.cluster_task.create to the data category for creating asynchronous log-clustering analysis tasks.
  • Added owl.logging.cluster_task.get for retrieving asynchronous log-clustering results through the task_id returned by create.
  • Log-clustering tasks accept a complete query, or can let the backend assemble one from namespace, conditions, timeRange, analysisField, and indexes.

Improvements

  • Updated the data category description and version for the new log-clustering create and get capabilities.
  • Added loader and Registry server regression coverage for schema parsing, required-parameter validation, and REST execution forwarding.

Compatibility

  • These are additive tools. Existing invocation forms for owl.logging.list, owl.data.query, and other data tools are unchanged.

1.0.8 (2026/05/07)

This iterative release includes the following changes.

New Features

  • Added owl.logging.list and owl.billing.list to data discovery. After syncing the latest public catalog, the CLI can discover log and cloud-billing sources and fields.
  • Added mode=tag to owl.metric.list for metric tag-key discovery, plus source filtering for fields and tags.
  • Data result-file names now retain a readable prefix and append a UUID, preventing repeated or concurrent queries from overwriting files.
  • Added a stable queryKey to the data-file index while retaining compatibility with older index.json files.

Bug Fixes

  • Fixed discovery schemas omitting the source parameter and causing local validation to reject owl exec ... --source ....
  • Fixed Registry REST and MCP HTTP wrappers reporting success when AIAPI discovery returned a business-level success:false response.
  • Fixed owl config show falling back to the default configuration directory after installation with a custom Owl directory through --owl-dir / -OwlDir.

Improvements

  • Updated README and usage examples for mode=field, mode=tag, owl.logging.list, and owl.billing.list.
  • Clarified public-catalog synchronization output by removing the potentially confusing Scope: public catalog message.
  • owl data clean defaults to one day; --days 0 or a negative value is treated as one day.
  • owl data clean removes only expired files recorded in the index and does not scan for unindexed orphan files.
  • Linux/macOS and Windows installers record .owldir beside the installation target and remove stale records when using the default directory or uninstalling, allowing the CLI to locate custom configuration, cache, and data directories without OWL_DIR.
  • Added loader, executor, Registry REST, and MCP regression coverage for discovery schemas and business errors.
  • Added CLI configuration and installer regression coverage for .owldir, config show, and custom installation directories.

Compatibility

  • Existing owl exec parameter forms remain supported: --key value, key=value, -p JSON, and --stdin.
  • Non-metric discovery tools support only mode=source|field; mode=tag applies only to owl.metric.list.

1.0.7 (2026/04/29)

This iterative release includes the following changes.

New Features

  • Added the tool namespace and retained the tools alias as tolerant alternatives to top-level list, show, exec, and schema commands for agents guessing command forms.
  • Added the categories alias to category for the same purpose.

Bug Fixes

  • Fixed help topics such as owl help tool and owl help categories not resolving.
  • Fixed some --help calls initializing configuration or Registry dependencies too early. Help now works without configuration.

Improvements

  • Added help-topic regression coverage confirming that topic help such as owl help tool matches command help such as owl tool --help.
  • Updated README command examples for the tool namespace.

Compatibility

  • Existing top-level list, show, exec, and schema commands remain the primary and compatible forms.
  • Removed example tool and Skill configuration no longer included in releases.

1.0.6 (2026/04/28)

This iterative release includes the following changes.

New Features

  • Added owl update, which downloads and runs the platform installer recorded for the active update channel.
  • Added --upgrade to Linux/macOS installation and -Upgrade to Windows installation, upgrading only when a newer remote version exists.
  • Installers now write update.base_url and update.channel for subsequent owl update calls.

Bug Fixes

  • Fixed upgrades failing to locate the existing installation reliably. The upgrader first reads binpath from the Owl directory, then falls back to owl on PATH.
  • Fixed an equal or older remote version replacing the local binary. The installer now skips binary replacement and only refreshes update-channel configuration.

Improvements

  • Added semantic-version comparison before upgrades, using local owl --version and the remote channel version manifest.
  • Linux/macOS runs the installer synchronously; Windows starts an independent PowerShell process to reduce the risk of replacing the running binary.

1.0.5 (2026/04/28)

This hotfix release includes the following changes.

Bug Fixes

  • Fixed Linux/macOS installer checksum comparison failing with bad substitution under the Bash 3.2 bundled with macOS.
  • Replaced Bash 4 ${var,,} syntax with the portable tr '[:upper:]' '[:lower:]' normalization path.

Improvements

  • Rebuilt all five platform packages so release-directory versions, manifest versions, and owl --version output match.
  • Retained both skill.md and skill.en.md for Chinese and English Agent Skill distribution.

1.0.4 (2026/04/27)

This installer-channel release includes the following changes.

New Features

  • Published skill.en.md to complete the English Agent Skill documentation.
  • Published installer support files for temporary-code installation and custom Owl directories under the 1.0.4 channel.

Bug Fixes

  • Fixed the previous production-channel installer missing OWL_DIR / OwlDir support.
  • Avoided overwriting a cached 1.0.3 channel by publishing corrected installation entry points under a new channel directory.

1.0.3 (2026/04/27)

This iterative release includes the following changes.

New Features

  • Added OWL_TEMP_CODE support. The installer derives the ai-api address from OWL_REGISTRY_ENDPOINT and exchanges the temporary code for a token through /api/v1/account/accesskey/exchange.
  • Added skill.md for Agent integration and channel distribution.

Bug Fixes

  • Fixed BASH_SOURCE[0] lookup failing under bash -c "$(curl .../install.sh)" by adding a $0 fallback.
  • Fixed unexpected newline syntax in the inline installer helper, keeping the published install.sh self-contained and directly executable.

Improvements

  • The temporary-code flow validates that an existing OWL_TOKEN matches the exchanged token and stops on mismatch.
  • OWL_TEMP_CODE exchange bypasses the local proxy by default, reducing the chance that proxy configuration affects temporary credentials.

1.0.2 (2026/04/24)

This iterative release includes the following changes.

New Features

  • Added custom Owl working directories through OWL_DIR, --owl-dir, and -OwlDir.
  • Added OWL_OWNER / --owl-owner so root or cloud-init installations can hand the configuration directory to a service user.
  • Recorded the binary path in binpath under the Owl directory for later upgrades and agent execution.

Bug Fixes

  • Fixed installers always writing registry.endpoint and auth.token to the current user's directory instead of the selected Owl directory.
  • Fixed config show displaying an inaccurate directory for custom-directory installations.

Improvements

  • Added cloud-init and systemd service-user installation guidance for OWL_DIR and OWL_OWNER.
  • Unified uninstall prompts, configuration initialization, and path recording around the resolved Owl directory.

1.0.1 (2026/04/23)

This hotfix release includes the following changes.

New Features

  • Added first-use automatic synchronization. When the local cache is empty or older than registry.sync_interval, commands such as list, show, exec, schema, and category automatically run owl sync.
  • Added sync.auto to disable automatic synchronization.

Bug Fixes

  • Fixed the owl binary in Linux/macOS 1.0.0 tarballs missing executable permission.
  • Fixed incremental owl sync retaining category cache entries deleted remotely.
  • Fixed installers exiting early under set -u in some cloud-init, systemd, and container environments without HOME.

Improvements

  • Automatic synchronization distinguishes first synchronization from cache refresh. First-sync failure returns an error; refresh failure preserves the old cache and emits a warning.
  • Restored and tracked 1.0.0 and 1.0.1 channel artifacts, completed installer regression tests, and added CRLF/LF auditing.

1.0.0 (2026/04/13)

This is the initial release.

New Features

  • Released the first Owl CLI channel version with five Linux, macOS, and Windows packages.
  • Added install.sh, install.ps1, owl-install.ps1, and SHA256SUMS for remote-channel installation, explicit-version installation, local-package installation, and checksum verification.
  • Added CLI support for configuration initialization, token login, tool-catalog synchronization, category and tool inspection, tool execution, OpenAI function-schema output, cache management, and data-file management.

Improvements

  • Included README and USAGE documentation in the release directory for test/production channel installation, runtime configuration, offline installation, uninstallation, and common commands.
  • Added cross-platform builds and a version manifest recording the current version, history, release time, commit, and platform list.

Known Issues

  • The owl binary in Linux/macOS tarballs had 0644 permissions and was not executable immediately after extraction. This was fixed in 1.0.1.