fix: assistant follow-ups — copyable answers, provider picker, nix hash, docs - #70
Merged
Conversation
✅ Deploy Preview for bazgaars-fmg ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Four commits that were finished alongside #69 but missed the merge.
Fix the desktop build. #69 brought Quill in, which changed
package-lock.json, but the pinned npm-deps hash innix/package.nixwent with the old lockfile.nix-buildfails onmaintoday with a hash mismatch. This is the hash CI itself computed.Let answers be copied.
.ui-dialog { user-select: none }exists so dialogs drag cleanly, and it also applied to the assistant, so no one could select an answer out of it. The panel body opts back in; the title bar keeps the drag behaviour, and no other dialog is touched. The same bug is live on Azgaar's master, where the panel CSS still sits in the global sheet.Pick a provider, then a model. The single dropdown listed every provider's models at once, and discovery made it longer. Choosing the provider first narrows the list to that provider's models, swaps in that provider's key and shows the local-server fields only for a local model. The stored setting is still the model, so existing preferences carry over: the saved model decides which provider starts selected.
Documentation. The Knowledge Base gains entries for the map assistant — what the two tabs are, whether a key is needed, which providers, what it may change, how to undo an edit, and what it costs. The Policy page previously promised the assistant never sees your map; that is now only true of the Help tab, so it is split into Help and This map, the latter stating plainly that map data goes to the provider you pick and that notes are the only thing it can change. The Ollama page described the old robot-button route into the AI Text Generator, which no longer exists, and pointed at
/api/generaterather than the OpenAI-compatible/v1endpoint the assistant uses.Verification
A clean worktree cut from merged
main, with a realnpm ci: 102 test files, 1070 tests,tsc --noEmitsilent, Biome clean apart from two pre-existing generator warnings, asset stamps current.In a headless browser against a local build: the panel and answers compute
user-select: textwhile the title bar staysnone, selecting an answer returns its text, and switching the provider from Anthropic to Mistral replaces the model list as expected.