| commit | d27921f73b315dc1e01b92cc27370c29c3986f64 | [log] [tgz] |
|---|---|---|
| author | Jon Friesen <jon@jonfriesen.ca> | Thu Jun 05 13:15:56 2025 +0000 |
| committer | Josh Bleecher Snyder <josharian@gmail.com> | Thu Jun 05 19:29:47 2025 -0700 |
| tree | 8d245ab695e991337b7c11cdef23d280d10df466 | |
| parent | 5c654f6e66db881f17e202ec60cf7c997f7c0bad [diff] |
dockerimg: prioritize Dockerfile.sketch over Dockerfile Implement prioritization system for Dockerfile discovery that prefers Dockerfile.sketch when available, falling back to standard Dockerfile behavior when not present. Problem Analysis: The existing code had a TODO comment requesting preference for 'Dockerfile.sketch' to allow users to tailor environments specifically for Sketch usage. The current logic only handled single Dockerfile scenarios or fell back to generated dockerfiles, missing the opportunity to prioritize sketch-specific configurations. Implementation Changes: 1. Prioritization Function: - Added prioritizeDockerfiles() function with clear priority order - Priority: Dockerfile.sketch > Dockerfile > other Dockerfile.* - Case-insensitive matching for broader compatibility - Returns first candidate when no priority matches 2. Discovery Logic Update: - Modified findOrBuildDockerImage() to use prioritization - Removed single-dockerfile restriction for better flexibility - Uses prioritizeDockerfiles() for any number of candidates - Maintains existing behavior for generated dockerfile fallback 3. User Experience Enhancement: - Clear console output showing which dockerfile is being used - Consistent behavior regardless of dockerfile count - Preserves all existing functionality and error handling Technical Details: - Maintains backward compatibility with existing Dockerfile usage - No changes to function signatures or public interfaces - Efficient O(n) prioritization with early returns - Proper filepath handling for cross-platform compatibility Benefits: - Users can create Dockerfile.sketch for sketch-specific environments - Automatic preference without requiring configuration changes - Maintains existing Dockerfile support as fallback - Clear, predictable behavior for dockerfile selection Testing: - Added comprehensive unit tests for prioritizeDockerfiles() - Integration tests verify findDirDockerfiles() compatibility - End-to-end tests confirm findRepoDockerfiles() behavior - All existing tests continue to pass without modification This enhancement enables users to create sketch-optimized Docker environments while preserving full backward compatibility with existing Dockerfile workflows. Co-Authored-By: sketch <hello@sketch.dev> Change-ID: s1d7f47401929e175k
- .github/
- .vscode/
- bin/
- browser/
- claudetool/
- cmd/
- dockerimg/
- experiment/
- git_tools/
- httprr/
- llm/
- loop/
- skabandclient/
- skribe/
- termui/
- test/
- webui/
- .clabot
- .dockerignore
- .gitignore
- CONTRIBUTING.md
- dear_llm.md
- go.mod
- go.sum
- LICENSE
- README.md
Sketch
Sketch is an agentic coding tool. It draws the 🦉
🚀 Overview
Sketch runs in your terminal, has a web UI, understands your code, and helps you get work done. To keep your environment pristine, sketch starts a docker container and outputs its work onto a branch in your host git repository.
Sketch helps with most programming environments, but Sketch has extra goodies for Go.
📋 Quick Start
go install sketch.dev/cmd/sketch@latest sketch
🔧 Requirements
Currently, Sketch runs on macOS and Linux. It uses Docker for containers.
| Platform | Installation |
|---|---|
| macOS | brew install colima (or Docker Desktop/Orbstack) |
| Linux | apt install docker.io (or equivalent for your distro) |
| WSL2 | Install Docker Desktop for Windows (docker entirely inside WSL2 is tricky) |
The sketch.dev service is used to provide access to an LLM service and give you a way to access the web UI from anywhere.
🤝 Community & Feedback
- Discord: Join our community at https://discord.gg/6w9qNRUDzS
- GitHub Issues: Submit feedback at https://github.com/boldsoftware/sketch/issues
📖 User Guide
Getting Started
Start Sketch by running sketch in a Git repository. It will open your browser to the Sketch chat interface, but you can also use the CLI interface. Use -open=false if you want to use just the CLI interface.
Ask Sketch about your codebase or ask it to implement a feature. It may take a little while for Sketch to do its work, so hit the bell (🔔) icon to enable browser notifications. We won't spam you or anything; it will notify you when the Sketch agent's turn is done, and there's something to look at.
How Sketch Works
When you start Sketch, it:
- Creates a Dockerfile
- Builds it
- Copies your repository into it
- Starts a Docker container with the "inside" Sketch running
This design lets you run multiple sketches in parallel since they each have their own sandbox. It also lets Sketch work without worry: it can trash its own container, but it can't trash your machine.
Sketch's agentic loop uses tool calls (mostly shell commands, but also a handful of other important tools) to allow the LLM to interact with your codebase.
Getting Your Git Changes Out
Sketch is trained to make Git commits. When those happen, they are automatically pushed to the git repository where you started sketch with branch names sketch/*.
Finding Sketch branches:
git branch -a --sort=creatordate | grep sketch/ | tail
The UI keeps track of the latest branch it pushed and displays it prominently. You can use standard Git workflows to pull those branches into your workspace:
git cherry-pick $(git merge-base origin/main sketch/foo)
or merge the branch
git merge sketch/foo
or reset to the branch
git reset --hard sketch/foo
Ie use the same workflows you would if you were pulling in a friend's Pull Request.
Advanced: You can ask Sketch to git fetch sketch-host and rebase onto another commit. This will also fetch where you started Sketch, and we do a bit of "git fetch refspec configuration" to make origin/main work as a git reference.
Don't be afraid of asking Sketch to help you rebase, merge/squash commits, rewrite commit messages, and so forth; it's good at it!
Reviewing Diffs
The diff view shows you changes since Sketch started. Leaving comments on lines adds them to the chat box, and, when you hit Send (at the bottom of the page), Sketch goes to work addressing your comments.
Connecting to Sketch's Container
You can interact directly with the container in three ways:
- Web UI Terminal: Use the "Terminal" tab in the UI
- SSH: Look at the startup logs or click the information icon to see a command like
ssh sketch-ilik-eske-tcha-lott. We have automatically configured your SSH configuration to make these special hostnames work. - Visual Studio Code: Look for a command line or magic link behind the information icon, or when Sketch starts up. This starts a new VSCode session "remoted into" the container. You can edit the code, use the terminal, review diffs, and so forth.
Using SSH (and/or VSCode) allows you to forward ports from the container to your machine. For example, if you want to start your development webserver, you can do something like this:
# Forward container port 8888 to local port 8000 ssh -L8000:localhost:8888 sketch-ilik-epor-tfor-ward go run ./cmd/server
This makes http://localhost:8000/ on your machine point to localhost:8888 inside the container.
Using Browser Tools
You can ask Sketch to browse a web page and take screenshots. There are tools both for taking screenshots and "reading images", the latter of which sends the image to the LLM. This functionality is handy if you're working on a web page and want to see what the in-progress change looks like.
❓ FAQ
"No space left on device"
Docker images, containers, and so forth tend to pile up. Ask Docker to prune unused images and containers:
docker system prune -a
🛠️ Development
See CONTRIBUTING.md for development guidelines.
📄 Open Source
Sketch is open source. It is right here in this repository! Have a look around and mod away.
If you want to run Sketch entirely without the sketch.dev service, you can set the flag -skaband-addr="" and then provide an ANTHROPIC_API_KEY environment variable. (More LLM services coming soon!)