OWL Changelog¶

This document records changes to the OWL CLI (owl), OWL Registry (registry), and the public tool catalog shared by both.

1.8.0(2026/11/04)¶

New Features¶

• Registry adds source IP V2 signatures for configured Studio/AIAPI targets. HTTP API, remote MCP, and related child calls share signing. Each send attempt and transport retry gets a new nonce and signature.
• Added owl.field_schema.search to search field configuration in the authorized workspace by keyword, kind, namespace, and measurement. Results include types, units, and unit sources. Pages default to 100 items, with a maximum of 1000. The full-catalog owl.field_schema.get remains available. Search only when fields are unknown or context is no longer valid. No match does not prove that stored data is absent.
• Added event offsets, comment pages, infrastructure and same-organization Trace cursors, topology grouping, and optional Monitor/SLO/Member pagination. Keep filters, time ranges, and permission context unchanged between pages. Existing calls that omit new pagination fields keep their previous behavior.
• Note changes and deletion accept expected_etag to bind the write to the version that was read. Write errors retain completed steps, resource identity, and recovery information to distinguish a failed write from a failed read after a completed write.

Fixes and Improvements¶

• Source IP uses the first X-Forwarded-For address. It uses the connection peer only when the entire header is absent or blank. An invalid first address causes signing to fail; later addresses are not used. Protected targets reject automatic redirects.
• CLI, REST, and MCP retain structured upstream errors, DQL diagnostics, and write recovery information. The CLI improves parameter help, combination checks, and cluster query time validation. Contracts clarify P95 examples, LN, query limits, Pipeline samples, and LLM application categories. Cluster counts do not prove complete time-range coverage.
• External MCP retains failures and the order and boundaries of text blocks. Fixes cover timeouts, cancellation, stdio process exit, pipe reads, and npx recovery. The message limit is 1 MiB. Output and stderr redact credentials. Tool risk annotations pass through discovery and caching; they do not replace authorization or approval.

Upgrade and Compatibility¶

• Deploy compatible Studio support first. Then upgrade Registry and refresh tool discovery: run owl sync for CLI clients and discover MCP tools again. Catalog sync does not update the CLI binary. Upgrade the CLI for the new help, local checks, and full error diagnostics.
• The Registry image configuration enables signing by default. Administrators must set OWL_AI_API_BASE_URL and OWL_AIAPI_SIGNING_SECRET_BASE64. Studio must support V2 and use the same 32-byte key encoded as standard Base64. Missing endpoint or key settings prevent startup. Update aiapiSigning in custom configurations; omission keeps it disabled. For stdio or deployments that do not use signing, explicitly set aiapiSigning.enabled: false.
• The ingress gateway must set and clean X-Forwarded-For. Studio/gateway must independently reject unsigned requests on protected routes and enforce IP allowlists, permissions, time windows, and nonce deduplication. An Owl upgrade alone does not activate the complete protection path.
• After a note version conflict, read again and compare changes. Do not replace the ETag and replay automatically. Omitting expected_etag gives no protection against changes after the read. Monitor updates retain omitted status, alert policies, and tags; explicit empty lists clear associations. Do not repeat a completed create after a read-back failure. Check unknown send outcomes first.

1.7.0(2026/10/28)¶

New Features¶

• Added owl.catalog.entity_create, owl.catalog.entity_modify, and the team query owl.workspace.member.group_list; catalog queries now support filtering by name, URN, and attributes.
• The CLI now includes runtime-profile/v1, where the executor injects a separate Profile and credentials per user without writing credentials to the configuration.
• Added owl.data.read_dql_docs to paginate through DQL document content in the Registry using the tool references returned by the search.

Bug Fixes and Optimizations¶

• DQL validation now preserves the original query, parsing or binding diagnostics, and available row/column information, and distinguishes query errors from an unavailable validator.
• Limited the request header length of CLI command logs to prevent transmission failures caused by long inline parameters; business parameters are still transmitted through the full request body.
• Infrastructure filter expressions removed like, which is unsupported upstream, and now support =, !=, and in.

Upgrade and Compatibility Notes¶

