When building locally using circleci CLI, it should be possible to ignore particular files. This would allow to ignore files with permissions that prevent the user inside docker from reading a file. This may be achieved by using an existing .dockerignore file (as in my case it is the same files that need to be excluded for docker builds with and without circleci). Or it could be achieved by adding a circleci specific ignore file. CCI-I-539

At this time, 2.0 workflows configuration is unsupported on the CircleCI CLI. CCI-I-401

If there's some misconfiguration or typo somewhere in the configuration of the CLI the following error will be returned when trying to create a namespace: "Non-nullable field was null". It would be extremely useful if the error message would return which field was "null". For example, the project name.

Hi, I'd like to be able to also use the CircleCI CLI on windows without resorting to vm's. Main purpose would be to check if my config file is valid. As a workaround/short term fix maybe you could make the config file checker available on the web in the same way that bitbucket pipelines have it? See: https://bitbucket-pipelines.atlassian.io/validator CCI-I-1394

Today I had problems updating/installing the Circle local CLI. The problem was I exceeded the GitHub API limit. It would be great if we can provide a Github OAUTH token (environment variable or option?) to the install.sh script (from github) and to the circleci update/switch commands CCI-I-544

If you define multiple workflows and have correct indentation on the first workflows and one indent too little on the rest, circleci config validate does not trigger an error. CCI-I-1131

create npm install of cli that will work on windows CCI-I-549

Originally https://circleci.atlassian.net/browse/CIRCLE-6997 . The local build tool/CLI/build-agent doesn't support YAML anchors and aliases. This was confirmed by a customer and Lev. Reported: https://discuss.circleci.com/t/yaml-anchors-implementation-incomplete/16916 CCI-I-89