{"version":"2.1.288","anchor":"remote-session-telemetryphases-for-repo-agents-skills-and","canonical_anchor":"remote-session-telemetryphases-for-repo-agents-skills-and","heading":"Remote sessions gain steps for repository agents, skills and switching","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/remote-session-telemetryphases-for-repo-agents-skills-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Remote sessions gain steps for repository agents, skills and switching\n\nRemote sessions have new named setup steps for repository agents, skills, root registration, switches and flag prefetching\n\n**Unclear.** What uses these step names and what they do for a session is not established.\n\n**What**\n\nThe list of named steps a remote session goes through gains five entries: `ccs_repo_agents`, `ccs_repo_skills`, `ccs_register_repo_root`, `ccs_repo_switches` and `ccs_host_flag_prefetch`.\n\n**Why**\n\nThe names suggest remote sessions may load agents and skills defined in a repository.\n\n- Flag `tengu_mcp_step_up_auth_dialog`: On for this account, and not off by default (read for one account on one subscription tier against v2.1.288; this account: on, anonymous baseline: on, compiled default: on) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}