Product documentation · Current desktop UI

Modules, languages, and feature discovery

UI library · Desktop windows · API reference

Tech Connector combines a desktop shell with optional specialist suites, connected host bridges, and model providers. A menu label, source function, registered operation, connected bridge, and validated outcome are different states. Use the status and catalog controls to see which state you have.

What is modular

  • Workspace suites: Chat, Editor, Search / Symbols, Pipelines, Assets, Kingdom, Ophanim, Garden, and DCC Driver are separate work areas.
  • Host integrations: each DCC or engine has its own bridge and operation catalog. A project can use one host without connecting the others.
  • Model providers: local and configured connected providers are selectable separately from graph execution. Model choice does not change the saved pipeline or prove a host result.
  • Reasoning adapters: the domain package can add context, tools, validation, indexing, code understanding, and repair providers one at a time. See the customization guide.
  • Project roots: the primary project, installed tools/, and user-added folders contribute to search. Adding a folder indexes it; it does not install a host bridge or grant a license.

Find available features in your build

In the desktop UI, use Apps > Capability Status... for live host state, Search / Symbols for indexed project code, and the Pipeline function picker for node candidates. Check a candidate's source and required inputs before adding it. The Help guide's search can find documented controls and bundled vendor API names; vendor links are references, not executable nodes.

An unlocked Python API session offers read-only inspection:

from tech_connector.api import create_api

api = create_api(project_root="C:/your-project")
surface = api.surface()                  # public API operations
features = api.features.search("asset")  # feature registry matches
wrappers = api.dcc.catalog()             # bundled DCC wrappers
maya_names = api.dcc.reference_search("selection", host="maya")

Use api.features.describe(feature_id, operation) for a selected operation, and api.dcc.native_catalog("maya") only after a Maya bridge is connected. The API reference explains these different catalogs.

Scripting and host API languages

Surface Language or API Practical boundary
Tech Connector scripts and headless API Python Public methods, project search, pipelines, and typed DCC calls.
Maya, Blender, Houdini, MotionBuilder, Substance Painter, 3ds Max Host Python APIs Native names and versions vary with the installed host and plugins. Inspect live callables where the Python bridge supports it.
Unreal Editor Unreal Python plus engine C++ reflection Python calls use the connected editor. C++ wrapper generation is preview-first and requires the appropriate plugin setup.
Unity Editor C# The Unity bridge is a separate integration; its C# API is not a Python native_catalog module.
Photoshop UXP JavaScript The Photoshop bridge is development-only in production until pairing is complete. The vendor API link is for lookup.
Game runtime C++ Native runtime code and platform integrations are distinct from desktop Python automation.

These are implementation and scripting languages, not a promise that every vendor method can be called across Tech Connector's bridge. Host objects may not serialize into a useful result. See native host APIs for discovery, call examples, and vendor references.

Interface languages

The current desktop guide documents English UI labels. Do not assume a translated desktop interface from a host API language or from the mobile client's language selector. The mobile client contains language choices, but individual screens and messages need separate translation review before a language can be described as fully localized.

Add a module or application

For a studio-specific reasoning component, extend one domain-package adapter as shown in the customization guide. For a new DCC or art program, start with the add a host guide: it separates a docs-aware app from a connected, tested bridge.