The hosting of your CSS files on their servers is also not suited for a development environment that has more than 1 environment, as I would not want to be editing files that are on a live server on a regular basis without first making those changes locally (and possibly checking them into an SCM of some sort first) because my css would quickly become out of sync across environments.
May I ask, the projects that you work on, do you have more than 1 environment that you use and do you collaborate with any other developers on these projects?
As far as working on teams, they're "thinking about how to expose your CSS in a versioned way so that you can keep it in Mercurial (with Kiln!), or Git, or whatever other version control software you might be using". Perhaps you're right, it's better to wait until that is implemented if you have that kind of setup.
EDIT: I've started testing it, and you can add other admins and editor users for sites, very nice.
Seems like a Web Putty browser plugin would help preserve the "local transparent editing a la Firebug" use case. Transparent meaning, no edits to your existing HTML required to demo different CSS stylings. Or am I misunderstanding this?
They also give you the option of hosting your CSS file on their servers, which is why you'd need the link to that CSS file.
It's all explained on their website which you might not have read/understood, or maybe I am missing something.
As a web developer working on quite a few projects, this tool seems great, although I can't have them hosting CSS for internal projects.