you'll have to put a piece of code to support the MSG_OSVER serial message and reply with a unique OS ID and OS-string for your OS
then, when c0nb0x connects - it will ask your FW for MSG_OSVER and it will display the OS-string instead of the "(auto) Adafruit v1.05"
it will also store this OS ID in any .CXM files which you export from the firmware
now, for any specific
behaviour and/or features - c0nb0x would have to be modified
for the variables you want to share with c0nb0x (in a similar fashion as how the Tempo variable is shared) both your firmware and c0nb0x will need to be modified
it's no problem to add more custom messages and more "known" OSes to c0nb0x, that was my whole idea about all this..
the problem is on the firmware side, because you are already struggling to fit more "features" on the small chip, and these custom messages will require some more free space
i started coding a new "Diagnostic" firmware (based on the stock firmware v1.05) with the purpose to be the first one to implement MSG_OSVER and a few custom messages for specialized comunication with c0nb0x
i didn't finish the firmware and haven't released it yet, this was my old wish from the time there were much more people here, but i was unable to make such an app at that time
c0nb0x's source code isn't very elegant, i will be a bit ashamed if anyone sees it
i'll see after i release v1.00
i wanna have one really "stable" basic version of it, before any big modifications to the source code