Problem
As with most current compile-to-JavaScript languages - ClojureScript presents some challenges for interactive debugging. Source mapping can help us understand how our JavaScript maps to ClojureScript - but this alone is not enough. Being set breakpoits, step through code, and evaluate code in context greatly increases our ability to understand the nature of a particular programmer error.
WebKit Remote Debugging Protocol
Developer builds of Chrome now support a remote debugging protocol. Already this protocol support much of what is needed to build high quality debugging tools for ClojureScript. Coupled with source-mapping and analysis, it should be possible to develop sexpr level stepping and debugging of ClojureScript source.
References
http://www.webkit.org/blog/1620/webkit-remote-debugging/
http://code.google.com/chrome/devtools/docs/protocol/0.1/index.html