Interactive CLIVersion: 2.0.1Interactive Explorer168 commandsFlatTreetdkabout1aboutShow build metadata and system informationai4agentsinstallWrite the Tabsdata skill where your coding agents look for skills: the shared .agents/skills folder, which most agents read, and the folders of the agents found in your home that read only their own (Claude Code, Antigravity). It tells the agent when to propose Tabsdata, the rules it follows, and to load the skill of your server with 'tdk ai load-skill'. Copies already installed are brought up to date, and those in folders agents no longer use are removed. Rerun it after upgrading tdkstatusShow where the Tabsdata skill is installed, for which agents, which tdk wrote each copy and whether it is this tdk'suninstallRemove the Tabsdata skill from every folder coding agents read, old folders includedload-skillPrint the Tabsdata skill of the server a profile is logged in to, as markdown, for a coding agent to follow: the rules, how to work, the server's skills and the commands you can run. Without a login it names the login to run. It always exits 0auth7add-certAdd a certificate for a Tabsdata Server. Only needed for self-signed certificates.delete-certDelete a certificate for a Tabsdata ServerinfoDisplay information of the currently authenticated userpassword-changeChange the password of a user in a Tabsdata Serverservice-tokencreateCreate a service token in one of your two slots. The token is shown once, here, and cannot be recovered afterwards: the server keeps only a SHA-256 digest of it.listList your service tokens. `Last used` has a resolution of ten minutes, which is what the rotation runbook needs to tell a retired token from one still in production.revokeRevoke the service token in one of your slots. The slot becomes free for the next rotation, and the token stops working immediately.collection8createCreate a new collectiondeleteDelete a collection by namegetDisplay a collection by namelistList all collectionstagdeleteRemove a user taglistList the tags, system and usersetSet a user tag, replacing its value if the key is setupdateUpdate a collection by nameconnection10checkCheck that a collection's connection connects, as a server-side probe. A check that ran and could not connect exits 0 with 'ok: false' in its resultentitiesList the entities the last refresh of a collection's connection found. Match names with '--filter fqn:lk:GLOB', where '*' matches any textgetDisplay the catalog of a collection's connection: probe status, schema fingerprint and the compatible local connectorslistList the connections of source and destination collectionsprobeDisplay a connection proberefreshExplore a collection's connection again, as a server-side probe, and replace its catalog of entitiessampleRead sample rows of a catalog entity, as a server-side probe. The rows are kept on the server for ten minutes and the read is audit-loggedtemplatePrint a fill-in connection template for a connector typetypesList the connection types available from installed connectorsvalidateValidate a connection YAML document against its connector schemacron4disableDisable a cron-triggered function 'tdk fn disable' restricted to functions that have a cron trigger; disabling an already-disabled one does nothing.enableEnable a cron-triggered function 'tdk fn enable' restricted to functions that have a cron trigger; enabling an already-enabled one does nothing.listList the cron triggers of the projectplansList the execution plans the cron triggers started, newest firstdocs3listList the documented symbolssearchSearch symbol names, qualified names and summaries, best firstshowShow the reference page of a symboldoctor1doctorCheck that this machine is ready to develop and register functions. Exits 1 when any check fails; warnings do not failexamples5extractExtract an example into a directorylistList the bundled examples, optionally filteredpathPrint the absolute path of the examples directory, or of one examplescaffoldWrite the skeleton of a publisher, transformer or subscriber. The source or destination is built from the installed connector, with '<value>' placeholders for the values it needs; the function never names a connection, since the collection's connection is used on the server. Needs no servershowPrint an example: the source of a snippet, or the README and function files of a projectfn15bundleDownload, unpack or print the bundle of a function version. The bundle is addressed by its function version id (fvid), or by '--name' for the function's current version; only Active or Frozen versions can be read (a version whose function has been deleted is not found). It holds the code that actually runs: the whole module tree the function was registered with, and its requirements.checkCheck a function file before registering it. Runs the code of the '--path' file on this machine, since it imports it. Imports the function as 'tdk fn register' does, reports what it declares (kind, input and output tables, triggers, connector), builds its bundle and flags calls such as eval, exec or subprocess. Nothing is uploaded. Exits 1 when a finding is an error; warnings do not fail.deleteDelete a functiondisableDisables a function Disabling an already-disabled function does nothing.enableEnables a function Enabling an already-enabled function does nothing.getDisplay a functionlistList the functions of a collection, or of the whole projectpatchRegister a code-only patch of a function version. With '--path' or '--source', runs the code of that file on this machine, since it imports it. A patch shares the parent's topology (tables, dependencies, triggers, workers) — only bundle / snippet / runtime values / description can be overridden. With '--source', the patch is the bundle of '--fn-version' with only the module that defines the function replaced, so its sibling modules, its requirements and its local packages carry over ('--requirements' and '--local-pkg' replace them). A patch is the only way to change the code a planned run executes: both 'tdk fnrun replay' and 'tdk plan recover' / 'tdk fnrun recover' re-run the function version the plan pinned, picking up its latest patch. Registering a new version with 'tdk fn update' does not affect runs that are already planned.patchesList patch versions of a function (latest first).registerRegister a function. Runs the code of the '--path' file on this machine, since it imports it. Dynamically imports the symbol named by `--path` (which must be a tabsdatak `PublisherInfo` / `TransformerInfo` / `SubscriberInfo` produced by a `@publisher` / `@transformer` / `@subscriber` decorator) and registers it via the v2 bundle producer (`tabsdatak.common._archive.bundle.build_bundle`). With `--update`, behaves idempotently: if the function already exists in the collection it is updated; otherwise it is registered. With `--dry-run`, checks the function as 'tdk fn check --coll' does and reports what would be registered, uploading nothing.tagdeleteRemove a user taglistList the tags, system and usersetSet a user tag, replacing its value if the key is settriggerTrigger a function execution. It waits for the execution to finish with '--wait' and returns at once with '--no-wait'; with neither, the 'tdk set --trigger-wait true|false' setting decides (default: true).updateUpdate a function. With '--path', runs the code of that file on this machine, since it imports it. Dynamically imports the symbol named by `--path` (a tabsdatak `*Info` descriptor) and updates the existing function via the v2 bundle producer (`tabsdatak.common._archive.bundle.build_bundle`). The new version applies to runs planned from here on. Runs already planned keep the version they were planned with, so an update does not reach a stalled plan: to change the code such a run executes, patch its version with 'tdk fn patch'.fnrun6diagnoseDiagnose why a function run did not succeed: its repair handles, the error signature of its latest worker's log and, when it is on hold, the failed runs that block it. Exits 0 whenever the diagnosis is produced; a function run that is not found exits 5.getDisplay a function run: its details plus its workers.listList function runs across every project you can view.logsShow the logs of the function run's workers (one per attempt): every worker's with '--all', newest first; else one worker's, picked from the listing when several ran. Each worker that did not succeed carries the error signature of its log.recoverRecover the transaction a function run belongs to: the transaction's failed or on-hold function runs are re-scheduled, each re-running its pinned function version and that version's latest patch.replayRe-execute a finished function run. Mints a new concrete physical function run against the latest patch (or head, if no patch exists). The pointer stays bound to the previous attempt's outputs until the new attempt finishes successfully. '--wait' waits for the new attempt to end.group8createCreate a new groupdeleteDelete a group by name. System groups cannot be deleted.getDisplay a group by namelistList all groupstagdeleteRemove a user taglistList the tags, system and usersetSet a user tag, replacing its value if the key is setupdateUpdate a group by name. System groups cannot be updated.info3licenseShow the license of tabsdata.release-notesShow the release notes of the current version of tabsdata.third-partyShow the third-party dependencies of tabsdata.login1loginLogin to the Tabsdata Serverlogout1logoutLogout from the Tabsdata Server: the login stored here always goes; the server is asked to end the session, which otherwise expires on its ownmetrics2inflightPoint-in-time `/inflight` — non-terminal LFRs per (collection, group, status).showPer-collection (or per-group) operational summary over the window. Renders one row per `(dim_entity, status)` with `Runs / Tables in / Rows in / Tables out / Rows out` (bytes columns added when any non-zero). Edges are dropped from the rendering — they belong in a flow visualization; use `-o json` for the raw shape.permission3grantGrant a permission to a userlistList a user's permissions, or who has access to a projectrevokeRevoke a permission from a userplan7cancelCancel a plan: every non-committed transaction in it is canceled, and so is every non-committed transaction that read its output and every queued run of the same functions, in later plans too. Canceled runs cannot be recovered; the result lists every run canceled.diagnoseDiagnose why a plan did not succeed. Reports the failed and retrying function runs, first failure first, each with its repair handles (the replay, recover and patch argv) and the error signature of its latest worker's log; the held runs with the failed runs that block them; and the root cause, the earliest failure, with its category. Exits 0 whenever the diagnosis is produced; the verdict is the plan's 'health'. A plan that is not found exits 5.getDisplay a plan: its details plus its function runs and workers.listList plans across every project you can view.logsShow the logs of the plan's workers: every worker's with '--all', newest first; else one worker's, picked from the listing when several ran. Each worker that did not succeed carries the error signature of its log.monitorMonitor the execution of a plan until it finishes. Exits 7 when '--timeout' runs out and 8 when a function run did not succeed.recoverRecover a plan: its failed or on-hold function runs are re-scheduled, each re-running its pinned function version and that version's latest patch.project13createCreate a new projectdeleteDelete a project by name.getDisplay a project by namegraphShow the project's functions and tables and the edges between themlistList all projectssecretsList the secrets of a project, with their keys (never their values)tagdeleteRemove a user tagkeysList the tag keys open on the project's entitieslistList the tags, system and usersetSet a user tag, replacing its value if the key is setvaluesList the values a tag key is open with on the project's entitiestopologylistList the project's topology versions, each with when it was currentupdateUpdate a project by nameset1setGive a setting a value. Settings apply to every later invocation. The pinned project and collection are per profile: they belong to the profile the command runs under. Every other setting is global: one value for all profiles. 'tdk unset' drops them back to their default and 'tdk settings' shows them. More than one can be set at once. Examples: tdk set --hints false tdk set --prompt false tdk set --trigger-wait false # fn trigger returns at once tdk set --server http://127.0.0.1:2457 tdk set --server 127.0.0.1 # http://127.0.0.1:2457 tdk set --proj sales tdk set --proj sales --coll orders tdk set --profile dev # default profile for commands tdk set --profile dev --proj sales # ...and pin dev's projectsettings1settingsShow the current settings: the global ones, and the pinned project and collection of the profile the command runs under. The machine formats give the stored values and name that profile.shell1shellStart an interactive shell sessionstatus1statusCheck the status of the serverstream4disableDisable a stream-publisher function 'tdk fn disable' restricted to stream publishers; disabling an already-disabled one does nothing.enableEnable a stream-publisher function 'tdk fn enable' restricted to stream publishers; enabling an already-enabled one does nothing.listList the stream publishers of the projectplansList the execution plans the stream publishers started, newest firsttable13dataShow rows of data from the tabledeleteDelete a tablediffShow how a table's schema changed, or how it differs from another's. With no '--from' or '--against', lists the schema changes over the committed data versions, newest firstdownloadDownload the table as a parquet fileflowShow the functions and tables upstream and downstream of a tablelistList the tables of a collection, or of the whole projectprofileShow per-column null rates, distinct counts and ranges of a table. Exact by default: the server aggregates the whole data version. When the version is too large or the query times out, or with '--approx', the stats come from random windows and 'approximate' says soschemaShow table schemastatsShow the size and schema of a tabletagdeleteRemove a user taglistList the tags, system and usersetSet a user tag, replacing its value if the key is setversionsList the committed versions of the data of a table, newest first; the newest is marked 'latest'.trx6cancelCancel a transaction and its non-committed function runs, every non-committed transaction that read its output and every queued run of the same functions, in later plans too. Canceled runs cannot be recovered; the result lists every run canceled.getDisplay a transaction: its details plus its function runs and workers.listList transactions across every project you can view.logsShow the logs of the transaction's workers: every worker's with '--all', newest first; else one worker's, picked from the listing when several ran. Each worker that did not succeed carries the error signature of its log.monitorMonitor the execution of a transaction until it finishes. Exits 7 when '--timeout' runs out and 8 when a function run did not succeed.recoverRecover a transaction: its failed or on-hold function runs are re-scheduled, each re-running its pinned function version and that version's latest patch.unset1unsetDrop a setting back to its default. The counterpart of 'tdk set': it removes what was stored for every setting it is given, so the shipped default applies again. The pinned project and collection are per profile, every other setting is global. More than one can be unset at once. Examples: tdk unset --hints tdk unset --prompt tdk unset --trigger-wait tdk unset --server tdk unset --coll # unpin the collection only tdk unset --proj # unpins the collection too tdk unset --all # every setting, the profile's pins tdk unset --profile # back to the default profileuser5createCreate a new userdeleteDelete a user by namegetDisplay a user by namelistList all usersupdateUpdate a user by nameworker3listList workers across every project you can view.logsShow the logs of a worker, with the error signature of its log when it did not succeed.recoverRecover the transaction a worker belongs to: the transaction's failed or on-hold function runs are re-scheduled.tdkserverabout1aboutShow build metadata and system informationassess1assessCheck whether a tabsdata instance can be createdbanner1bannerShow Tabsdata bannerconfig4checkCheck the values still to be provided in the configs of a tabsdata instancegetDownload the configmaps of a tabsdata instance for editingputReplace the configmaps of a tabsdata instance from edited filesviewView the configmaps of a tabsdata instancecreate1createCreate a tabsdata instancedelete1deleteDelete the resources of a tabsdata instancehelp1helpShow the commands of tabsdata on kubernetesinfo3licenseShow the license of tabsdatarelease-notesShow the release notes of the current version of tabsdatathird-partyShow the third-party dependencies of tabsdatainit1initProduce an editable input config folder for a tabsdata instanceinspect1inspectShow the configuration and state of a tabsdata instancelist1listList registered tabsdata instancesquickstart1quickstartInitialize, create and start a tabsdata instance in one steprestart1restartRestart a tabsdata instanceset1setSet a session setting used when commands omit itsettings1settingsShow the tabsdata session settingsshell1shellOpen an interactive shell. The commands listed under it are entered at the shell prompt, not on the tdkserver command line.start1startStart a tabsdata instancestatus1statusShow the running workloads of a tabsdata instancestop1stopStop a tabsdata instancestubs1stubsCopy the configuration stubs for '--config', and the project secrets stub, into the tabsdata home foldertrash1trashTrash a local kminus tabsdata instanceunset1unsetUnset a session settingupgrade1upgradeUpgrade a tabsdata instance to the running tabsdata versionvenv2listList the tabsdata virtual environmentsupdateUpdate the complementary packages of a tabsdata virtual environmentabouttdk aboutShow build metadata and system informationtdk about \ --format table \ --profile production-o, --formattable | json | yamloptional--profilestringoptional