Issue
This feature would lay out a pattern to support a wide variety of use cases. The available vars I'm imagining include:
- tokens (in, out, cached etc)
- execution time of last model call
- context tokens
- model calls since last "/clear" etc
- context file count
- pwd
- all the vars in the standard prompt
- now() (in a few flavours)
- config options
- etc etc
The vars could then be used to define templates for the following:
- TUI status bar lines (lower and upper)
- linear mode prompts
- standardised (TUI and linear) model call prefaces and postscript (ie to go in the scrollable console log in both modes)
- log formats (with several logs definable for different trigger events)
- embedding in custom commands
- ?? others
Each variable should be:
- cached
- lazy defined with some kind of performance tracking (as inevitably someone will make a bloated template and wonder why there experience is so laggy)
- vieweable within a complete list (~
export in bash) - ?? /vars
Version and model info
No response
Issue
This feature would lay out a pattern to support a wide variety of use cases. The available vars I'm imagining include:
The vars could then be used to define templates for the following:
Each variable should be:
exportin bash) - ??/varsVersion and model info
No response