feat(mothership): add secrets input in chat

[Sg312]

Summary

Add secrets input in chat

Type of Change

• New feature

Testing

Manual

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

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

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Jun 30, 2026 1:01am

[greptile-apps]

Greptile Summary

This PR adds inline secret entry support to chat messages. The main changes are:

• A new secret_input credential tag type.
• Validation for secret input name and optional scope.
• A chat-rendered SecretInput widget that saves to personal or workspace environments.
• Permission gating for secret inputs and credential connect links.

Confidence Score: 4/5

The chat secret save path needs fixes before merging.

• Chat-entered credentials default to workspace storage when scope is omitted.
• Personal secret saves can overwrite newer keys because they send a full map from cached state.
• Credential connect links may disappear for read-only users when the target flow is personal.

apps/sim/app/workspace/[workspaceId]/home/components/message-content/components/special-tags/special-tags.tsx

Security Review

The new chat secret input can save a manually pasted credential to the shared workspace environment by default. User-provided API keys should stay user-only unless a trusted server path explicitly opts into workspace scope.

Important Files Changed

Filename	Overview
apps/sim/app/workspace/[workspaceId]/home/components/message-content/components/special-tags/special-tags.tsx	Adds parsing and rendering for chat secret inputs, with new environment-save behavior and permission gates.

_{Reviews (1): Last reviewed commit: "improvement(secrets): special tags impro..." | Re-trigger Greptile}

[greptile-apps]

Chat Secrets Default Shared

When a chat secret_input tag omits scope, this defaults the pasted credential to workspace and saves it through the shared workspace environment path. A user-provided API key entered in chat can therefore become a workspace secret instead of a user-only credential, exposing the key name and making the secret available to workspace-scoped flows.

Rule Used: API keys and other user-provided credentials shoul... (source)

Learned From
simstudioai/sim#2133