{"version":"2.1.314","anchor":"config-in-agent-view-gives-a-hint-about-defaulttoagentsview","canonical_anchor":"config-in-agent-view-gives-a-hint-about-defaulttoagentsview","heading":"Running \/config in agent view now explains how to stop opening there","tier":"use","area":"Agents View","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/config-in-agent-view-gives-a-hint-about-defaulttoagentsview","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Running \/config in agent view now explains how to stop opening there\n\nIn agent view, \/config now tells you to run it in a session and that `\/config defaultToAgentsView=false` stops Claude Code opening in agent view\n\n**What**\n\nAgent view is a screen Claude Code can open on instead of a regular session. Some commands do not work there. When you run `\/config` in agent view and the `defaultToAgentsView` setting is on, the message now reads: \"Run \/config in a session. \/config defaultToAgentsView=false stops opening here\".\n\nBefore, `\/config` showed the same general message as every other command, saying it isn't available in agent view and that you should open a session and run it there. Other commands still show that general message.\n\n**Why**\n\nIf Claude Code keeps opening in agent view and you do not want it to, the message now tells you the exact setting to change: run `\/config defaultToAgentsView=false` from a session.\n\n- Area: Agents View\n- Names: `defaultToAgentsView`, `\/config`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}