Dependencies

tCode is deliberately small on disk. Its only runtime dependencies are requests, used for talking to the tAI backend, prompt_toolkit, which powers the interactive prompt and live command completion you see while typing, and pygments, used for syntax-highlighting code inside responses.

None of these pull in a large secondary dependency tree of their own; installing tCode adds a handful of well-established, widely used packages rather than dozens of transitive ones, and none of it touches anything outside your Python environment's own package directory.

This matters most in environments where dependency footprint is actively managed, a CI image, a locked-down corporate machine, a container meant to stay minimal. tCode does not require anything unusual to be permitted through that kind of gate.

All three are widely used, actively maintained open-source packages with long track records well beyond tCode specifically, rather than anything written or maintained in-house. Auditing tCode's dependency footprint is the same exercise as auditing any small Python CLI tool's, not a special case.