commit	4168263109e4f5dfa9b24d3ce66594d90c6cf66a	[log] [tgz]
author	philip.zeyliger <philip.zeyliger@gmail.com>	Mon Jun 09 22:23:25 2025 +0000
committer	Autoformatter <bot@sketch.dev>	Mon Jun 09 22:24:32 2025 +0000
tree	7a359884219f736a0da706f098d277d6713d8fad
parent	209ea91bc220b945936250f8aecd9d69974e0ada [diff]

webui: fix mobile error message styling to display in red

Add proper red styling for error messages in mobile chat interface to match
desktop behavior and fix GitHub issue #141.

Problem Analysis:
Mobile error messages lacked visual distinction from regular messages, appearing
with the same gray background as assistant messages. The desktop interface
properly displays error messages with red background (#ffebee) and red text
(#d32f2f), but the mobile-chat component was missing this styling, creating
inconsistent user experience across interfaces.

The mobile chat component correctly filtered error messages (type: 'error')
and displayed them, but the getMessageRole() method didn't handle error types,
defaulting them to 'assistant' styling.

Implementation Changes:

1. CSS Error Message Styling:
   - Added .message.error .message-bubble styles with red theme
   - Background: #ffebee (light red background matching desktop)
   - Text color: #d32f2f (dark red text for readability)
   - Border-radius: 18px (uniform rounding for clean appearance)
   - Maintains mobile-optimized layout and touch-friendly design

2. Message Role Classification:
   - Enhanced getMessageRole() method to properly handle error message types
   - Added explicit 'error' case returning 'error' class name
   - Ensures error messages receive proper CSS class assignment

3. Test Coverage:
   - Added comprehensive mobile-chat component tests
   - Specific test for error message red styling verification
   - CSS color validation using computed styles
   - Message filtering and rendering tests for all message types

Technical Details:
- Styling follows existing mobile component patterns with touch-friendly design
- Color scheme matches desktop timeline-message component for consistency
- Error messages maintain left alignment like other system messages
- Clean, uniformly rounded corners without extra borders for polished appearance

Benefits:
- Visual consistency between desktop and mobile error message presentation
- Clear error message identification for mobile users
- Improved accessibility with distinct error styling
- Maintains touch-friendly mobile design principles
- Clean, professional appearance without visual clutter
- Resolves GitHub issue #141 mobile error visibility

Testing:
- Added mobile-chat.test.ts with error message styling verification
- TypeScript compilation successful with no type errors
- Build process completes without warnings
- CSS computed style validation confirms red color application

This fix ensures error messages are visually distinctive on mobile devices,
providing users with clear feedback when errors occur while maintaining
the clean, touch-optimized mobile interface design.

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

2 files changed

tree: 7a359884219f736a0da706f098d277d6713d8fad

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