跳转到内容
xcsh
Security
Networking
Platform
AI
Demo Resources
Resources
搜索
Ctrl
K
取消
GitHub
选择主题
深色
浅色
自动
选择语言
English
Français
Español
Deutsch
Português (Brasil)
日本語
한국어
简体中文
繁體中文
العربية
Italiano
हिन्दी
ไทย
Architecture and contribution
概述
Agent loop and sessions
Storage and artifacts
Tool runtime
Provider streaming
Extension discovery
Native runtime
Native development
TUI runtime
Relationship to pi
TUI interaction style
Prompt authoring
Build and release xcsh
File-test parallelism qualification
Automate and extend
概述
Headless modes
Embed xcsh with the SDK
Extensions and tools
Hooks and rules
Create and load skills
Plugins and marketplaces
MCP configuration
MCP runtime
Configure and secure
概述
Settings precedence
Environment variables
Providers and models
Resolve secrets safely
Sandbox boundaries
F5 Distributed Cloud
概述
Contexts and namespaces
Write resource manifests
Validate and diff
Create and update
Get, export, delete
API catalog
Getting started
概述
Model authentication
First manifest
Integrations and deployment
概述
VS Code
Office task pane
Chrome
Containers
Herdr
Reference and troubleshooting
概述
CLI reference
Slash command reference
Configuration schema
Run diagnostics
Use xcsh
概述
How xcsh works
Terminal CLI
Use the interactive TUI
Use built-in tools
Sessions and memory
Plan complex work
TUI navigation
概述
GitHub
选择主题
深色
浅色
自动
选择语言
English
Français
Español
Deutsch
Português (Brasil)
日本語
한국어
简体中文
繁體中文
العربية
Italiano
हिन्दी
ไทย
Architecture and contribution
此内容尚不支持你的语言。
Use these pages when changing xcsh itself rather than operating it.
Which implementation boundary matters?
Section titled “Which implementation boundary matters?”
Agent loop and sessions
Storage, blobs, and artifacts
Tool runtime
Provider streaming
Extension discovery
Native runtime
Native development
Terminal user interface (TUI) runtime
Relationship to upstream pi
Prompt authoring
Build, test, contribute, and release
File-test parallelism qualification