{"version":"2.1.242","anchor":"slash-commands-load-on-demand-instead-of-at-startup","canonical_anchor":"slash-commands-load-on-demand-instead-of-at-startup","heading":"Slash commands load on demand instead of at startup","tier":"notice","area":"Slash Commands","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/slash-commands-load-on-demand-instead-of-at-startup","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Slash commands load on demand instead of at startup\n\nBuilt-in slash commands load when you invoke them, so startup does less work.\n\n**What**\n\nEach built-in slash command is now a separate chunk fetched when you invoke it, rather than code loaded as part of the main bundle, which moves that work off startup.\n\n**Details**\n\n- The registry entries changed from wrappers around already-loaded module initializers to real dynamic imports, one chunk per command, covering \/config, \/mcp, \/skills, \/install-github-app and the rest.\n- The list of available command names still comes from the same map's keys, so nothing changes about which commands exist or how they are discovered.\n- The conditional entries for background\/daemon\/stop and workflows are unchanged.\n\n**Evidence**\n\n`\"install-github-app\": () => import(`\n\n- Area: Slash Commands\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}