#317 [Docs] Document protocol used by Flyte CoPilot Issue created by kumare3 Motivation: Why do you think this is important? When new users are using CoPilot, the protocol used to communicate should be clearly documented. Goal: What should the final outcome look like, ideally? Any user should be able to refer to this documentation and use coPilot Describe alternatives you've considered NA Flyte component ☑︎ Overall ☐ Flyte Setup and Installation scripts ☑︎ Flyte Documentation ☐ Flyte communication (slack/email etc) ☐ FlytePropeller ☐ FlyteIDL (Flyte specification language) ☐ Flytekit (Python SDK) ☐ FlyteAdmin (Control Plane service) ☐ FlytePlugins ☐ DataCatalog ☐ FlyteStdlib (common libraries) ☐ FlyteConsole (UI) ☐ Other [Optional] Propose: Link/Inline NA Additional context NA Is this a blocker for you to adopt Flyte This is a blocker to use CoPilot flyteorg/flyte

#317 [Docs] Document protocol used by Flyte CoPilot Issue closed as not planned by github-actions[bot] flyteorg/flyte