Skip to content
Trigora

Search docs by title or keyword.
    Product Docs Pricing Research Blog GitHub Start building →
    Start building →

    Engine-native primitives

    The two authoring surfaces serve different runtimes:

    @trigora/sdk
    → Programs for Trigora Cloud and trigora dev
    

    Engine-native primitives
    → artifacts you run on an embedded TCC host

    effect, waitForEvent, sleep, and invoke in @trigora/sdk are the Trigora programming model. The engine identifies durable operations from the frontend’s resolved imports, not from a function that happens to share a name.

    For an embedded-engine integration, use the primitive package documented in tcc-engine. @trigora/client can connect to a custom host only if that host separately implements the Trigora HTTP API, including /v1/executions. The TCC host protocol and the Trigora HTTP API are distinct interfaces. See Host protocol.