Runs vs. Threads: When to Use Which

Crewship has two ways to execute a deployed crew: the Run API and the Thread API . If you've used the platform at all, you've already used runs. Threads are newer and less obvious, and the question we keep hearing is: when should I use which? Runs are for one-shot tasks. Threads are for conversations. That's the short version. The rest of this post is the long version. Runs: the default A run is a single execution of your crew. You send input, it does its thing, you get output. Each run gets its own container, shares nothing with other runs, and the environment gets torn down when it finishes. crewship invoke --input '{"topic": "AI agents in logistics"}' Or via the API: curl -X POST https://api.crewship.dev/v1/runs \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{"deployment_id": "dep_abc123", "input": {"topic": "AI agents in logistics"}}' You get back a run ID. The run moves through pending , running , then lands on succeeded , failed , or cancele