AI agent
Agent tool calls
Read the actual runtime tool names, availability signals, inputs, outputs, errors, and changed-file results shown in the Agent timeline.
Updated
By Kition Docs
Verified against Kition 0.1.41 (d3e1b931) on 2026-08-29
Availability is decided per turn
The runtime can report available_tools plus separate availability for hosted web search and browser search. The list depends on the active pane, configured provider, selected model, runtime capabilities, and task context.
A tool name appearing in the UI code does not guarantee that the current turn can call it. Use the timeline and capability reason instead of relying on a static universal tool catalog.
Tool names recognized by the 0.1.41 client
- Documents —
document_search,document_read,document_write,create_markdown - Workspace files —
file_search,fs_read,fs_stat,fs_list,fs_mkdir,fs_remove,fs_copy,apply_patch - Tables —
data_table_create,data_table_schema,data_table_records,data_table_record_draft,data_table_add_fields,data_table_add_records - Web and browser —
web_search,web_fetch,browser_open,browser_navigate,browser_search,browser_context_entities,browser_ingest_strategy - Images and artifacts —
image_search,save_image_asset,artifact_write,register_artifact - Shell —
shell_execor the compatibility nameexec_command - MCP — qualified names are rendered as
server__tool
What the timeline shows
- Running, completed, and failed tool status
- Tool arguments and returned data when available
- Friendly labels for known tool names and raw names for unknown tools
- Saved artifacts and paths modified by document or patch tools
- Model reconnect progress for supported transient failures
- Additional backend detail when desktop debug mode is enabled
Tool-loop controls that exist
The user can stop the active stream. A shell command blocked by execution policy can present Allow once, an optional remembered prefix, or Deny. Some table plans require an explicit Apply action.
Kition 0.1.41 does not expose general Retry tool, Edit arguments, Skip tool, or tool-concurrency controls in the Agent timeline. Correct a failed step with a new message or stop and start a new turn.
Treat output as evidence, not proof
A completed tool card means the runtime reported completion. Verify durable changes in the document, table, filesystem, browser, or external system before reporting the task as done.
Stopping a turn does not undo a file write, table mutation, external request, or command that already finished.
Implementation sources
Related pages
Agent chat basics
Open a workspace-scoped chat, attach only the context you need, choose a model, and review the streamed work.
Agent approvals and safety boundaries
Use the shell-command approval card and feature-specific previews without assuming Kition 0.1.41 has a universal per-tool permission editor.
Browser context for the Agent
Open pages in Kition’s embedded desktop browser, sign in manually, and let the Agent read supported page context without promising full browser automation.
