A new version of the Connector CLI — the command-line tool used to develop, configure, and manage CHILI GraFx connectors — is available. This release is about the local debugger, and about closing the gap between how a connector behaves on your machine and how it behaves once published.
When you invoke a connector method in the debugger, most of what matters happens out of sight: how long the method took, and which external requests it made along the way. Until now the debugger showed only the end result, so a slow query or an unexpected extra round-trip was hard to spot.
The debugger now shows an Execution metrics panel alongside the output. For every method you invoke, it reports whether the call succeeded or failed, how long it took to complete, and a record of every outgoing fetch — including the URL and the time each one took. If a method made no external calls, the panel says so explicitly, which is a quick way to confirm a caching or short-circuit path is working as intended.
Two smaller changes to the result panel: errors are now visually distinct from successful responses, and the formatted JSON output can be copied to your clipboard in one click.
Testing a method that takes an asset ID — such as detail or download — usually means running query first and copying an ID out of the result. Because that result is rendered as JSON, the value you copy tends to arrive with its surrounding quotes or braces attached, and the method then fails on characters that were never part of the ID.
Fields in the debugger that expect an ID now normalize what you paste, extracting the ID itself and discarding the JSON around it.
The debugger recompiles connector.ts whenever you save it and reloads the browser tab. This is no longer something you opt into — watch mode is always active when you run connector-cli debug, so the edit-and-refresh loop works without any extra flags.
Compilation problems are also reported more consistently, so a TypeScript error is raised as an error instead of leaving you debugging an out-of-date build.
Connectors that need to pace themselves — polling an external job until it completes, or backing off after a rate-limit response — use the global sleep(ms) helper to pause between requests. That helper was available in the connector runtime but not in the local debugger, so any connector using await sleep(...) failed under connector-cli debug even though it ran correctly once published.
The debugger now provides sleep(ms) as well, bringing it in line with the runtime. Polling and back-off logic can be tested locally instead of only after deployment.
