Gitiles
Code Review Sign In
code.v1.dodo.cloud / sketch / cf724583660cf683efa7fd8eb9b32e120e88beb7
commitcf724583660cf683efa7fd8eb9b32e120e88beb7[log] [tgz]
authorbanksean <banksean@gmail.com>Mon Jul 21 22:22:57 2025 +0000
committerAutoformatter <bot@sketch.dev>Mon Jul 21 22:45:56 2025 +0000
treeca8f4072f3e131ace3400552698caa04786a155c
parent4432056dc2db2f4b9b1120a890255a540a4c8537 [diff]
skaband: move timeline viewer from sketch/webui to resolve bundle conflicts

Move read-only timeline viewer functionality from sketch/webui to skaband
to eliminate custom element registration conflicts when using newsessions
with newui=true parameter.

Changes made:
- Created skaband/sketch-timeline-readonly.ts with timeline viewer functionality
- Updated skaband/messages.gohtml to use local sketch-timeline-readonly.js bundle
- Removed messages-viewer.ts from sketch/webui build configuration
- Updated Makefile to remove messages-viewer bundle extraction steps
- Added sketch-timeline-readonly.ts to skaband build.js entry points

Files created:
- skaband/sketch-timeline-readonly.ts: Timeline viewer component for archived sessions
- skaband/sketch-timeline-readonly.test.ts: Test coverage for timeline functionality

Files removed:
- sketch/webui/src/messages-viewer.ts: Relocated to skaband
- sketch/webui/src/messages-viewer.test.ts: Relocated to skaband

Build configuration updates:
- sketch/webui/esbuild.go: Remove messages-viewer.ts from bundleTs arrays
- sketch/webui/package.json: Remove messages-viewer.js export
- skaband/build.js: Add sketch-timeline-readonly.ts entry point
- Makefile: Remove messages-viewer bundle extraction from build and prepare-deploy

The timeline viewer is only used by skaband for archived session viewing,
so co-locating it with skaband eliminates the architectural issue where
both messages-viewer.js and newsessions-components.js contained overlapping
custom elements (sketch-timeline, sketch-tool-card-*, etc.) causing
registration conflicts.

This change resolves bundle conflicts on /newsessions?newui=true while
maintaining identical functionality for archived message viewing.

Co-Authored-By: sketch <hello@sketch.dev>
Change-ID: sd62ec3594672899ek
5 files changed
tree: ca8f4072f3e131ace3400552698caa04786a155c
  1. .github/
  2. .vscode/
  3. bin/
  4. browser/
  5. build/
  6. claudetool/
  7. cmd/
  8. dockerimg/
  9. embedded/
  10. experiment/
  11. git_tools/
  12. httprr/
  13. llm/
  14. loop/
  15. mcp/
  16. skabandclient/
  17. skribe/
  18. termui/
  19. test_recipes/
  20. update/
  21. webui/
  22. .clabot
  23. .dockerignore
  24. .gitignore
  25. .goreleaser.yml
  26. CONTRIBUTING.md
  27. dear_llm.md
  28. go.mod
  29. go.sum
  30. LICENSE
  31. Makefile
  32. README.md
  33. test_file.js
README.md

Sketch

Go Reference Discord GitHub Workflow Status License

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

Install via GitHub Releases

Grab the most recent nightly release.

Update by running sketch -update.

Build from source

Clone this repo, and then run:

$ make
$ ./sketch

🔧 Requirements

Currently, Sketch runs on MacOS and Linux. It uses Docker for containers.

PlatformInstallation
MacOSbrew install colima (or OrbStack or Docker Desktop)
Linuxapt install docker.io (or equivalent for your distro)
WSL2Install 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

📖 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:

  1. Creates a Dockerfile
  2. Builds it
  3. Copies your repository into it
  4. 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:

  1. Web UI Terminal: Use the "Terminal" tab in the UI
  2. 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.
  3. 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

Go Reference

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!)