Update AgentPhone logo and bgColor

[modi2meet]

Summary

• Replace old green phone icon SVG with current AgentPhone logomark (robot mascot)
• Update block bgColor from gradient to #000000

Test plan

• Verify AgentPhone icon renders correctly in the block palette
• Verify block card displays with black background

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		May 27, 2026 5:10am

[cursor]

PR Summary

Low Risk
Visual-only changes to an icon component and block bgColor; no API or workflow logic touched.

Overview
Refreshes AgentPhone branding in the workflow builder: the block card background switches from a dark green gradient to solid #000000, and AgentPhoneIcon is replaced with the current logomark (robot mascot) using a larger viewBox and white/#171717 artwork instead of the old green phone SVG.

Any surface that imports AgentPhoneIcon from icons.tsx (e.g. block palette, integrations icon map) picks up the new mark automatically; integration JSON metadata outside this diff may still list the old gradient until regenerated separately.

^{Reviewed by Cursor Bugbot for commit fdf4687. Bugbot is set up for automated code reviews on this repo. Configure here.}

[greptile-apps]

Greptile Summary

This PR updates the AgentPhone block's visual identity: the old green phone SVG icon is replaced with the current AgentPhone robot mascot logomark, and the block's bgColor is simplified from a dark gradient to solid #000000.

• The new AgentPhoneIcon SVG (viewBox=\"0 0 236 240\") uses white fills with fillRule=\"evenodd\" compound paths and near-black (#171717) fills for inner features, designed to render against the new black block background.
• bgColor in agentphone.ts is changed from 'linear-gradient(135deg, #1a1a1a 0%, #0a2a14 100%)' to '#000000', which pairs correctly with the white-on-black mascot design.

Confidence Score: 5/5

This is a pure visual/branding update with no logic changes — safe to merge.

Both changes are cosmetic: the SVG replacement is a brand asset swap and the bgColor change is a one-line simplification from gradient to solid black. No logic, API contracts, or data flow are affected.

No files require special attention.

Important Files Changed

Filename	Overview
apps/sim/blocks/blocks/agentphone.ts	bgColor changed from CSS gradient string to solid #000000, aligning with the new black-background brand asset
apps/sim/components/icons.tsx	AgentPhoneIcon SVG replaced from old green phone icon (viewBox 150×150) to new robot mascot logo (viewBox 236×240) with white/near-black fills on transparent background

_{Reviews (1): Last reviewed commit: "Update AgentPhone logo and block backgro..." | Re-trigger Greptile}

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
29606901	Triggered	Generic High Entropy Secret	a54dcbe	apps/sim/providers/utils.test.ts	View secret
32763747	Triggered	Generic Password	3e9849b	helm/sim/tests/validators_test.yaml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}