Intrinsic SDK

Project notes

Start with an accessible solution

This profile reviews release v1.37.20260928.1, commit 987e6298c3a04fbd9a03a5a284c5d04c2af9fd46. Its release notes provide a matching Bazel archive and development-container configuration. Use that versioned environment rather than combining an arbitrary client checkout with a different backend. The root README calls the SDK and Flowstate beta and says use of the repository requires Flowstate beta participation. The root license file supplies Apache-2.0 terms; the relationship between that license and the broader README condition is unresolved here. [1] [6] [7]

The Python entry point is intrinsic.solutions.deployments.connect. It can use a direct address or an organization and solution/cluster configuration; calling it without arguments reads the locally selected solution. The connection code checks backend health and raises errors when credentials, selection or a running solution are missing. A successfully installed Python package is therefore not evidence of a usable robot connection. [2]

Once connected, the returned solution exposes its world, skills and executive interfaces. Inspect the object-world client and select a read-only query before introducing mutations or execution into your application. The client source documents a threading constraint: a Solution and its descendants are not thread-safe, so separate threads need separate solution objects. [2] [3]

The companion SDK examples are learning resources for this interface, not additional standalone runtimes. This profile covers the released client source and release setup instructions only. We have not installed the environment, authenticated to Flowstate, executed a skill or established compatibility with a particular Intrinsic Core release. Third-party dependencies and hosted services retain their own terms. [1] [6] [7]