Summary
The user is asking if ContainerTask tasks can use FlyteDirectory for inputs and outputs, referencing a GitHub pull request. They intend to test this remotely to enhance their workflows but are unsure if the functionality is restricted to local execution. They are also confused about whether the issue lies in the Flyte copilot binary not being updated to handle folders. The response confirms that Flyte copilot does not support FlyteDirectory as input but does support it as output, and due to higher priorities, there will be no support for it at this time.