# Project-Based Cursor CLI Containers

**URL:** <https://forum.cursor.com/t/project-based-cursor-cli-containers/127970>\
**Category:** Built for Cursor\
**Created:** [August 10, 2025, 8:43am UTC](https://forum.cursor.com/t/project-based-cursor-cli-containers/127970 "2025-08-10T08:43:19Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![koudelka](https://avatars.discourse-cdn.com/v4/letter/k/b5ac83/32.png) [@koudelka](https://forum.cursor.com/u/koudelka)\
**Post date:** [August 10, 2025, 8:43am UTC](https://forum.cursor.com/t/project-based-cursor-cli-containers/127970/1 "2025-08-10T08:43:19Z")

</div>

I’ve been experimenting with running Cursor CLI agents inside project-specific Docker containers. The setup is dead simple — a `<name>.cursor-agent` file and a Bash function that creates or resumes the container when you run `cursor-agent`.  
It’s been great for isolation, reproducibility, and security. Curious to hear if others in the Cursor community have tried something similar, or if this could be worth formalizing into a shared convention.  
Repo: [https://github.com/cleaton/cli-agent-container](https://github.com/cleaton/cli-agent-container)