Container Use Extension
π₯Plug & Play
Watch the demo
This tutorial covers how to add the Container Use MCP Server as a goose extension enabling goose to work in an isolated environment.
Quick Install
- goose Desktop
- goose CLI
Command
container-use stdio
Configurationβ
info
- Remote MCP
- Local MCP
- goose Desktop
- goose CLI
- Launch the installer
- Click
Yesto confirm the installation - Click the button in the top-left to open the sidebar
- Navigate to the chat
- Run the
configurecommand:
goose configure
- Choose to add a
Command-line Extension.
β goose-configure
β
β What would you like to configure?
β Add Extension
β
β What type of extension would you like to add?
β β Built-in Extension
β β Command-line Extension (Run a local command or script)
β β Remote Extension (Streamable HTTP)
β
- Give your extension a name.
β goose-configure
β
β What would you like to configure?
β Add Extension
β
β What type of extension would you like to add?
β Command-line Extension
β
β What would you like to call this extension?
β Container Use
β
- Enter the command to run when this extension is used.
β goose-configure
β
β What would you like to configure?
β Add Extension
β
β What type of extension would you like to add?
β Command-line Extension
β
β What would you like to call this extension?
β Container Use
β
β What command should be run?
β npx -y mcp-remote https://container-use.com/mcp
β
- Enter the number of seconds goose should wait for actions to complete before timing out. Default is
300seconds.
β goose-configure
β
β What would you like to configure?
β Add Extension
β
β What type of extension would you like to add?
β Command-line Extension
β
β What would you like to call this extension?
β Container Use
β
β What command should be run?
β npx -y mcp-remote https://container-use.com/mcp
β
β Please set the timeout for this tool (in secs):
β 300
β
- Enter a description for this extension.
β goose-configure
β
β What would you like to configure?
β Add Extension
β
β What type of extension would you like to add?
β Command-line Extension
β
β What would you like to call this extension?
β Container Use
β
β What command should be run?
β npx -y mcp-remote https://container-use.com/mcp
β
β Please set the timeout for this tool (in secs):
β 300
β
β Enter a description for this extension:
β Run container automation with container-use
β
- Choose
Nowhen asked to add environment variables.
β goose-configure
β
β What would you like to configure?
β Add Extension
β
β What type of extension would you like to add?
β Command-line Extension
β
β What would you like to call this extension?
β Container Use
β
β What command should be run?
β npx -y mcp-remote https://container-use.com/mcp
β
β Please set the timeout for this tool (in secs):
β 300
β
β Enter a description for this extension:
β Run container automation with container-use
β
β Would you like to add environment variables?
β No
β
β Added Container Use extension
- goose Desktop
- goose CLI
- Launch the installer
- Click
Yesto confirm the installation - Click the button in the top-left to open the sidebar
- Navigate to the chat
- Run the
configurecommand:
goose configure
- Choose to add a
Command-line Extension.
β goose-configure
β
β What would you like to configure?
β Add Extension
β
β What type of extension would you like to add?
β β Built-in Extension
β β Command-line Extension (Run a local command or script)
β β Remote Extension (Streamable HTTP)
β
- Give your extension a name.
β goose-configure
β
β What would you like to configure?
β Add Extension
β
β What type of extension would you like to add?
β Command-line Extension
β
β What would you like to call this extension?
β Container Use
β
- Enter the command to run when this extension is used.
β goose-configure
β
β What would you like to configure?
β Add Extension
β
β What type of extension would you like to add?
β Command-line Extension
β
β What would you like to call this extension?
β Container Use
β
β What command should be run?
β container-use stdio
β
- Enter the number of seconds goose should wait for actions to complete before timing out. Default is
300seconds.
β goose-configure
β
β What would you like to configure?
β Add Extension
β
β What type of extension would you like to add?
β Command-line Extension
β
β What would you like to call this extension?
β Container Use
β
β What command should be run?
β container-use stdio
β
β Please set the timeout for this tool (in secs):
β 300
β
- Enter a description for this extension.
β goose-configure
β
β What would you like to configure?
β Add Extension
β
β What type of extension would you like to add?
β Command-line Extension
β
β What would you like to call this extension?
β Container Use
β
β What command should be run?
β container-use stdio
β
β Please set the timeout for this tool (in secs):
β 300
β
β Enter a description for this extension:
β Run container automation with container-use
β
- Choose
Nowhen asked to add environment variables.
β goose-configure
β
β What would you like to configure?
β Add Extension
β
β What type of extension would you like to add?
β Command-line Extension
β
β What would you like to call this extension?
β Container Use
β
β What command should be run?
β container-use stdio
β
β Please set the timeout for this tool (in secs):
β 300
β
β Enter a description for this extension:
β Run container automation with container-use
β
β Would you like to add environment variables?
β No
β
β Added Container Use extension
Example Usageβ
Here's a simple example of updating a file-based to-do app to use a SQLite database plus full testing - all within an isolated container environment.
info
See Isolated Development Environments for more examples, common workflows, and troubleshooting tips.
Promptβ
Run a container agent to add a feature to save my to-do list data in sqlite, build and run tests, but use a separate Git branch so my main code stays safe.
goose Outputβ
I'll help you create a container environment to add SQLite functionality to your to-do list application on a separate Git branch. Let me start by creating the environment and examining your current code structure.
βββ environment_create | containeruse ββββββββββββββββββββββββββ
environment_source: ./examples/todo-list
explanation: ...
title: ...
Now let me set up the environment with the necessary tools and then proceed with the SQLite feature development:
βββ environment_config | containeruse ββββββββββββββββββββββββββ
config:
base_image: python:3.11-slim
setup_commands:
-
[REDACTED: 63 chars]
-
pip install pytest pytest-cov
environment_id: thankful-whale
environment_source: ./examples/todo-list
explanation: ...
Let me install pytest after the environment is running:
---
Great! I've created a container environment for safely adding SQLite functionality to your to-do list app. Let me first explore the current code structure and then create a new Git branch.
---
Now I'll create the SQLite-based storage implementation. First, let me create a new version of the TaskManager with SQLite support:
---
## β
SQLite Feature Successfully Added!
I've successfully created a container environment and added SQLite functionality to your to-do list application! Here's what was accomplished:
### π― **Features Implemented**
1. **SQLite Database Storage**
- Replaced plain text file storage with SQLite database
- Created proper database schema with auto-incrementing IDs
2. **Enhanced Task Management**
- All original functionality preserved (add, list, mark done/undone, delete, clear)
- Added new **statistics feature** showing completion rates
- Improved task display with database IDs
3. **Two Implementation Versions**
- `taskman_sqlite.py` - Full-featured with Rich UI
- `taskman_sqlite_simple.py` - Simplified without external dependencies
### π§ͺ **Testing Completed**
- β
Created comprehensive test suite (`test_taskman_sqlite.py`)
- β
Built simple test runner (`test_simple.py`)
- β
All tests pass successfully
- β
Manual testing confirms functionality works perfectly
### π **Live Demo Results**
# Added tasks successfully
β Added task: Buy groceries
β Added task: Walk the dog
# Listed tasks with SQLite IDs
π Task List (SQLite)
# ID Status Task
1 1 β Done Buy groceries
2 2 β Todo Walk the dog
# Statistics working
Task Statistics:
Total tasks: 2
Completed: 1
Pending: 1
Completion rate: 50.0%
# Database verified
sqlite3 tasks.db "SELECT * FROM tasks;"
1|Buy groceries|1
2|Walk the dog|0
### π **Safe Development**
- β
Used separate container environment
- β
All changes isolated from your main code
- β
Original implementation preserved
- β
Backward compatibility maintained
### π **Files Created**
- `taskman_sqlite_simple.py` - Main SQLite implementation
- `test_simple.py` - Test suite
- `SQLITE_FEATURE_README.md` - Comprehensive documentation
- `tasks.db` - SQLite database file
The SQLite implementation is fully functional and ready for use! The original file-based version remains untouched, so you can safely evaluate the new SQLite features without any risk to your existing code.