feat: add support for per-Agent thinkingDefault level#27
Closed
feat: add support for per-Agent thinkingDefault level#27
Conversation
Owner
Author
|
Closing — all commits already present in dgarson/fork. |
dgarson
added a commit
that referenced
this pull request
Feb 22, 2026
Built by Wes: - Export type cards: Sessions/Agent Configs/Audit Log/Usage Data/Workspace Files/Full Backup - Format selectors (JSON/CSV/ZIP), date range pickers, Export Now with progress simulation - Scheduled exports: toggle, frequency, last/next run, Add Schedule modal - Recent exports table: 6 rows, status badges (Completed/Failed/In Progress), download links - Strict TypeScript, full a11y Build: ✓ 0 TS errors, 1.34s, 16.61 kB / gzip 4.05 kB
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.
Summary
Describe the problem and fix in 2–5 bullets:
Change Type (select all)
Scope (select all touched areas)
Linked Issue/PR
User-visible / Behavior Changes
List user-visible changes (including defaults/config).
If none, write
None.Security Impact (required)
Yes/No)Yes/No)Yes/No)Yes/No)Yes/No)Yes, explain risk + mitigation:Repro + Verification
Environment
Steps
Expected
Actual
Evidence
Attach at least one:
Human Verification (required)
What you personally verified (not just CI), and how:
Compatibility / Migration
Yes/No)Yes/No)Yes/No)Failure Recovery (if this breaks)
Risks and Mitigations
List only real risks for this PR. Add/remove entries as needed. If none, write
None.