Tauri Command Reference

This page documents the current command surface registered in src-tauri/src/lib.rs and consumed by the React frontend.

Naming and Payload Conventions

• Rust command names use snake_case.
• Frontend invoke calls use the same command names.
• Argument key casing depends on the command signature:
  • direct function arguments typically use Rust-style names
  • request structs can opt into camelCase via serde attributes (for example SpawnAgentRequest)

Command Groups

Agents (commands/agent.rs)

• spawn_agent
• list_agents
• list_agent_metrics
• kill_agent
• pause_agent
• resume_agent
• clear_agent_session
• rename_agent
• reorder_agents
• update_agent_config
• enable_agent_worktree
• list_agent_worktrees
• assign_agent_worktree
• delete_agent_worktree
• disable_agent_worktree

Worktree commands update agent config only. UI callers that move an agent between the source checkout and a worktree must follow the config command with clear_agent_session so the provider starts fresh in the new workspace instead of resuming across a cwd change. enable_agent_worktree accepts an optional worktree_name. Wardian uses the provided name, or the agent session name when it is omitted, for the wardian/<slug> branch and the project-sibling <source-checkout>.wt/<slug> folder. list_agent_worktrees includes external Git worktrees for known source workspaces and marks only unassigned Wardian-managed worktrees as deletable. delete_agent_worktree removes only unassigned Git-registered worktrees under Wardian-managed roots, including legacy <wardian-home>/agents/<session-id>/worktrees/ paths, cleans Wardian-generated build-cache redirects, and uses non-force Git removal; it does not remove assigned worktrees, source checkouts, or external worktree paths.

The live control protocol exposes CLI wrappers for the same worktree operations: agent_worktree_list, agent_worktree_enable, agent_worktree_join, and agent_worktree_disable. Unlike the raw Tauri worktree commands, the control mutation handlers call clear_agent_session after moving an agent workspace so CLI behavior matches the GUI flow.

Terminal (commands/terminal.rs)

• send_input_to_agent
• submit_prompt_to_agent
• send_binary_input_to_agent
• inject_session_input
• broadcast_input
• resize_agent_terminal
• read_agent_pty

send_input_to_agent and send_binary_input_to_agent are raw PTY input paths for terminal interaction. They must not be used as the source of truth for structured agent-to-agent communication.

submit_prompt_to_agent is the structured prompt submission command for live agents. It returns a DeliveryDetail and routes through the same backend live-surface delivery service used by CLI sends, command panel sends, remote prompt sends, workflow live routing, and mailbox drain. It must not be replaced with raw send_input_to_agent calls for prompt injection. Fixed sleeps before injection are not a correctness mechanism; delivery should wait for readiness evidence or queue the interaction.

read_agent_pty drains buffered terminal output after agent-pty-output-ready. It is display data and compatibility evidence only. Structured ask/reply completion, Queue evidence, and provider status transitions must not depend on replaying this text.

Classes (commands/class.rs)

• list_agent_classes
• create_agent_class
• delete_agent_class
• get_default_class_instruction
• reset_class_to_default
• reset_all_class_prompts

Watchlists (commands/watchlist.rs)

• load_watchlists
• save_watchlists
• load_queue_items
• save_queue_items
• load_queue_preferences
• save_queue_preferences
• load_agent_interactions
• save_agent_interactions

The CLI team and watchlist commands read and write watchlists/index.json directly. They normalize the current v2 state shape and legacy flat watchlist arrays for reads, write canonical v2 JSON for mutations, and best-effort notify the running app when the local control endpoint is available. Team create/add/split operations also seed communication-topology edges while preserving existing seed-suppression tombstones.

Queue commands persist the frontend Queue projection and preferences for the active Wardian home. Queue items should carry stable evidence_id and evidence_source fields when they are derived from provider runtime events, interaction-store events, or other live runtime evidence. Startup hydration may restore these items, but it must not create new completion or action-needed evidence.

load_agent_interactions and save_agent_interactions preserve the existing lightweight graph interaction projection. They are separate from the backend interaction control plane records used by structured ask and reply.

Filesystem and Explorer (commands/fs.rs)

• resolve_system_include_directories
• validate_directory_path
• get_explorer_root
• get_directory_tree
• delete_file
• reveal_in_explorer
• read_file_preview

Workflows (commands/workflow.rs)

Current workflow commands:

• workflow_parse
• workflow_validate
• workflow_write
• workflow_list_blueprints
• workflow_list_runs
• workflow_read_run
• workflow_run
• workflow_resume
• workflow_approve
• workflow_cancel
• schedule_create
• schedule_list
• schedule_pause
• schedule_resume
• schedule_remove
• schedule_run_now

Old workflow system command names such as run_workflow, list_workflows, list_scheduled_runs, and create_scheduled_run belong to the retired JSON workflow system. Do not add new frontend behavior against those names.

Library (commands/library.rs)

