Skip to content

feat: prevQuery.json -> globalScope.json, painted the tui elements#105

Merged
baalimago merged 7 commits intomainfrom
fix/global-scope-chat
Feb 8, 2026
Merged

feat: prevQuery.json -> globalScope.json, painted the tui elements#105
baalimago merged 7 commits intomainfrom
fix/global-scope-chat

Conversation

@baalimago
Copy link
Owner

@baalimago baalimago commented Feb 8, 2026

Another breaking change in strides towards becoming the most integrated CLI tool in the world! Althought the update is backwards
compatible, so no need for any updates

Naming it prevQuery.json didn't really fit anymore, global scope matches the terminology with dir scope better. This also
opens up the avenue for chats which are bound in other ways. git scope, perhaps? Who knows where we're heading with this.

In addition, on clai chat continue <empty-string>, the dirscope conversation is continued, followed by global scope.
The "continue" here is practically listing all the messages in the conversation in a convenient way, so that it's possible
to see how the LLM is doing.


Additional features:

  • We now have colours! This should've perhaps been its own PR, but noone reads these anyways so it doesn't matter very much

This is just convenience to quickly inspect the ongoing conversation by
listing it. Will simplify inspecting and resuming chat which is
currently worked on
We now have a theme.json and default colours. Also a NO_COLOUR arg which
removes any ansi colours
Setup still isn't colourized, but that's the last one
@baalimago baalimago force-pushed the fix/global-scope-chat branch from 4f0172a to 59af9ab Compare February 8, 2026 11:44
@baalimago baalimago changed the title refactor: prevQuery.json -> globalScope.json feat: prevQuery.json -> globalScope.json, painted the tui elements Feb 8, 2026
@baalimago baalimago merged commit 76dd83c into main Feb 8, 2026
2 checks passed
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