mcpField
F
FixThis

FixThis

Local
github.com/beyondwinDeveloper Tools5Updated today

About FixThis

FixThis is a local-first feedback and handoff tool for Jetpack Compose debug apps. It turns UI annotations into screenshots, source candidates, and confidence notes for coding agents, with a local browser console and no external API calls.

Key features

  1. 01Annotate Compose UI elements or areas
  2. 02View the app in a local browser console
  3. 03Provide source candidates with line numbers
  4. 04Include confidence warnings and screen fingerprints
  5. 05Save local MCP handoffs or copy prompts

Use cases

  1. 01Report a specific UI change to a coding agent
  2. 02Identify source locations for dense Compose screens
  3. 03Distinguish repeated UI instances during feedback
  4. 04Share annotated context through MCP or Markdown

MCP support

Its local MCP server lets Claude Code or Codex access saved feedback handoffs through the `Save to MCP` flow. The project also supports copying a prompt for chat agents.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"beyondwin-fixthis": {
"command": "npx",
"args": [
"-y",
"@beyondwin/fixthis"
]
}
}
}
Run commandnpx -y @beyondwin/fixthis

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@beyondwin/fixthis1.5.0

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

FixThis for Android Compose

CI License: MIT JDK 21 Node 20+ Compose

FixThis Studio — point at any Jetpack Compose UI element, annotate, hand off AI-ready context to your coding agent

Point at a Jetpack Compose UI, write the change, and hand Claude, Codex, Cursor, or another coding agent the source context it needs.

FixThis is debug-only. It attaches a sidekick to a Compose debug app, mirrors the screen into a local browser console, and turns annotations into a compact handoff: screenshot bounds, semantics, source candidates, and confidence warnings.

Click a component to select it. Drag when the target is spacing, empty room, or something that is not a clean Compose node.

Works Today

  • Try the sample app in about five minutes.
  • Install the desktop CLI/MCP with Homebrew, npm, or GitHub Releases.
  • Add it to an external app with the Gradle plugin io.github.beyondwin.fixthis.compose.
  • Let Claude Code or Codex configure the sample with ./scripts/bootstrap-mcp.sh --sample.
  • Let an agent configure your app with fixthis install-agent.
  • Use Copy Prompt with Cursor, ChatGPT, or any chat agent.
  • Use Save to MCP with Claude Code or Codex.
  • Save to MCP can attach a bounded, redacted Android diagnostics baseline. Switch the session to Manual or Off if you do not want that. Copy Prompt never starts collection.
  • Runs locally over ADB and 127.0.0.1. No external API calls.

Quick Start: Agent Installs FixThis in Your App

Claude Code / Codex Bootstrap Prompt

Paste this into Claude Code or Codex from the root of a Jetpack Compose Android app:

Install FixThis in this project and configure it for this agent.

Use this order:
1. Run `fixthis install-agent --project-dir . --target all --verify --json`.
2. Use the JSON `readiness.state` and `actions[]` as the source of truth.
3. If `requiresUserAction` is true, tell me the exact blocking action.
4. Do not call `fixthis_open_feedback_console` until `readyForMcpTooling` is true, or until the report's `agent_after_restart` action is reached after restart.

Restart Claude Code or Codex if the report asks for it.
Do not configure release builds. Do not commit `.fixthis/`.

The agent should run:

# macOS
brew install beyondwin/tools/fixthis

# Node
npm install -g @beyondwin/fixthis

# macOS/Linux fallback
curl -fsSL https://raw.githubusercontent.com/beyondwin/FixThis/main/scripts/install-fixthis.sh \
  | bash -s -- --version v1.5.0

fixthis install-agent --project-dir . --target all --verify --json

If Homebrew already has it, run brew update && brew upgrade beyondwin/tools/fixthis and check fixthis --version.

