Repository navigation
ADO Lens 0.8.0 - #12
Merged
Merged
Conversation
…ne tools or developer prompts
Fewer tokens in every session: about 1.3k instead of 5.5–7k. - Tool groups loaded on demand: a session starts with the core (`ado_status`, `ado_settings`, `ado_upgrade`, `ado_work_item`, `ado_query`, `ado_search`, `ado_trace` and the new `ado_tools`), and Claude loads a group with `ado_tools enable=write` (or `"write;boards"`) when the conversation needs it; the client is told about the new tools (MCP `tools/list_changed`). Groups: `write`, `boards`, `wiki`, `code`, `tests`, `recipes`, `pr`, `pipelines`. The mode says which groups may be loaded. Skills and prompts load the groups they use. - `adolens config --load-all-tools true` (or *Tools at start* in the settings menu): every group of the mode at start, for a client that does not take new tools during a conversation. - Tool sets renamed to groups: `work` → `write`, `trace` → `code`, `test` → `tests` (old names in the settings still work). - Shorter descriptions of `ado_update`, `ado_create` and `ado_pr_update`. - Pull request tags (labels): `ado_pr_update action=tag tags="R349; -old"`, tags when creating a PR, and tags shown in PR lists, details and merged PRs. - Product Owner mode: no pull request or pipeline tools and no developer prompts (`dev_*`); they stay in the dev and full modes.
Fewer tokens in every session: about 1.3k instead of 5.5–7k. - Tool groups loaded on demand: a session starts with the core (`ado_status`, `ado_settings`, `ado_upgrade`, `ado_work_item`, `ado_query`, `ado_search`, `ado_trace` and the new `ado_tools`), and Claude loads a group with `ado_tools enable=write` (or `"write;boards"`) when the conversation needs it; the client is told about the new tools (MCP `tools/list_changed`). Groups: `write`, `boards`, `wiki`, `code`, `tests`, `recipes`, `pr`, `pipelines`. The mode says which groups may be loaded. Skills and prompts load the groups they use. - `adolens config --load-all-tools true` (or *Tools at start* in the settings menu): every group of the mode at start, for a client that does not take new tools during a conversation. - Tool sets renamed to groups: `work` → `write`, `trace` → `code`, `test` → `tests` (old names in the settings still work). - Shorter descriptions of `ado_update`, `ado_create` and `ado_pr_update`. - Pull request tags (labels): `ado_pr_update action=tag tags="R349; -old"`, tags when creating a PR, and tags shown in PR lists, details and merged PRs. - Product Owner mode: no pull request or pipeline tools and no developer prompts (`dev_*`); they stay in the dev and full modes.
Fewer tokens in every Claude Code session: about 1.6k instead of 5.5–7k. - Tool groups loaded on demand: a session starts with the core (`ado_status`, `ado_settings`, `ado_upgrade`, `ado_work_item`, `ado_query`, `ado_search`, `ado_trace` and the new `ado_tools`), and Claude loads a group with `ado_tools enable=write` (or `"write;boards"`) when the conversation needs it; the client is told about the new tools (MCP `tools/list_changed`). Groups: `write`, `boards`, `wiki`, `code`, `tests`, `recipes`, `pr`, `pipelines`. The mode says which groups may be loaded. Skills and prompts load the groups they use. - `adolens config --tool-loading auto|demand|all` (or *Tools at start* in the settings menu). `auto`, the default: on demand in Claude Code; every group of the mode at start in other clients (Claude Desktop), which may not take new tools during a conversation. `demand`: on demand everywhere. `all`: everything at start. - Tool sets renamed to groups: `work` → `write`, `trace` → `code`, `test` → `tests` (old names in the settings still work). - Shorter descriptions of `ado_update`, `ado_create` and `ado_pr_update`. - Pull request tags (labels): `ado_pr_update action=tag tags="R349; -old"`, tags when creating a PR, and tags shown in PR lists, details and merged PRs. - Product Owner mode: no pull request or pipeline tools and no developer prompts (`dev_*`); they stay in the dev and full modes.
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
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.
Fewer tokens in every Claude Code session: about 1.6k instead of 5.5–7k.
ado_status,ado_settings,ado_upgrade,ado_work_item,ado_query,ado_search,ado_traceand the newado_tools), and Claude loads a group withado_tools enable=write(or"write;boards") when the conversation needs it; the client is told about the new tools(MCP
tools/list_changed). Groups:write,boards,wiki,code,tests,recipes,pr,pipelines. The modesays which groups may be loaded. Skills and prompts load the groups they use.
adolens config --tool-loading auto|demand|all(or Tools at start in the settings menu).auto, the default: ondemand in Claude Code; every group of the mode at start in other clients (Claude Desktop), which may not take new
tools during a conversation.
demand: on demand everywhere.all: everything at start.work→write,trace→code,test→tests(old names in the settings still work).ado_update,ado_createandado_pr_update.ado_pr_update action=tag tags="R349; -old", tags when creating a PR, and tags shown inPR lists, details and merged PRs.
dev_*); they stay in the dev andfull modes.