• get_library_tree
• save_library_item
• update_library_metadata
• open_library_folder
• deploy_skill
• remove_deployed_skill
• list_deployed_skills
• list_deployed_skill_refs
• list_skill_deployments
• library_watch
• library_unwatch

Settings and Patch (commands/settings.rs, commands/patch.rs)

• run_gemini_patch
• list_available_shells
• get_settings_folder_path
• load_shell_settings returns resolved shell settings plus sparse user overrides.
• save_shell_settings accepts the versioned shell settings document and persists sparse overrides.
• load_app_settings returns resolved app settings plus sparse user overrides.
• save_app_settings accepts the versioned app settings document and persists sparse overrides.
• save_agent_session_persistence
• save_opencode_theme

Remote Access (commands/remote.rs)

• load_remote_access_status
• load_remote_gateway_config
• save_remote_gateway_config
• create_remote_pairing_offer
• list_remote_devices
• list_pending_remote_pairing_requests
• load_remote_setup_check
• approve_remote_pairing_request
• reject_remote_pairing_request
• revoke_remote_device

Debug builds also register debug_create_remote_session for native gateway tests. It is not registered in release builds.

Git (commands/git.rs)

• git_status
• git_init
• git_clone_repository
• git_current_branch
• git_log
• git_commit_changes
• git_diff_file
• git_diff_file_against_workspace
• git_show_file_revision
• git_stage
• git_unstage
• git_discard_changes
• git_ignore
• git_commit
• git_commit_signed
• git_commit_staged_signed
• git_commit_all_signed
• git_commit_signed_no_verify
• git_commit_staged_signed_no_verify
• git_commit_all_signed_no_verify
• git_commit_no_verify
• git_commit_staged_no_verify
• git_commit_all_no_verify
• git_commit_empty
• git_commit_empty_no_verify
• git_commit_amend
• git_commit_amend_no_verify
• git_commit_staged_amend_no_verify
• git_commit_all_amend_no_verify
• git_commit_staged_amend
• git_commit_all_amend
• git_undo_last_commit
• git_rebase_abort
• git_pull
• git_list_branches
• git_checkout_branch
• git_create_branch
• git_stash_push
• git_list_stashes
• git_show_stash
• git_stash_staged
• git_stash_apply_latest
• git_stash_apply
• git_stash_pop_latest
• git_stash_pop
• git_stash_drop
• git_stash_drop_all
• git_fetch
• git_push
• git_create_worktree
• git_remove_worktree
• git_watch
• git_unwatch

Event Surface (Backend -> Frontend)

Common app-level events:

• agent-metrics
• agent-json-event
• agent-pty-output-ready
• agent-terminal-cleared
• agents-updated
• workflow-telemetry
• workflow-progress
• workflow-status-updated
• scheduled-runs-updated
• git-changed
• library-changed with payload { "library_type": "skills" }

For payload semantics, see IPC and Event Governance and the workflow engine docs.

Live Control Protocol

The standalone wardian CLI primarily talks to the desktop app through Wardian's live control endpoint rather than Tauri invoke. These command contracts share DTOs with crates/wardian-core/src/control.rs:

• send_message
• ask
• submit_reply
• agent_watch

send_message routes provider-aware delivery to one or more targets. Delivery responses contain runtime_state, delivery_state, input_mode, optional message_id, delivery_phase, observed_state, reason, profile, and provider-specific error details. When the target runtime is not ready for live input, the command should queue the message in the mailbox or fail according to its queue policy instead of injecting text early. This slice does not create durable message interactions for ordinary send calls; structured durability belongs to ask and reply.

ask creates a task interaction with reply_required, delivers the prompt plus reply instructions, and waits for the parent task to reach a terminal structured state. It returns the attached structured reply when complete. Output-marker waiting remains a compatibility mode, but it is not the structured ask/reply completion path.

submit_reply resolves the request ID against the interaction store, creates or attaches a reply interaction, and completes the parent task. Unknown request IDs fail deterministically. Duplicate replies must be rejected or handled by an explicit idempotency policy. When origin contains a Wardian agent session ID, the backend verifies that the sender is the task target.

agent_watch returns ordered status, transcript, output, and delivery evidence from watch state. delivery snapshots are derived from delivery watch events. Raw PTY output is opt-in and should be used only for terminal rendering or transport debugging.

Provider input readiness is tracked separately from provider install readiness. Live delivery gates on per-session provider input state:

{
  "session_id": "uuid-1",
  "generation": 7,
  "state": "ready",
  "ready_evidence": "prompt_detected",
  "observed_at": "2026-05-25T16:00:00.000Z"
}

Provider runtime status remains authoritative for provider-internal states such as action_required. Interaction status tracks Wardian-owned delivery and reply lifecycle only.

Change Management Guidance

When adding or changing commands:

1. Register/unregister in src-tauri/src/lib.rs.
2. Update frontend invoke callsites.
3. Update this reference page.
4. Update user or developer guides impacted by behavior changes.