fixthis install-agent applies the Gradle plugin, writes MCP config, and writes .fixthis/project.json plus .fixthis/agent-setup.*. If doctor reports NEEDS_INSTALL or metadata is missing, run ./gradlew fixthisSetup and rerun fixthis install-agent --project-dir . --target all --verify --json. Restart Claude Code or Codex when the report asks, then call fixthis_open_feedback_console. For a manual check, use fixthis doctor --project-dir . --json.

Published plugin:

plugins {
    id("io.github.beyondwin.fixthis.compose") version "1.5.0"
}

The plugin adds the debug-only sidekick and keeps release builds out.

Quick Start: Sample App to Agent Handoff

git clone <this-repo> && cd FixThis
./gradlew :fixthis-cli:installDist :fixthis-mcp:installDist
fixthis-cli/build/install/fixthis/bin/fixthis doctor --package io.github.beyondwin.fixthis.sample
fixthis-cli/build/install/fixthis/bin/fixthis run --package io.github.beyondwin.fixthis.sample

fixthis run installs the sample debug APK, launches it, and opens FixThis Studio at http://127.0.0.1:<port>.

In the console:

  1. Click Annotate.
  2. Click a UI element, or drag an area.
  3. Type the change you want.
  4. Repeat for other spots on this screen.
  5. Copy Prompt for a chat agent, or Save to MCP for Claude Code / Codex.

You are done when a numbered annotation is visible and you have copied Markdown or saved a local MCP handoff.

Maintainers can prove that Copy Prompt path on a connected device:

npm run real-copy-prompt:smoke -- --strict

Pick Your Path

GoalStart here
Try it without touching your appSample quick start
Add it to your debug buildAdd to your app
Connect an agentConnect your agent
Bootstrap MCP from this repoMCP.md
Use the consoleConsole tour
Understand the productProduct
Diagnose a failureTroubleshooting
Inspect contractsDocs index
ContributeCONTRIBUTING.md
ReaderStart here
First-time userSample quick start
External app developerAdd to your app
Agent in this repoAGENTS.md and project map
MaintainerDocs index and project map
Contract or CLI changeReference contracts

Why not just a screenshot?

A screenshot is enough when the target is obvious. FixThis helps when the UI is dense, list-rendered, or named mostly by composable:

  • Top-3 source candidates with line numbers and match reasons
  • editSurface hints for call site vs component vs copy vs layout vs interop
  • Instance grouping so identical cards stay distinct
  • Screen fingerprint so a rotated or changed screen cannot sneak into a save
  • Honest confidence: visual-only, stale, or possible AndroidView/WebView
  • Bounded runtime diagnostics on Save to MCP
  • Retry-safe batches that do not duplicate work

Modules

ModuleRole
:app (sample/)Validation sample
:fixthis-compose-corePure Kotlin domain
:fixthis-compose-sidekickDebug Android runtime
:fixthis-gradle-pluginSource index and debug wiring
:fixthis-cliDesktop CLI
:fixthis-mcpMCP server and local console

More: Product, decisions, architecture.

Status

Public install paths:

  • Gradle plugin io.github.beyondwin.fixthis.compose
  • Maven io.github.beyondwin:fixthis-compose-sidekick and fixthis-compose-core
  • Homebrew brew install beyondwin/tools/fixthis
  • GitHub Release fixthis-cli-mcp-vX.Y.Z.tar.gz
  • npm @beyondwin/fixthis
  • MCP Registry io.github.beyondwin/fixthis

Live dashboard: Release readiness.

main may be ahead of the latest tag. See CHANGELOG and release notes.

Agents in this repo should read AGENTS.md.

Trust

FixThis stays on your machine. The sidekick talks over ADB, the console binds to localhost, and Save to MCP writes under .fixthis/. Screenshots can still contain sensitive pixels. Review them before sharing. Do not commit .fixthis/.

Details: Privacy, Security, Threat model.

V1 stays narrow: Compose debug builds, local ADB, MCP-first handoff, best-effort source candidates, no cloud upload. See Roadmap.

License

MIT. Third-party notices in NOTICE.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.