• After upgrading the CLI and Registry together, run owl sync so MCP clients rediscover the tools. Catalog writes depend on the matching AIAPI/Backend; see Catalog Entity Creation and Modification for usage.
• When reading DQL documents, use the returned read_reference and do not read references_dir on the Agent host. The matching order for enabling the runtime Profile is Owl → Agent full release package → reinstall with user mode enabled; before rolling back, disable user mode and reinstall first.

1.6.1(2026/10/23)¶

Security Fixes¶

• The build toolchain for the CLI and the standard and UOS Registry was upgraded to Go 1.27.3, fixing CVE-2026-111943 in crypto/x509 by refusing to trust the untrusted intermediate certificates listed in the advisory. Source builds require Go 1.27.3 or later.

1.6.0(2026/10/21)¶

New Features¶

• owl.event.resolve: resolves event details by event document ID, event or incident ID, or link.
• owl.account.workspace.same_org.list: new CLI tool entry to discover candidate workspaces for same-organization Trace queries.

Bug Fixes and Optimizations¶

• Unified parameter and time range validation across CLI, HTTP, and MCP, and hardened validation for infrastructure filter conditions, workspace pagination, and event details parameters. When owl exec -f json fails preflight checks, it now returns structured JSON and a non-zero exit code.
• owl sync now returns failure when any category download fails, retaining the existing cache and local version of the failed category. A failed first-time auto-sync blocks subsequent execution; auto-sync failures after cache expiry still warn and use the existing cache, as before.

Upgrade and Compatibility Notes¶

• After upgrading the CLI and Registry together, run owl sync so MCP clients rediscover the tools. owl.event.get continues to use the raw doc_id returned by the list; use owl.event.resolve for event IDs, incident IDs, or links.
• v1.6.0 uniformly validates 13-digit integer millisecond timestamps and requires the end time to be greater than the start time. Parameters that must be provided as a pair cannot be passed on one side only; required fields and maximum ranges follow each tool's schema. The maximum time range for owl.data.query is 7 days.
• The DQL in owl.data.query may omit the inline time window, allowing start_time/end_time to provide the query window. Inline absolute windows must match the external window; relative windows are rejected. PromQL range selectors represent the lookback duration, not the query window, and are not subject to DQL validation. The Registry requires an available dqlcheck; DQL queries are not executed when validation is unavailable. The request window is not equivalent to the time range actually executed by the backend or covered by results.

1.5.0(2026/10/14)¶

New OWL CLI Features¶

