> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/release-notes/jp/developer-tools/commander/older/commander-v16.9.25.md).

# コマンダー 16.9.25

GitHubでリリースを確認: <https://github.com/Keeper-Security/Commander/releases/tag/v16.9.25>

{% hint style="info" %}
Commander v16.9.22～v16.9.24はスキップされました
{% endhint %}

## 新機能

* [`find-ownerless`](/keeperpam/jp/commander-cli/command-reference/record-commands.md#find-ownerless)\
  ボルト内で所有者が設定されていないレコードをすべて検出します。
  * スイッチ`--claim`を指定すると、検出したレコードの所有権を取得できます。

## 向上点

* ログイン時のセキュリティデータ更新処理を最適化しました。
* [`user-report`](/keeperpam/jp/commander-cli/command-reference/reporting-commands.md#user-report-command)\
  レポート対象のユーザー一覧を管理対象ノードに限定し、「last\_login」フィールドに範囲外や「n/a」の表示を追加しました。
* [`list`](/keeperpam/jp/commander-cli/command-reference/record-commands.md#list-command)\
  レコードタイプによる絞り込みで「general」フィルタに対応しました。

## バグ修正

* [share-report](/keeperpam/jp/commander-cli/command-reference/reporting-commands.md#share-report-command)\
  所有者のいないレコードの所有者値に関する不具合を修正。
* その他軽微なバグ修正および改善。


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.keeper.io/release-notes/jp/developer-tools/commander/older/commander-v16.9.25.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.