From 9a93ee6375d610d580ef16c5ec52218727fab187 Mon Sep 17 00:00:00 2001 From: karl Date: Wed, 14 Oct 2026 12:52:47 +0200 Subject: [PATCH] Add user-facing agent prompt for source builds on all platforms --- README.md | 57 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 57 insertions(+) diff --git a/README.md b/README.md index 3ae0109..2c315dc 100644 --- a/README.md +++ b/README.md @@ -205,6 +205,63 @@ limitation it encounters. Prefer to set it up yourself? See the [build and launch instructions](docs/BUILDING.md). +### Build from source with your agent — macOS, Windows and Linux + +Want to build searchi yourself? Copy this prompt into an agent with local +terminal access. It builds for the computer you are using; on headless Linux, +it builds the CLI without desktop dependencies. + +```text +Build searchi from its source code, install it on this computer, and get it +ready for my first search. Do not substitute a prebuilt searchi release. +Repository: https://tea.karlcom.de/karl/searchi.git + +Detect whether I am using macOS, Windows or Linux, and detect my processor +architecture. Clone the public repository into a dedicated folder, or reuse +my existing checkout without overwriting local changes. Record the commit +you build. Read README.md, AGENTS.md, SKILLS.md and docs/BUILDING.md; use the +current normal release-build instructions and relevant platform documents. + +Install or configure the required build tools and native dependencies for +my platform. On Windows, prepare the C++ toolchain, Windows SDK and WebView2; +on macOS, prepare the Xcode tools; on Linux desktop, prepare the documented +WebKitGTK dependencies. Follow the repository's pinned versions and lockfiles. +Do the work, rather than only giving me commands to run. Ask for my help when +a password, license acceptance or system approval needs a human. + +Build the desktop app by default, including its frontend and native release +shell. On headless Linux, build only the CLI and workers, with no GUI dependencies. +Build and stage the genuine Google EmbeddingGemma 2 worker, extraction worker, +and supported media/speech helpers using the repository scripts. Use the normal +auto hardware-detecting runtime with CPU fallback. A missing acceleration build +dependency must be resolved or reported, not silently replaced by a CPU-only +distribution. The repository's Windows VM CPU-testing rule applies to tests +in that VM; it does not define the normal product build. + +Prepare the verified local models through the documented setup flow, reusing +valid cached assets. Tell me the expected download size first. Keep my existing +settings, index and model cache intact, keep search local, and leave optional +external summaries disabled. + +Run the applicable documented build checks, then install the built app and +its required runtime files in a dedicated location. Verify the installed copy, +not just an executable that depends on the source tree or a development server. +On desktop, open the app and verify filename search, a search by meaning, and +the launcher shortcut/tray where supported. On headless Linux, verify indexing +and genuine semantic search through the CLI, then give me a repeatable command +and optional MCP configuration. Use an owned sample folder for these checks; +do not alter my files. Let normal desktop indexing continue in the background. + +Finish with the installed location, source commit, how to launch searchi, +which checks actually passed, and any concrete platform limitation. Do not +claim an untested platform, hardware backend or UI interaction works. +``` + +Building needs internet access, disk space for the toolchain and local models, +and permission to install dependencies. macOS native execution remains +unverified in this repository; your agent should verify its build on your Mac +and report any issue. See [platform build instructions](docs/BUILDING.md). + ### Your first search Once searchi is running: