fix(mothership): billing for mcps, hosted key tools

[icecrasher321]

Summary

Correctly bill for MCP executions + hosted key tools in the mothership.

Type of Change

• Bug fix

Testing

Tested manually

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		Jul 17, 2026 7:47pm

[cursor]

PR Summary

Medium Risk
Touches billing attribution and dual billing paths (ledger vs Go service cost); incorrect flags could under- or over-charge, though workflow double-billing is explicitly guarded.

Overview
Fixes missing charges when Mothership/copilot runs MCP tools and hosted-key integrations that bypass the workflow execution ledger.

The copilot tool executor now copies billingAttribution into _context for dynamic app/MCP tool calls (when present), so internal routes can send the billing-attribution header and MCP execution can require attribution. llm_chat forwards workspaceId from _context in the /api/providers body so that header validates correctly.

For hosted-key tool spend, applyHostedKeyCostToResult still sets output.cost, but also adds top-level _serviceCost when copilotToolExecution is true so Go’s per-round extractServiceCost path can bill—matching media tools. Workflow runs omit _serviceCost to avoid double billing with the execution ledger.

Tests cover attribution threading, copilot vs workflow _serviceCost behavior, and lockfile updates for lucide-react resolution.

^{Reviewed by Cursor Bugbot for commit b904c8b. Configure here.}

[greptile-apps]

Greptile Summary

This PR updates billing context and hosted-key cost reporting for copilot tool executions. The main changes are:

• Propagate billing attribution into dynamically dispatched tool context.
• Emit hosted-key service costs for copilot calls without double-billing workflow runs.
• Include workspace context in internal LLM provider requests.
• Add tests for attribution propagation and caller-specific cost reporting.
• Update dependency resolutions in bun.lock.

Confidence Score: 5/5

This looks safe to merge.

• No blocking issues found in the changed code.
• Copilot and workflow billing remain separated by the existing execution-scope flag.
• Workspace forwarding matches the provider route's existing request contract and billing validation.

Important Files Changed

Filename	Overview
apps/sim/lib/copilot/tool-executor/executor.ts	Conditionally propagates billing attribution into the trusted dynamic-tool context.
apps/sim/lib/copilot/tool-executor/executor.test.ts	Tests billing-attribution propagation and omission for dynamic tools.
apps/sim/tools/index.ts	Adds copilot-only hosted-key service-cost output while retaining workflow ledger billing.
apps/sim/tools/index.test.ts	Tests service-cost emission for copilot calls and suppression for workflow calls.
apps/sim/tools/llm/chat.ts	Adds the execution workspace to internal provider requests when available.
bun.lock	Updates lucide-react dependency resolutions and lockfile metadata.

_{Reviews (1): Last reviewed commit: "fix llm chat tool" | Re-trigger Greptile}