Skip to content
This repository was archived by the owner on Oct 29, 2026. It is now read-only.

Load Gemma from the shipped Mesh config - #34

Merged
kukirin-ui merged 1 commit into
mainfrom
cursor/meridian-skill-trees-15e2
Oct 11, 2026
Merged

kukirin-ui merged 1 commit into
mainfrom
cursor/meridian-skill-trees-15e2

Conversation

@kukirin-ui

Copy link
Copy Markdown
Owner

What this does

config.json sets the active model to custom. custom_model_path is /data/data/com.termux/files/home/models/gemma-2-9b-it-Q4_K_M.gguf. Mesh opens on Gemma 2 9B and asks that file. Save identity keeps a different choice.

The file ships inside the app. Mesh reads it on launch. A model saved from the Model menu stays selected after that.

Download model still looks in Downloads and ~/models first, so a Gemma file already on the phone is linked and is not fetched again.

Version 2.3.28 (versionCode 71). Install this over 2.3.27. Pro and a connected Termux session are still required.

Checks

  • node tools/qa/ui-audit.mjs checks the custom tier and the Gemma path.
  • node tools/license/gates.test.mjs
  • Browser: Mesh opens with Gemma 2 9B selected. A question uses gemma-2-9b-it-Q4_K_M.gguf. Saving Llama 3.2 1B updates the note and keeps that choice.
  • Build APK succeeded: https://github.com/kukirin-ui/Meridian/actions/runs/38098557426

Install

Logged-in download of Meridian-2.3.28-debug: https://github.com/kukirin-ui/Meridian/actions/runs/38098557426/artifacts/11687042965

Open in Web Open in Cursor 

config.json now points custom_model_path at the Gemma file in the Termux home models folder. Mesh opens on that model until Save identity stores a different choice.

Co-authored-by: AAA <kukirin-ui@users.noreply.github.com>
@kukirin-ui
kukirin-ui marked this pull request as ready for review October 11, 2026 00:31
@kukirin-ui
kukirin-ui merged commit 2ee82c8 into main Oct 11, 2026
2 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants