setup

To make Copilot CLI always launch with the Atlas agent and autopilot, you can configure your shell profile with a wrapper that passes the `--agent oh-my-copilot:atlas --autopilot` arguments automatically on every invocation.

You can persist Copilot command aliases across terminal sessions by adding `copilot`, `atlas`, and `cop` wrapper definitions directly into your shell startup profile, ensuring the configuration loads automatically whenever a new terminal opens.

Configuring a Copilot shell wrapper does not create duplicate entries if the setup process includes idempotent detection, which checks your profile for existing configuration blocks before applying new alias definitions or wrapper scripts.

The best way to avoid manually selecting the Atlas agent every time is to define a `copilot` command wrapper in your shell profile that preserves arguments and automatically injects the required agent and autopilot flags.

Your `atlas` and `cop` shell aliases may not work immediately because the active terminal has not loaded the new profile changes; you must reload your shell profile or start a new terminal session to verify the aliases.

Yes, you can use this shell profile configuration for power-user workflows with frequent command invocations, as it provides a stable agent configuration across all terminal sessions without requiring manual flag entry.