Problem statement
Users who already use local agent tools such as Claude Code or Codex may already have API providers, base URLs, model names, and API keys configured locally.
When they first set up TouchAI, they need to re-enter similar provider settings manually. This adds friction for users who are already comfortable with daily agent workflows and makes onboarding feel repetitive.
Proposed solution
Add an onboarding or settings flow that can detect existing local Claude Code / Codex configuration and offer to import compatible API provider settings into TouchAI.
Expected behavior:
- Detect whether supported Claude Code or Codex configuration files exist locally.
- Offer an explicit import action during first-run onboarding, or from Settings.
- Preview the providers that will be imported before saving.
- Mask sensitive values such as API keys in the preview.
- Import only compatible API/provider fields, such as provider name, base URL, model name, and API key value or reference where safe.
- Never modify the original Claude Code or Codex configuration.
- Let users skip the flow and configure TouchAI manually.
- Handle missing, unsupported, or partially readable configs gracefully.
Initial scope should be limited to API/provider settings. Importing MCP servers, custom instructions, tool settings, or agent runtime behavior should be discussed separately because those may cross RFC-first boundaries.
Alternatives considered
- Keep manual setup only. This is simpler, but adds friction for users who already have working local agent configurations.
- Provide documentation for manually copying settings. This helps, but still requires users to find and translate config fields themselves.
- Support only one source first, such as Claude Code or Codex, then expand after the import flow is validated.
Main area
tauri
Risk boundaries
No AgentService, conversation runtime, tool execution, instruction loading, session persistence, context construction, MCP integration, database schema, or migration changes are intended for this issue.
Mockups, screenshots, or examples
Example onboarding copy:
Import settings from existing agent tools
TouchAI found local Claude Code / Codex configuration. You can review compatible API provider settings before importing them, or skip this step and configure TouchAI manually.
[Review import] [Skip]
Source discussion: raised from a product discussion with @hiqiancheng.
Problem statement
Users who already use local agent tools such as Claude Code or Codex may already have API providers, base URLs, model names, and API keys configured locally.
When they first set up TouchAI, they need to re-enter similar provider settings manually. This adds friction for users who are already comfortable with daily agent workflows and makes onboarding feel repetitive.
Proposed solution
Add an onboarding or settings flow that can detect existing local Claude Code / Codex configuration and offer to import compatible API provider settings into TouchAI.
Expected behavior:
Initial scope should be limited to API/provider settings. Importing MCP servers, custom instructions, tool settings, or agent runtime behavior should be discussed separately because those may cross RFC-first boundaries.
Alternatives considered
Main area
tauri
Risk boundaries
No AgentService, conversation runtime, tool execution, instruction loading, session persistence, context construction, MCP integration, database schema, or migration changes are intended for this issue.
Mockups, screenshots, or examples
Example onboarding copy:
Source discussion: raised from a product discussion with @hiqiancheng.