louis_lifu/warp

Fix Sentry framework copy in ./script/run. (#11666)

Description

Fixes local macOS runs with cocoa_sentry enabled by ensuring the app bundle’s Contents/Frameworks directory exists before copying Sentry.framework into it.

Without this, cp can create Contents/Frameworks as the copied framework directory itself, leaving framework internals directly under Contents/Frameworks and causing codesign --deep to reject the bundle.

Linked Issue

None.

Testing

Not run after the fix. This was diagnosed from a failed local run of:

./script/run --features cocoa_sentry,crash_reporting

That run reached the codesigning step and failed because the Sentry framework was copied into an invalid bundle layout.

I have manually tested my changes locally with ./script/run

Agent Mode

Warp Agent Mode - This PR was created via Warp’s AI Agent Mode

Co-Authored-By: Oz oz-agent@warp.dev

Warp Agentic Development Environment product preview

Website · Code · Agents · Terminal · Drive · Docs · How Warp Works

[!NOTE] OpenAI is the founding sponsor of the new, open-source Warp repository, and the new agentic management workflows are powered by GPT models.

About

Warp is an agentic development environment, born out of the terminal. Use Warp’s built-in coding agent, or bring your own CLI agent (Claude Code, Codex, Gemini CLI, and others).

Installation

You can download Warp and read our docs for platform-specific instructions.

Warp Contributions Overview Dashboard

Explore build.warp.dev to:

Watch thousands of Oz agents triage issues, write specs, implement changes, and review PRs
View top contributors and in-flight features
Track your own issues with GitHub sign-in
Click into active agent sessions in a web-compiled Warp terminal

Oz for OSS

Maintaining a popular open-source project? Apply for Oz credits to explore Oz for OSS.

Oz for OSS is our partner program for bringing the same agentic open-source management workflows used in this repository to select partner repositories. We work directly with maintainers to implement workflows for issue triage, PR review, community management, and contributor coordination in a way that fits each project.

Licensing

Warp’s UI framework (the warpui_core and warpui crates) are licensed under the MIT license.

The rest of the code in this repository is licensed under the AGPL v3.

Open Source & Contributing

Warp’s client codebase is open source and lives in this repository. We welcome community contributions and have designed a lightweight workflow to help new contributors get started. For the full contribution flow, read our CONTRIBUTING.md guide.

[!TIP] Chat with contributors and the Warp team in the #oss-contributors Slack channel — a good place for ad-hoc questions, design discussion, and pairing with maintainers. New here? Join the Warp Slack community first, then jump into #oss-contributors.

Issue to PR

Before filing, search existing issues for your bug or feature request. If nothing exists, file an issue using our templates. Security vulnerabilities should be reported privately as described in CONTRIBUTING.md.

Once filed, a Warp maintainer reviews the issue and may apply a readiness label: ready-to-spec signals the design is open for contributors to spec out, and ready-to-implement signals the design is settled and code PRs are welcome. Anyone can pick up a labeled issue — mention @oss-maintainers on an issue if you’d like it considered for a readiness label.

Building the Repo Locally

To build and run Warp from source:

./script/bootstrap   # platform-specific setup
./script/run         # build and run Warp
./script/presubmit   # fmt, clippy, and tests

See WARP.md for the full engineering guide, including coding style, testing, and platform-specific notes.

Joining the Team

Interested in joining the team? See our open roles.

Support and Questions

See our docs for a comprehensive guide to Warp’s features.
Join our Slack Community to connect with other users and get help from the Warp team — contributors hang out in #oss-contributors.
Try our Preview build to test the latest experimental features.
Mention @oss-maintainers on any issue to escalate to the team — for example, if you encounter problems with the automated agents.

Code of Conduct

We ask everyone to be respectful and empathetic. Warp follows the Code of Conduct. To report violations, email warp-coc at warp.dev.

Open Source Dependencies

We’d like to call out a few of the open source dependencies that have helped Warp to get off the ground: