Cloud animation for Cloud Agent subagent

[roman-commits-code]

Linked issue

Closes #0

What does this PR do?

Adds a unique inline animation for the Cloud Agent (Remote-Runner) subagent type, replacing the generic braille spinner it shared with all other agents. The Cloud Agent now shows a cloud glyph (☁) with a loading arc (◜◝◞◟) tracing around it, completing in a full circle before restarting — visually distinguishing remote execution from local agents at a glance.

The animation works across all three TUI rendering surfaces:

• Agent widget (persistent panel above the editor)
• Inline tool-call block (foreground agent progress)
• get_subagent_result icon (queued/running status)

Other agent types are unaffected — they continue to use the standard braille spinner.

Checklist

• I have read CONTRIBUTING.md and agree to the CLA
• This PR links to an open issue above
• Tests pass locally (pnpm run test)
• Lint passes (pnpm run check)
• Documentation updated if behavior changed

[readme-ai-writer]

📚 No documentation changes were needed for this PR.

[kimchi-review]

Kimchi Code Review

Property	Value
Commit	32ad059
Author	@roman-commits-code
Files changed	0
Review status	Completed
Comments	2 (2 warning)
Duration	31s

Summary

📊 Review Score: 78/100 (overall code quality — 0 lowest, 100 highest)
⏱️ Estimated effort to review: 2/5 (1 = trivial, 5 = very complex)

🧪 Tests: no — No test files were added or modified in the diff. The change is mostly visual (animation frames and widget rendering), but there are no unit tests for getAgentSpinnerFrames, frame indexing, or the optional subagentType propagation paths.

📝 Found 2 issue(s). See inline comments for details.

What to expect

Kimchi will analyze the changes in this pull request and post:

• A summary of the overall changes
• Inline comments on specific lines with findings categorized by issue type

The review typically completes within a few minutes. This comment will be updated once the review is ready.

Interact with Kimchi

• @getkimchi review — re-trigger a full review on the latest commit
• @getkimchi summary — regenerate the PR summary
• @getkimchi ignore — skip this PR (no review will be posted)
• Reply to any inline comment to ask follow-up questions or request clarification

Configuration

Reviews are configured by your organization admin.
Review instructions, excluded directories, and severity thresholds can be adjusted per repository in the Kimchi dashboard.

---

Powered by Kimchi — AI-powered code review by CAST AI

[kimchi-review]

📊 Review Score: 78/100 (overall code quality — 0 lowest, 100 highest)
⏱️ Estimated effort to review: 2/5 (1 = trivial, 5 = very complex)

🧪 Tests: no — No test files were added or modified in the diff. The change is mostly visual (animation frames and widget rendering), but there are no unit tests for getAgentSpinnerFrames, frame indexing, or the optional subagentType propagation paths.

📝 Found 2 issue(s). See inline comments for details.

[kimchi-review]

⚠️🔧 Maintainability

getAgentSpinnerFrames(details.subagentType) is called with a value that may be undefined, because GetSubagentResultDetails.subagentType is declared as optional (subagentType?: string) while getAgentSpinnerFrames requires a non-optional string. Although the function happens to fall back to SPINNER when the type does not match, relying on this is brittle and may break under stricter TypeScript settings or future refactors. It is also inconsistent with getSubagentResultIcon, which explicitly guards the call with subagentType ? getAgentSpinnerFrames(subagentType) : SPINNER.

💡 Suggestion: Change getAgentSpinnerFrames in src/extensions/agents/ui/agent-widget.ts to accept type: string | undefined (returning SPINNER for undefined), or guard the call here: const frames = details.subagentType ? getAgentSpinnerFrames(details.subagentType) : SPINNER.

[soundvibe]

this comment makes sense, it would be better to handle this possible null case in getAgentSpinnerFrames itself.