In Cyc's multithreaded implementation, each API connection spawns a separate thread which is completely dedicated to handling the API server connection. When the connection is broken, the thread exits.

Note that a consequence of using a multithreaded implementation is that the Cyc process is always responsive to new TCP connections, and modifications to the Cyc KB performed via the API server are always reflected in future API connections.