Skip to content

Move cloud object models to separate crate.#11164

Draft
vorporeal wants to merge 2 commits into
david/move-GenericStringModel-to-warp_server_clientfrom
david/start-moving-cloud-object-models
Draft

Move cloud object models to separate crate.#11164
vorporeal wants to merge 2 commits into
david/move-GenericStringModel-to-warp_server_clientfrom
david/start-moving-cloud-object-models

Conversation

@vorporeal
Copy link
Copy Markdown
Contributor

@vorporeal vorporeal commented May 18, 2026

Description

Moves the remaining low-level cloud object model definitions out of the app crate so they can be reused outside warp without pulling in app-specific code.

This PR moves the workflow enum and cloud environment model surfaces into the server/client cloud object layer while keeping compatibility re-exports for existing app call sites. This is a preparatory step toward extracting the shared cloud object substrate and model crates in the follow-up PRs.

Linked Issue

None.

Testing

  • cargo check --manifest-path /Users/david/src/warp/Cargo.toml -p warp --tests

No manual app testing; this is a crate-boundary refactor with no intended product behavior changes.

Agent Mode

  • Warp Agent Mode - This PR was created via Warp's AI Agent Mode

CHANGELOG-NONE

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

Copy link
Copy Markdown
Contributor Author

vorporeal commented May 18, 2026

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant