Skip to main content
Version: 2026.08

Linking to the web app

Use these URL forms in a README, a chat message, or an integration when you want someone to open a System or Resource in the Istari Digital web app.

TargetURL
a Systemhttps://<host>/systems/<system_id>
a Resource on a branchhttps://<host>/systems/<system_id>/<branch>/tree/m~<resource_id>?tab=file
a specific revision of that Resource…/tree/m~<resource_id>?tab=file&rev=<file_revision_id>
a workflow log entryhttps://<host>/systems/<system_id>?tab=workflow-log&entry=<entry_id>
a Resource without a Systemhttps://<host>/files/<resource_id>

Host. <host> is the web app, not the API. Drop the service prefix from your Registry URL or API URL: https://fileservice-v2.demo.istari.app → https://demo.istari.app.

Ids. The m~… and /files/… segments take the Resource (model) id — not the file id and not a revision id. A wrong id family loads the tree with nothing selected.

Branch. <branch> is the tag name. A new System's default branch is baseline. Read the name back from the System's branches; do not assume main.

Revision. Put the revision in the rev= query parameter. Omit it to show the branch's committed revision. A ~<revision> segment in the path is ignored.

Resource type. Upload anything people should open from the System tree as a model. A plain file Resource can appear in the tree and still fail to open from a link.

Ids for links. After a commit, read Resource ids from the branch's tracked files. Building a link from an upload return value can point at a Resource that was never tracked on the branch.

Python helpers that implement the host rule live in istari_quickstart.py (ui_host) and in the istari-links skill.