Tool

import

Import multiplies everything else. Once a source is in the graph, every tool reaches it with the same addresses and the same grammar as your own code — so a question can follow a call out of your service and into the library it depends on without changing tools or losing the thread.

import("github://dotnet/aspire") import("github://dotnet/[email protected]") # pinned to a tag import("sarif:///reports/roslyn.sarif") # lint findings, joinable in SQL

After the first of those, github://dotnet/aspire/** is an address like any other — readable, searchable, and joinable against your own code in a single query.

Run it yourself

rql import github://dotnet/aspire

Or say it to your agent

“import the aspire repo so we can compare it with ours”

Parameters

ParameterWhat it does
importUrirequiredThe source to import, in one of the forms below. Prefix with - to remove it.

What you can import

SourceWhat it pulls in
github://owner/repoA GitHub repository. Add @ref to pin a tag, branch, or commit.
git://host/pathAny git remote. https://host/path.git@ref, ssh://git@host/path, and git@host:path.git all work too.
s3://bucket/prefix/An S3 bucket, indexed in place and read-only. Large or binary objects are kept as searchable metadata.
local:///absolute/pathA folder on disk — or just .. Live-watched, never cloned, never modified.
sarif:///path.sarifA findings report from Roslyn, Snyk, SonarQube, or anything else that emits SARIF.
-github://owner/repoRemove an import and its indexed data. Local files are never touched.

How it behaves

This page names what exists. The depth behind every name — the bounds, the failure modes, how they compose — ships inside the binary at help:///, and answers to explore and read exactly like your code does. Install it, and your agent has the manual.