commit	9aa141a4bdde68a1ad57d56ba3cb0023109c6b7b	[log] [tgz]
author	banksean <banksean@gmail.com>	Fri Jun 27 05:02:24 2025 +0000
committer	Autoformatter <bot@sketch.dev>	Fri Jun 27 05:07:21 2025 +0000
tree	343ad7ce6404ceeee210a1f43d4b3c0f86e70756
parent	b01b150abe7bf3066a08dcaafe1e443aa101c5c1 [diff]

skaband: remove all manual input switching functionality from sessions page

fix for #430

Completely remove auto-switch and manual switch functionality to simplify
the repository selection interface and eliminate user confusion.

Problems Solved:

Complex Dual-Mode Interface:
- Auto-switch feature automatically changed UI state without user consent
- Manual switch buttons created confusing dual-mode interface
- Users unclear when to use dropdown vs manual input vs auto-switching
- Multiple code paths for repository input handling created maintenance overhead

Inconsistent User Experience:
- Repository loading failures triggered unexpected auto-switch behavior
- Manual buttons overlaid on repository selection interface
- Console error logging without clear user benefit
- No clear guidance on which input method to use

JavaScript Complexity:
- switchToManualInput() and enhancedSwitchToManualInput() functions
- Complex validation setup and event handlers for switching
- setTimeout scripts for auto-switch timeouts and console logging
- Event listeners and DOM manipulation for button interactions

Solution Implementation:

Complete Feature Removal:
- Removed all auto-switch timeout scripts and console error logging
- Eliminated switchToManualInput() and enhancedSwitchToManualInput() functions
- Removed all manual switch buttons from repository selection interface
- Simplified JavaScript by removing switching-related event handlers

Simplified Repository Selection:
- Repository selection now uses standard HTML select dropdown only
- Hidden text input remains for loading state (standard form behavior)
- No manual override buttons or automatic switching functionality
- Clean, predictable interface focused on dropdown selection

Template Structure Cleanup:
- Removed button elements with switch-to-manual IDs from HTML
- Eliminated complex validation setup code tied to manual switching
- Simplified repository selection container structure
- Preserved core form functionality and submission workflow

Implementation Details:

Removed JavaScript Functions:
- switchToManualInput(): DOM manipulation for switching input modes
- enhancedSwitchToManualInput(): Validation setup and enhanced switching
- Auto-switch timeout script: 10-second timeout with console logging
- Manual button event handlers: onclick setup and event listeners

Removed HTML Elements:
- Manual switch button in dropdown mode
- Manual switch button in loading state
- All switch-to-manual ID references
- Button overlay positioning and styling

Preserved Core Functionality:
- Repository select dropdown when GitHubRepos available
- Hidden text input for loading states
- Form submission and validation workflow
- Repository selection and session creation process

Testing Updates:
- Updated TestRepositoryUIFeatures to reflect simplified interface
- Removed tests checking for presence of removed switching functionality
- Tests now focus on core dropdown and loading state functionality
- Verified repository selection continues to work with standard form behavior

User Experience Impact:
- Single, predictable way to select repositories via dropdown
- No unexpected UI changes or automatic state transitions
- Standard HTML form behavior users expect
- Reduced cognitive load with simpler interface

Files Modified:
- skaband/sessions.gohtml: Removed switching functions, buttons, and timeout scripts
- skaband/skaband_test.go: Updated tests for simplified interface

The simplified interface eliminates confusion by providing a single,
standard way to select repositories through HTML dropdown selection.

Co-Authored-By: sketch <hello@sketch.dev>
Change-ID: sdc7975f0ace4b511k

webui/src/web-components/DEAR_LLM.md[diff]

1 file changed

tree: 343ad7ce6404ceeee210a1f43d4b3c0f86e70756

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