Skip to content

Add dev build skills, and keep the Default Fee input a fixed width - #1029

Merged
Rigidity merged 6 commits into
mainfrom
rigidity/dev-launch-skills
Nov 19, 2026
Merged

Rigidity merged 6 commits into
mainfrom
rigidity/dev-launch-skills

Conversation

@Rigidity

@Rigidity Rigidity commented Nov 19, 2026 •

Copy link
Copy Markdown
Collaborator

Adds two agent skills for trying a dev build by hand, and fixes the Default Fee setting's input, which shrank beside its description.

Dev build skills

  • /dev-fresh-wallets runs pnpm tauri:dev with a new SAGE_ROOT in the agent's scratchpad, so testing starts with no wallets and default settings. A previous root can be reused ("same wallets as last time").
  • /dev-my-wallets runs it with SAGE_ROOT unset, against the real data directory: the real keys, wallet databases and config.toml. Webview storage (frontend settings, WalletConnect sessions) is per origin, so the dev build has its own. Before launching it checks that the installed Sage isn't running, and runs scripts/check_migrations.py.
    • Why the check exists. Sage turns any sqlx migration error into the "Database Migration Required" dialog, which deletes and resyncs the database if confirmed. For the apps database, the error is a panic at startup instead.
    • What it compares. It reads every database's _sqlx_migrations read-only (version, success and SHA-384 checksum) and compares it with the checkout's migrations and with the installed release tag's.
    • What it does with the result. It blocks the launch if a database the launch opens would fail: the apps database, and the active wallet's database and shared database on the active wallet's network. It asks first if those would be migrated past the installed release. Other wallets are listed with what would happen if they were opened.

Both share .claude/skills/dev-fresh-wallets/references/dev-session.md:

  • Ongoing work is paused until the user says to continue or closes the app.
  • The dev command runs detached, so no tool timeout can stop the app. A monitor passes on errors, warnings, panics and rebuilds, and the agent looks up the code behind each one.
  • Work asked for while the app runs keeps the dev command running, so the change is rebuilt or hot-reloaded in place.
  • When the app closes, the agent reads the whole log and reports how it ended, rebuilds, and deduplicated errors and warnings, marked as caused by the branch or not.

Default Fee input

  • Fixed width. The input had no width of its own, so a long description squeezed it, most of all as a fixed amount: about 100px in an 800px window. It's now 256px in every mode (speed, custom rate, fixed amount), like the other settings controls with fixed widths. FeeAmountInput takes a wrapperClassName for this, since in automatic mode className only sets the height.
  • Shorter description. It's now "The fee new transactions start with". The speed dropdown already shows each speed's rate and time.

Decisions to confirm

  • Fresh roots stay temporary, in the agent's scratchpad, as asked. They can be reused within a session, and a path can be given to keep one. The alternative is a durable default location such as ~/sage-profiles/.
  • The Default Fee description is one line. The alternative is a second sentence about automatic fees.

Checked in the sandbox at 1280, 800, 660 and 390px wide: the control stays 256px in all three modes, the below-minimum warning wraps within it, and the page doesn't scroll sideways. The catalogs aren't updated here, so the next release needs pnpm extract for the new description.

Note

Low Risk

The app change is a width and a description on one settings row, through a new optional prop that no other fee input passes. The skills only add agent instructions and a read-only script under .claude/, and don't affect the app.

  • Settings: fixed-width Default Fee input, shorter description
  • Fee inputs: optional wrapperClassName on FeeAmountInput and className on AutoFeeInput
  • Agent skills: dev-fresh-wallets, dev-my-wallets (with a read-only migration check script) and their shared session reference

… own

Both run pnpm tauri:dev detached, watch its log while the user tests, keep it running through edits so it rebuilds, and report what was notable when the app closes. The fresh-wallet skill gives the build a new SAGE_ROOT; the other unsets SAGE_ROOT and first checks that the installed Sage isn't running and that the user accepts any database migrations the release doesn't have.
Beside a long description, the input shrank, most of all as a fixed amount, which fell to about 100px in an 800px window. It's now 256px in every mode, like the other settings controls with fixed widths.
- Check database migrations in both directions before launching on real wallets, since any migration error leads to Sage's delete-and-resync dialog, and read applied versions in a way that works on WAL databases
- Say what the installed release does with a database migrated past it, and that a dev build's WalletConnect sessions and frontend settings are its own
- Keep fresh roots temporary and reusable within a session, with a given path to keep one longer
- Only count the window as up when sage-tauri runs, name the usual sources of log floods, and install with the pinned pnpm and the frozen lockfile
- Check every applied migration's checksum and success flag, not just the highest version, since a changed or failed migration brings up the same reset dialog
- Move the check into a script that opens databases read-only and doesn't create a missing one
- Fix the wording of which Running line means the window is up
- Block a launch only on databases it opens (the active wallet's, the shared ones and the apps database), and warn about other wallets, noting when the installed release already fails on them too
- Handle release tags without the apps migrations, and missing tags
- Report unreadable databases without blocking, and count an empty or missing database as having nothing applied
The migration check treated every database of the active wallet, and every shared database, as opened at launch, but Sage opens only the active wallet's database and shared database on its network. Others are now reported as what would happen if they were opened, without blocking or asking. The active wallet's databases are listed even before they exist, and shared databases aren't compared with releases that don't have them.
@Rigidity
Rigidity enabled auto-merge November 19, 2026 03:43
@Rigidity
Rigidity merged commit 2b8cd7e into main Nov 19, 2026
9 checks passed
@Rigidity
Rigidity deleted the rigidity/dev-launch-skills branch November 19, 2026 03:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant