MigraQ Tencent Cloud Migration Service Expert

Problem

When migration consulting and migration execution are handled in the same interface, a local skill can easily cross boundaries: guessing prices or specs, or triggering cloud-resource writes before authorization is ready. MigraQ separates the workflow: pre-sales analysis is routed to a remote Tencent Cloud migration expert agent, while resource-changing operations enter the authenticated path only when needed.

How It Works

• Local layer handles meta-intents only: help, cancellation, --clear-session, and post-processing the previous remote answer such as shortening, translation, or format changes.
• Default to unauthenticated forwarding: resource scans, sizing recommendations, TCO analysis, migration plan consultation, and other non-execution questions use the unauthenticated migrateq_sse_api.py channel.
• Authentication is limited to write operations: migration execution, cluster creation or destruction, CVM/COS resource changes, and similar actions require TENCENTCLOUD_SECRET_ID and TENCENTCLOUD_SECRET_KEY.
• Forward the original wording: the question payload preserves the user's exact wording, without rewriting or translating, and may append context only after the original text.
• Reuse session state: the same conversation continues with the returned session_id, shared by unauthenticated and authenticated calls.
• Fail with actionable guidance: AuthError is not retried, while NetworkError, HTTPError, and StreamError can be retried, and the user is guided to check check_env.py or provide source cloud, scale, and requirements.

Boundaries

It is not a local migration knowledge base and does not promise concrete prices, specs, or compatibility numbers. Use unauthenticated routing for consulting, analysis, and planning; use AK/SK authentication only when creating, modifying, deleting, or executing migration tasks on Tencent Cloud resources.