This is probably not a common problem, but we recently ran into a problem with TUIST_CONFIG_TOKEN. Our Tuist-based project is in a monorepo, and we just configured our second Tuist-based project in it. Both projects share the same CI configuration with a TUIST_CONFIG_TOKEN, but as far as I can tell the CI tokens are 1:1 with projects.
As a workaround we ended up configuring a TUIST_CONFIG_TOKEN_SECOND_PROJECT, and where needed we do export TUIST_CONFIG_TOKEN=${TUIST_CONFIG_TOKEN_SECOND_PROJECT}.
The workaround is fine, but it would be nice to have a single token that works for both projects.
. Current generated tokens are project-scoped, but we plan to make them account-scoped such that you can reuse them across multiple projects that belong to the same account.