• The CLI now supports independent Profile management and account switching: use owl profile add/list/current/rename/remove to save and manage multiple full configurations, and owl switch, --profile, or OWL_PROFILE to select a configuration persistently or temporarily. Each named Profile stores its configuration, credentials, cache, data, and logs independently. (#21)
• The CLI now includes offline Bash and PowerShell completion that suggests commands, Profile aliases, categories, tool names, tool parameters, and schema enumeration values. Completion only reads the current Profile's local cache; it does not access the network or execute tools. (#24)

OWL CLI Bug Fixes and Optimizations¶

• Hardened Bash completion candidate matching; shell special characters, spaces, or URLs in the schema are treated as literal values. (#24)
• Fixed an issue where owl profile remove --purge could remove configuration and credentials before cleanup failed; after a failure, fix the permissions and retry. (#21)

OWL Registry and Public Tool Catalog¶

• Added owl.external_datasource.list and owl.external_datasource.query to discover external data sources accessible to the current workspace, and execute a single restricted read-only SQL using the datasource_uuid returned by the list. (#13)
• Registry logs now fully redact sensitive fields such as sql, rows, and nested arguments. (#13)
• owl.metric.list, owl.rum.list, owl.apm.list, owl.network.list, owl.profile.list, owl.logging.list, owl.billing.list, and owl.infrastructure.list/get now require 13-digit millisecond start_time and end_time values, with a maximum time window of 7 days. (#25)
• The time range for owl.llm.list remains optional; when both start_time and end_time are omitted, it queries the most recent 24 hours. (#25)
• The dql_namespace/namespace schemas of the DQL query tools now include the complete enumeration and common data type mappings; owl.data.show_dql_namespace provides the full type meanings and clarifies that its returned dql_namespace values still use the same-named field in owl.data.query, while in simple query and log clustering tools they should be passed as-is to namespace. Existing field names and request forwarding behavior remain unchanged.

Upgrade and Compatibility Notes¶

• When no Profile is selected, the original ${OWL_DIR}/config.yaml continues to be used; the root configuration remains default and is not migrated automatically. The CLI's --conf is deprecated; after importing configuration, use --profile instead. The Registry service's --config is not affected. (#21)
• Run owl sync after upgrading the Registry or the public catalog. Time ranges must be explicitly provided when calling the discovery and infrastructure tools above; owl.llm.list may continue to omit the time range. (#25)

1.4.0(2026/09/23)¶

New Features¶

• Added authorized cross-workspace data queries: discover authorized workspaces via owl.workspace.data_authorized.list, then pass workspace_uuids and target_region to the DQL tools. Queries in the current workspace do not require workspace discovery; same-organization cross-workspace Trace continues to use the dedicated tool.
• Added the workspace category, including the authorized workspace list and owl.workspace.member.list; the old name owl.member.list is retained as an invocation alias, and both CLI and MCP reuse the new tool's parameter and permission validation.
• Added owl.incident.get to fetch details by incident UUID along with paginated references to related events, then read event content via owl.event.get.

Bug Fixes and Optimizations¶

• Fixed the issue where historical testing-<SHA> builds could not be upgraded via owl update; both the Linux/macOS and Windows installers now support migrating to the official version of the current configured channel while preserving the existing configuration and SHA256 verification. Regular versions continue to only upgrade and never downgrade, skip installation for the same version, and still report errors for unrecognized versions. (#226)
• CLI and MCP now preserve the AIAPI error diagnostic fields and trace ID to help locate the causes of cross-workspace query failures.
• Parameter preflight now supports JSON Schema union types and preserves constraint validation for each type branch.
• Static MCP tools now include OpenAI metadata, and the issue with forwarding OAuth Bearer tokens upstream has been fixed.

Upgrade Requirements¶

• First confirm that the target site has deployed the matching AIAPI, including /api/v1/workspace/data_authorized/list, the cross-workspace query contract, and /api/v1/incident/get.
• Upgrade the CLI and Registry programs together, then run owl sync to fully refresh the catalog; MCP clients rediscover the tools. Older CLI versions do not support aliases, so syncing the catalog alone does not guarantee that old commands remain usable.
• The old member category has been removed; use owl.workspace.data_authorized.list for authorized workspace discovery. See Migration Notes for details.

1.3.0(2026/08/26)¶

This is a feature iteration release with the following updates:

New Features¶

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

Bug Fixes/Optimizations¶

• Unauthorized responses from the OAuth upstream are now preserved 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.
• The data query tools' timeout was adjusted to 130 seconds, and the Registry client's default timeout was adjusted to 150 seconds with configuration support.
• The Registry image now records version and revision information, and regression tests for the release process were added to improve the traceability of build artifacts.

Compatibility Adjustments¶

• Existing CLI commands and default configuration paths remain unchanged; --conf is a new entry point, and skipping TLS verification is disabled by default.
• MCP still exposes the facade tools by default; both site routing and the OpenAI Apps challenge are enabled only after explicit configuration.
• The incompletely designed Agent Protocol (including owl agent --stdio) is not included in this release.

1.2.1(2026/08/07)¶

This is a hotfix release with the following changes:

Bug Fixes¶

• Fixed the issue where result files generated by data-type tools had overly long IDs; new files now use 22-character URL-safe random IDs, reducing the risk of overly long file names and paths caused by long parameters, and making it easier for Agents to reference them in subsequent commands. (#8)
• Fixed the issue where owl.data.simple_query and owl.data.simple_query_file only validated the parameter schema but not the auto-generated DQL; they now construct the equivalent DQL before execution and call the Registry's DQL validation to intercept invalid query fragments early. (#7)

Enhancements¶

• When generated DQL validation fails for simple queries, structured generated_dql / dql.builderError issues are now returned so Agents can locate and fix parameters such as where_clause, select_clause, and group_by_clause. (#7)

Compatibility Adjustments¶

• The data file index format and the stable queryKey remain unchanged; existing indexes and result files can still be read. Only the IDs and file names of newly generated files are shorter. (#8)
• Valid simple query invocation methods and the remote execution path remain unchanged; only invalid DQL now fails earlier, before the request is sent. (#7)

1.2.0(2026/08/05)¶

This is a feature iteration release with the following updates:

New Features¶

• The CLI now includes owl validate, owl tool validate, and owl capabilities, which validate parameter schemas and tool-specific syntax without executing the target tool, and return structured results for Agents to assess 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 the current context, while cache and data files continue to use the shared paths in the configuration. (3da3e8e)
• Added same-organization workspace discovery, and data queries can now use same_org_workspace_uuids to query multiple workspaces in the same organization, which can be used for cross-workspace Trace retrieval. (71fa73e)
• owl exec now shows version update notifications: the CLI throttles new-version checks by update channel and notifies about upgrades through a notice field in the JSON output without affecting existing parsing. (7c7113c)
• The public tool catalog now includes mdsearch document retrieval and SLO list capabilities. (135c8ff, 18f87b0)
• The public tool catalog now includes Studio Notes V2 capabilities for listing, creating, modifying, and deleting notes. (a72af5f)
• The public tool catalog now includes data forwarding rule discovery and asynchronous query capabilities. (6c37c93, c6dcd80)
• The public tool catalog now includes a Dashboard list capability. (6c98f0b)
• Added an OSS automatic release pipeline targeting five platforms across Linux, macOS, and Windows; after the test channel passes validation, the same build artifact can be promoted to the production channel. (9fba8e2)

Bug Fixes¶

• Fixed the issue where the Registry lost the original status and error information when the upstream returned client errors for HTTP tools; the CLI now receives more accurate and actionable failure reasons. (e1267e0)
• Fixed the issue where large Dashboard results were still returned through the text path; the related tools now save results to data files to avoid large payloads consuming Agent context. (68cac16)
• Fixed the issue where data forwarding query results were still returned through the text path; query results are now written to data files. (30aa6fc)
• Fixed the issue where account information could be mixed up during workspace credential switching and display; configuration output now masks secrets by default and only shows the raw secret when explicitly requested. (3da3e8e)
• Streamable MCP sessions now complete authentication before being established; unauthorized requests do not create session state. (2a5d8e9)

Enhancements¶

• Unified the parameter parsing and preflight logic of owl exec and owl validate to support returning all parameter issues at once; before validation, the normal first-use or cache-expired auto-sync is executed, and 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, making it easier to locate issues across layers. (386abc0)
• Sensitive tokens in logs now keep only their first and last characters for correlation while the middle remains redacted, preventing full credentials from entering logs. (6a6d0ad)

Compatibility Adjustments¶

• Existing short commands such as list, show, exec, and schema, as well as the tool/tools namespaces, remain compatible; validate and capabilities are new entry points. (#6)
• Legacy token, auth.token, workspaces.<name>.token, and auth.token_file configurations can still be read; newly written credentials uniformly use api-key, and old configurations are not proactively deleted. (3da3e8e)
• The PromQL mode of owl.data.query is not passed to the DQL validator; existing valid queries and MCP tool invocation methods remain unchanged. (#6)

1.0.11(2026/05/25)¶

This is an iteration release with the following updates:

New Features¶

• Added the CLI-only tool owl.data.simple_query_file to the data category; after the CLI synchronizes the latest public tool catalog, it can call the existing simple query backend interface with simple query parameters and save results through the existing data file lifecycle.
• owl.data.simple_query_file and the MCP tool owl.data.simple_query remain separate exposure surfaces to prevent large results from being returned through the MCP text/context path.

Enhancements¶

• Added regression tests with a real public config, covering the CLI visibility of owl.data.simple_query_file, its MCP invisibility, outputType: data, authentication methods, and parameter schemas.

Compatibility Adjustments¶

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

1.0.10(2026/05/18)¶

This is a hotfix release with the following changes:

Bug Fixes¶

• Fixed the issue where the CLI could generate a double slash when joining the Registry API path if registry.endpoint was configured with a trailing slash, causing owl sync to return nginx 404.
• The Registry Client now normalizes the endpoint at construction time, 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 the category sync path with a trailing-slash endpoint to prevent future URL joining regressions.

Compatibility Adjustments¶

• The user configuration format is unchanged; existing endpoints without a trailing slash keep their original behavior, and endpoints with a trailing slash are also compatible.

1.0.9(2026/05/12)¶

This is an iteration release with the following updates:

New Features¶

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

Enhancements¶

• Updated the data category description and version to clarify 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 Adjustments¶

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

1.0.8(2026/05/07)¶

This is an iteration release with the following updates:

New Features¶

• Added owl.logging.list and owl.billing.list to the data category discovery chain; after the CLI synchronizes the latest public tool catalog, it can directly discover source/field for logs and cloud billing.
• owl.metric.list now supports mode=tag to discover metric tag keys, and supports filtering field or tag results by source.
• Data result file names now keep a readable prefix and append a UUID to prevent overwriting same-named files during repeated queries or concurrent multi-session usage.
• The data file index now includes a stable queryKey to identify the same query while maintaining compatibility with the legacy index.json.

Bug Fixes¶

• Fixed the issue where discovery tool schemas did not declare the source parameter, causing owl exec ... --source ... to be rejected by local parameter validation.
• Fixed the issue where the outer layer of the Registry REST and MCP HTTP tools could still report success when the AIAPI discovery list returned a success:false business error.
• Fixed the issue where, after specifying a custom Owl directory via the installer's --owl-dir/-OwlDir, running owl config show later could still fall back to the default configuration directory.

Enhancements¶

• Updated the data discovery examples in the README and usage documentation, adding invocation methods for mode=field, mode=tag, owl.logging.list, and owl.billing.list.
• Adjusted the public catalog sync message to avoid outputting the easily misinterpreted Scope: public catalog when the public catalog is hit.
• owl data clean cleans files older than 1 day by default; --days 0 or negative values are treated as 1 day.
• owl data clean only cleans expired files registered in the index; unregistered orphan files keep their original behavior and are not actively scanned or deleted.
• The Linux/macOS and Windows installers now record the .owldir path next to the installation target and clean up old records when a custom directory is not used or on uninstall, allowing the CLI to continue locating custom configuration, cache, and data directories without the OWL_DIR environment variable.
• Added regression tests for discovery schemas and business errors in the loader, executor, Registry REST, and MCP.
• Added regression tests for CLI configuration parsing and installer custom directories, covering .owldir record reading, config show path display, and post-install directory locations.

Compatibility Adjustments¶

• The 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 applies only to owl.metric.list.

1.0.7(2026/04/29)¶

This is an iteration release with the following updates:

New Features¶

• The CLI now has a tool namespace while retaining the tools alias; this entry point serves as an auxiliary form alongside top-level commands such as list, show, exec, and schema, improving tolerance when Agents guess command forms.
• The category command now has a categories alias, making it easier for Agents to discover category capabilities by naturally guessing command forms.

Bug Fixes¶

• Fixed the issue where help topics such as owl help tool and owl help categories could not be resolved.
• Fixed the issue where some --help calls prematurely triggered configuration initialization or Registry dependencies; help commands now return directly in unconfigured environments.

Enhancements¶

• Added regression tests for help topics, confirming that querying help by topic (such as owl help tool) and viewing help by command (such as owl tool --help) return consistent information.
• Adjusted the tool-viewing command examples in the README, adding the tool namespace usage.

Compatibility Adjustments¶

• Existing top-level commands such as list, show, exec, and schema remain the primary usage and stay compatible to avoid breaking existing scripts.
• Removed some sample tools and Skill configurations that are no longer published.

1.0.6(2026/04/28)¶

This is an iteration release with the following updates:

New Features¶

• Added the owl update command, which downloads and executes the installation script for the corresponding platform based on the update channel recorded by the installer.
• The Linux/macOS installation script now supports --upgrade, and the Windows installation script now supports -Upgrade, to upgrade the local CLI only when the remote version is newer.
• The installer now writes update.base_url and update.channel into the configuration to provide the update source for subsequent owl update commands.

Bug Fixes¶

• Fixed the issue where the existing installation path could not be reliably located during upgrades; the upgrade flow now reads binpath in the Owl directory first, then falls back to owl in PATH.
• Fixed the issue where the installation could still be overwritten 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, reading the local owl --version and the remote channel version for comparison before upgrading.
• The update flow runs 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 is a hotfix release with the following changes:

Bug Fixes¶

• Fixed the issue where the Linux/macOS installer reported bad substitution when running checksum comparisons under the system Bash 3.2 on macOS.
• Replaced the Bash 4 syntax ${var,,} with tr '[:upper:]' '[:lower:]', which is available in the POSIX toolchain, ensuring the checksum case-normalization logic is compatible with older Bash.

Enhancements¶

• Rebuilt the CLI packages for the 5 platforms so the release directory version, manifest version, and the owl --version output within the packages remain consistent.
• Kept both skill.md and skill.en.md Skill documents to continue supporting Chinese and English Agent Skill distribution.

1.0.4(2026/04/27)¶

This is an installer channel release with the following updates:

New Features¶

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

Bug Fixes¶

• Fixed the issue where the previous production channel installation script lacked OWL_DIR/OwlDir support.
• Avoided directly overwriting the same-version release when the existing 1.0.3 channel was affected by the sync cache; a new channel directory now hosts the corrected installation entry.

1.0.3(2026/04/27)¶

This is an iteration release with the following updates:

New Features¶

• The installer now supports OWL_TEMP_CODE, deriving the ai-api address from OWL_REGISTRY_ENDPOINT and exchanging it for a real token via /api/v1/account/accesskey/exchange.
• Added skill.md to provide channel-distributed Skill documentation for Agent integration scenarios.

Bug Fixes¶

• Fixed the issue where reading BASH_SOURCE[0] could fail under the bash -c "$(curl .../install.sh)" entry point, changing to script entry parsing with a $0 fallback.
• Fixed unexpected newline formatting 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 verifies that OWL_TOKEN matches the exchange result and aborts the installation if they do not match.
• OWL_TEMP_CODE requests bypass the local proxy by default, reducing the chance that temporary credential exchange is affected by proxy configuration.

1.0.2(2026/04/24)¶

This is an iteration release with the following updates:

New Features¶

• The CLI and installer now support a custom Owl working directory: added OWL_DIR, --owl-dir, and -OwlDir.
• The installer now supports OWL_OWNER/--owl-owner to hand the configuration directory to the service user after cloud-init or root installation.
• After installation, the binary path is recorded to binpath in the Owl directory for later upgrades and Agent runtime location.

Bug Fixes¶

• Fixed the issue where the installer always wrote registry.endpoint and auth.token to the current user's directory when persisting them; they are now written to the specified Owl directory.
• Fixed the issue where config show displayed an inaccurate directory in custom-directory scenarios.

Enhancements¶

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

1.0.1(2026/04/23)¶

This is a hotfix release with the following changes:

New Features¶

• The CLI now auto-syncs on first use: when the local cache is empty or older than registry.sync_interval, commands such as list, show, exec, schema, and category automatically trigger owl sync.
• Added the sync.auto configuration option to allow disabling automatic sync.

Bug Fixes¶

• Fixed the issue where the owl binary in the 1.0.0 Linux/macOS tar packages lacked the executable permission.
• Fixed the issue where owl sync incremental sync did not remove cached categories that were deleted remotely.
• Fixed the issue where the installation script could exit early due to set -u in some cloud-init/systemd/container environments without HOME.

Enhancements¶

• Auto-sync failures now distinguish between first sync and cache refresh: a failed first sync returns an error, while a failed refresh of existing cache keeps the old cache and outputs a warning.
• The release directory restored and now tracks the 1.0.0 and 1.0.1 channel artifacts, with installer regression tests and CRLF/LF auditing added.

1.0.0(2026/04/13)¶

This is the initial release with the following updates:

New Features¶

• Released the first channel version of the Owl CLI, providing 5 platform packages across Linux, macOS, and Windows.
• Provides install.sh, install.ps1, owl-install.ps1, and SHA256SUMS, supporting remote channel installation, specified-version installation, local package installation, and checksum verification.
• The CLI supports configuration initialization, login token writing, tool catalog sync, category listing, tool listing, tool execution, OpenAI function schema output, cache management, and data file management.

Enhancements¶

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

Known Issues¶

• The owl binary in the Linux/macOS tar packages has 0644 permissions and is not executable after direct extraction; this issue was fixed in 1.0.1.