@xano/sdk 1.0.13 → 1.0.15

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (246) hide show
  1. package/CHANGELOG.md +28 -0
  2. package/README.md +28 -28
  3. package/dist/.build-fingerprint +1 -1
  4. package/dist/{agent-file-refresh-DAFGNMQX.js → agent-file-refresh-ZRGNOA6Q.js} +12 -11
  5. package/dist/{agent-skill-command-6M46ZGOL.js → agent-skill-command-DV26SDA2.js} +51 -50
  6. package/dist/{answer-shape-CBUQRSXI.js → answer-shape-AVZSKBR6.js} +4 -4
  7. package/dist/{backend-dir-J2J7JNS6.js → backend-dir-NTMXWE5R.js} +11 -10
  8. package/dist/{backend-slot-X5AUX2TT.js → backend-slot-DZAUHLTS.js} +3 -3
  9. package/dist/bin.js +47 -46
  10. package/dist/{branch-YS2K3VOB.js → branch-IJTBZZFO.js} +8 -8
  11. package/dist/{branch-commands-BUKVE637.js → branch-commands-4PJEBNRK.js} +26 -25
  12. package/dist/{chunk-PCHIHVX6.js → chunk-2LF734YB.js} +4 -4
  13. package/dist/{chunk-ENBGJJJH.js → chunk-3GZMP7II.js} +9 -9
  14. package/dist/{chunk-R7XZW4SB.js → chunk-3H7R4ISR.js} +2 -2
  15. package/dist/{chunk-DB7P2SSK.js → chunk-45K2QZBR.js} +3 -3
  16. package/dist/{chunk-C2SAVXAB.js → chunk-4MX5LMPQ.js} +2 -2
  17. package/dist/{chunk-IZI3SYXH.js → chunk-5FJ4M4HB.js} +38 -38
  18. package/dist/{chunk-FBWMKHLO.js → chunk-5SJQAJLF.js} +3 -3
  19. package/dist/{chunk-E763QI3G.js → chunk-5SKWGCAJ.js} +2 -2
  20. package/dist/{chunk-JKGRQW6D.js → chunk-5W7S2SCA.js} +4 -4
  21. package/dist/{chunk-KICERNAP.js → chunk-66ZU2CD5.js} +4 -4
  22. package/dist/{chunk-F2NFNYCB.js → chunk-6EFXPTHT.js} +3 -3
  23. package/dist/{chunk-CTUIMNEM.js → chunk-6X73VFCX.js} +2 -2
  24. package/dist/{chunk-VTMTIBKP.js → chunk-74OPNM2Z.js} +2 -2
  25. package/dist/{chunk-DZUNF7IH.js → chunk-75QC66XI.js} +2 -2
  26. package/dist/{chunk-U4BGBU3R.js → chunk-7AKH4QDJ.js} +44 -44
  27. package/dist/{chunk-CGZSF756.js → chunk-7ZQ73AHJ.js} +28 -28
  28. package/dist/{chunk-5SMUND4J.js → chunk-A2N2C2WD.js} +6 -6
  29. package/dist/{chunk-XL7EA62X.js → chunk-AE5CRAKS.js} +5 -5
  30. package/dist/{chunk-5ONWBQ2C.js → chunk-ASQX477B.js} +7 -7
  31. package/dist/{chunk-JFPLHK6Y.js → chunk-AXMUYBWQ.js} +2 -2
  32. package/dist/{chunk-5XDKKE5Y.js → chunk-B6AFJVG4.js} +4 -4
  33. package/dist/{chunk-4CS4DKQC.js → chunk-BEKEOXNG.js} +2 -2
  34. package/dist/{chunk-ZSMHS7BU.js → chunk-CJGLAQRD.js} +4 -4
  35. package/dist/{chunk-M7DIIJPW.js → chunk-DBDTQR23.js} +4 -4
  36. package/dist/{chunk-RZABQ4YH.js → chunk-DGYXCIBV.js} +4 -4
  37. package/dist/{chunk-P6HXDOFG.js → chunk-DH6O5NQU.js} +13 -13
  38. package/dist/{chunk-I2AVVARA.js → chunk-ECQXASG3.js} +2 -2
  39. package/dist/{chunk-2BHYGUTI.js → chunk-EQXHUWUO.js} +2 -2
  40. package/dist/{chunk-EGEANMMK.js → chunk-FIERONKM.js} +2 -2
  41. package/dist/{chunk-A2AOUBJS.js → chunk-FKQX6KU7.js} +3 -2
  42. package/dist/{chunk-UECNKDDA.js → chunk-FOBVJ2UR.js} +8 -8
  43. package/dist/{chunk-GRWYO2MS.js → chunk-FXZEZAV2.js} +3 -3
  44. package/dist/{chunk-H6VVSGKN.js → chunk-G4WRZU5T.js} +7 -7
  45. package/dist/{chunk-K6BQPFRS.js → chunk-GBSHHNSD.js} +3 -3
  46. package/dist/{chunk-N3XSXGAL.js → chunk-GCINMMFL.js} +2 -2
  47. package/dist/{chunk-WZXEQUIM.js → chunk-GDJCWQIK.js} +2 -2
  48. package/dist/{chunk-ZACMAKZE.js → chunk-GIQIMWTK.js} +14 -14
  49. package/dist/{chunk-POZ6V4MU.js → chunk-GKQTXUOW.js} +2 -2
  50. package/dist/{chunk-D4VKPOD4.js → chunk-GRXX2TOJ.js} +13 -112
  51. package/dist/{chunk-YJK4NPXC.js → chunk-GVHWIDEJ.js} +3 -3
  52. package/dist/{chunk-UKC65HBQ.js → chunk-HCNIB3EC.js} +4 -4
  53. package/dist/{chunk-DILYWJVP.js → chunk-HXFLHA5K.js} +2 -2
  54. package/dist/{chunk-FLDFKG24.js → chunk-IKXXTRMN.js} +4 -4
  55. package/dist/{chunk-QWWQM4XZ.js → chunk-JAYHFXWH.js} +7 -7
  56. package/dist/{chunk-6LECAG3Y.js → chunk-JWASCOHO.js} +4 -4
  57. package/dist/{chunk-DPSR5GRE.js → chunk-K6SWZ6H4.js} +49 -49
  58. package/dist/{chunk-VA4JK4TW.js → chunk-KMKUH2IO.js} +3 -3
  59. package/dist/{chunk-UFFIU57H.js → chunk-LSJ3SQEU.js} +4 -4
  60. package/dist/{chunk-JHQAVWHW.js → chunk-M7O3T7IM.js} +2 -2
  61. package/dist/{chunk-BXVNRUDB.js → chunk-MGG4CHO4.js} +3 -3
  62. package/dist/{chunk-7NNLRNXE.js → chunk-MIS6F4HM.js} +4 -4
  63. package/dist/{chunk-6HTXQAMG.js → chunk-N72XNQNJ.js} +14 -14
  64. package/dist/{chunk-H7GMGZHI.js → chunk-NDV6CBR7.js} +2 -2
  65. package/dist/{chunk-6OOZJQJK.js → chunk-NNI5R6V6.js} +68 -68
  66. package/dist/{chunk-IFXPHVPY.js → chunk-NPYYDTXS.js} +3 -3
  67. package/dist/{chunk-DYGRTWAI.js → chunk-O44MJTLR.js} +3 -3
  68. package/dist/{chunk-HDANNK4A.js → chunk-OZWAITII.js} +9 -9
  69. package/dist/{chunk-ONNSFD73.js → chunk-P7GKTV7N.js} +10 -10
  70. package/dist/{chunk-373AVIL2.js → chunk-QAEBBTYR.js} +7 -7
  71. package/dist/{chunk-3ZVSOZZC.js → chunk-QRMKQYCB.js} +2 -2
  72. package/dist/{chunk-TANWE2ZY.js → chunk-QW7NGUYW.js} +80 -80
  73. package/dist/{chunk-U4DSFCH5.js → chunk-R3GPRNBT.js} +2 -2
  74. package/dist/{chunk-SBS2IYTN.js → chunk-RBTZEHXF.js} +3 -3
  75. package/dist/{chunk-XFQAA2SU.js → chunk-RVAEPPRH.js} +2 -2
  76. package/dist/{chunk-W5MKVFBQ.js → chunk-RXNMZM6H.js} +5 -5
  77. package/dist/{chunk-6QJORUHC.js → chunk-RYWNNJK5.js} +2 -2
  78. package/dist/{chunk-NZ7ML6LG.js → chunk-SH4RY6QX.js} +290 -98
  79. package/dist/{chunk-ZGNWMGN3.js → chunk-SHHXLI2K.js} +26 -8
  80. package/dist/{chunk-MLKJUEG3.js → chunk-SL55XKVL.js} +23 -23
  81. package/dist/{chunk-H5FAYLCR.js → chunk-SPLRKCFV.js} +2 -2
  82. package/dist/{chunk-XYVPF63S.js → chunk-SXMZNSQ6.js} +8 -8
  83. package/dist/{chunk-NMHTB346.js → chunk-TT6LN55R.js} +36 -10
  84. package/dist/{chunk-B5N6EWOM.js → chunk-TXFOQZUQ.js} +3 -3
  85. package/dist/{chunk-VFRL4G72.js → chunk-UNFQN3TT.js} +3 -3
  86. package/dist/{chunk-EKS7SAZS.js → chunk-UVHSMANV.js} +53 -61
  87. package/dist/{chunk-RQHXYL77.js → chunk-V7WCTXEH.js} +5 -7
  88. package/dist/{chunk-HEMWBHQS.js → chunk-VUWR5YLE.js} +13 -13
  89. package/dist/{chunk-O6PWEJUV.js → chunk-VXHXSGPU.js} +8 -8
  90. package/dist/chunk-VYJYDMY6.js +9 -0
  91. package/dist/{chunk-C4TZP5PQ.js → chunk-WS2X5BB2.js} +5 -5
  92. package/dist/{chunk-P5JF3U65.js → chunk-WS4BA75E.js} +37 -4
  93. package/dist/{chunk-HUEFVPYW.js → chunk-WXKSB2N3.js} +3 -3
  94. package/dist/{chunk-DFCYAEBE.js → chunk-XLP4CNSF.js} +3 -3
  95. package/dist/{chunk-OCNTMJSY.js → chunk-XPSDDTUZ.js} +3 -3
  96. package/dist/{chunk-OBRMA2VK.js → chunk-XY4OBD26.js} +3 -3
  97. package/dist/{chunk-XVOODRNK.js → chunk-Y5XAPLZS.js} +4 -4
  98. package/dist/{chunk-ZISPEBNM.js → chunk-YCKKL5PD.js} +60 -55
  99. package/dist/{chunk-XM56DAM7.js → chunk-YR3MNGWZ.js} +8 -8
  100. package/dist/{chunk-WQZCFVAD.js → chunk-ZC6H2ERE.js} +5 -5
  101. package/dist/{chunk-UDCKYLBW.js → chunk-ZDVVIJPU.js} +4 -4
  102. package/dist/{chunk-ENAUSLMP.js → chunk-ZF2CBXT5.js} +3 -3
  103. package/dist/{chunk-AUYXBKGR.js → chunk-ZOHEHIFS.js} +2 -2
  104. package/dist/{chunk-3RZ4UJWV.js → chunk-ZPJXWMHK.js} +4 -4
  105. package/dist/{chunk-A3CT26GX.js → chunk-ZRXDPCMN.js} +2 -2
  106. package/dist/{chunk-RAGFXELQ.js → chunk-ZYECXDVV.js} +5 -5
  107. package/dist/cli.js +45 -44
  108. package/dist/{codegen-command-BAFON45M.js → codegen-command-RDD4GL35.js} +63 -62
  109. package/dist/codegen.js +2 -2
  110. package/dist/{commands-IFRAGWGK.js → commands-5ILSWDSV.js} +2 -2
  111. package/dist/{completion-RTXCODHS.js → completion-UNKBVVDT.js} +2 -2
  112. package/dist/{config-EHFXNFSP.js → config-NTOASFCA.js} +3 -3
  113. package/dist/{deploy-command-JW7R3BPW.js → deploy-command-BYAZZF37.js} +52 -51
  114. package/dist/{deploy-source-ZUPLAL7L.js → deploy-source-QCPZWNJO.js} +27 -26
  115. package/dist/{dev-env-sync-W7OTV7OD.js → dev-env-sync-6MHK3UHC.js} +46 -45
  116. package/dist/{display-name-hint-BKPMISQU.js → display-name-hint-MYXCCAOP.js} +10 -10
  117. package/dist/{env-example-refresh-TS7WBVZQ.js → env-example-refresh-MQWHY7ZS.js} +64 -63
  118. package/dist/{env-pull-command-5IYXQ2WK.js → env-pull-command-KUIEKBTM.js} +42 -41
  119. package/dist/{env-target-TQBPLU2S.js → env-target-Y77RLRS5.js} +9 -9
  120. package/dist/{env-var-command-AKCWYZPB.js → env-var-command-BZWJD75C.js} +37 -36
  121. package/dist/{ephemeral-CART6DIR.js → ephemeral-VLPRDNEJ.js} +8 -8
  122. package/dist/{ephemeral-command-SJYH6XRS.js → ephemeral-command-SYKDPALW.js} +43 -42
  123. package/dist/{ephemeral-state-HPKSKC4Y.js → ephemeral-state-RUOU2GFS.js} +7 -7
  124. package/dist/{generate-command-FSCFZPOJ.js → generate-command-CSQDQZSW.js} +68 -67
  125. package/dist/{gitignore-6IJ66XME.js → gitignore-OQGYM7DO.js} +15 -14
  126. package/dist/{guards-RU4C7TFG.js → guards-JUYBDLZY.js} +6 -6
  127. package/dist/{impersonate-command-IH4HMSS3.js → impersonate-command-HSFCZBV6.js} +33 -32
  128. package/dist/{import-RUBCGLCA.js → import-T4ZTOTBT.js} +4 -4
  129. package/dist/index.d.ts +105 -109
  130. package/dist/index.js +11 -11
  131. package/dist/{init-command-STB4YSAK.js → init-command-6Z7QNVDY.js} +50 -51
  132. package/dist/{init-modules-YIZYPCMM.js → init-modules-BL2SR5RK.js} +7 -7
  133. package/dist/{init-web-OGKACAOC.js → init-web-DYE2FEXL.js} +2 -2
  134. package/dist/internal.d.ts +2 -2
  135. package/dist/internal.js +68 -62
  136. package/dist/{keep-data-merge-VRKS64JK.js → keep-data-merge-SHF75FC7.js} +24 -24
  137. package/dist/{lambda-config-reconcile-FXPDH2U5.js → lambda-config-reconcile-VOBVZPWS.js} +3 -3
  138. package/dist/{landing-record-5EFK7RI6.js → landing-record-7EOLEKH3.js} +17 -16
  139. package/dist/{live-diff-HARRGFV4.js → live-diff-M2OLXKM6.js} +6 -6
  140. package/dist/{local-engine-choice-TRTEJVMV.js → local-engine-choice-TOC3UYZZ.js} +30 -29
  141. package/dist/{local-engine-command-2FK2PE2P.js → local-engine-command-6KSRDZBR.js} +35 -34
  142. package/dist/{local-engine-deploy-ZZVHBI2X.js → local-engine-deploy-4N4NFZ4T.js} +11 -11
  143. package/dist/{local-engine-lookup-QFRKO35F.js → local-engine-lookup-AQTUGSBT.js} +2 -2
  144. package/dist/{local-engine-mcp-bridge-T2EFRRAF.js → local-engine-mcp-bridge-AMYRH4SY.js} +9 -9
  145. package/dist/{local-engine-mcp-command-FB7EOGG6.js → local-engine-mcp-command-XTP3EATV.js} +41 -48
  146. package/dist/{local-engine-process-XH35DURU.js → local-engine-process-OD5OSWDG.js} +6 -6
  147. package/dist/{local-engine-update-check-HAXE7BVG.js → local-engine-update-check-G3YCBXRE.js} +4 -4
  148. package/dist/{lock-commands-7PBZIRWR.js → lock-commands-437P6BHY.js} +50 -49
  149. package/dist/{login-command-2O6GRMTH.js → login-command-BNRDAVFV.js} +23 -22
  150. package/dist/{logout-command-RZXGW3O2.js → logout-command-FCGCHB7Y.js} +13 -12
  151. package/dist/{loop-QHZD37KX.js → loop-WOAEXMTC.js} +6 -6
  152. package/dist/{marketplace-command-NCMLGIMS.js → marketplace-command-SUBJZPJV.js} +33 -33
  153. package/dist/{marketplace-resolve-HPCRNV5O.js → marketplace-resolve-JR4BBJ6K.js} +5 -5
  154. package/dist/{meta-client-DYYM5F5G.js → meta-client-AYJS3RQ3.js} +10 -10
  155. package/dist/{module-manifest-EFE6JBZW.js → module-manifest-63I5GRK4.js} +3 -3
  156. package/dist/node.d.ts +2 -2
  157. package/dist/node.js +50 -49
  158. package/dist/{operation-outcome-SHNROAFA.js → operation-outcome-ORQPVJKB.js} +19 -19
  159. package/dist/{output-target-PSSR3E4N.js → output-target-KNHHNDM3.js} +16 -15
  160. package/dist/{plan-disclosure-WEMB5ZJ2.js → plan-disclosure-4DUFRGCP.js} +16 -16
  161. package/dist/{plugin-contributions-U5PAZKBE.js → plugin-contributions-YYEP7IWH.js} +4 -4
  162. package/dist/{plugin-prompt-O5PAMV5B.js → plugin-prompt-GKCQKNYI.js} +4 -4
  163. package/dist/{plugin-questions-ZVYNKDRB.js → plugin-questions-P7MA3TYI.js} +3 -3
  164. package/dist/{preflight-command-6F7JF3YQ.js → preflight-command-32GFVKSN.js} +56 -55
  165. package/dist/{profile-command-5AOGD6GV.js → profile-command-U2XTKOMF.js} +24 -23
  166. package/dist/{profile-pointer-VTOZDBHM.js → profile-pointer-JJ7K5O2R.js} +3 -3
  167. package/dist/{project-dependency-EZNTHMWI.js → project-dependency-X3KCWBK5.js} +6 -6
  168. package/dist/{project-sdk-ZGJM4WYQ.js → project-sdk-YHJZRCNB.js} +3 -3
  169. package/dist/promote-command-OO56IZBT.js +148 -0
  170. package/dist/{prompt-F7UVH4GP.js → prompt-QNMJIWNI.js} +3 -3
  171. package/dist/{publish-command-6VVSJPLI.js → publish-command-5ZVZ6IYT.js} +55 -54
  172. package/dist/{pull-command-GE2WUEUF.js → pull-command-LT5PCEIW.js} +66 -65
  173. package/dist/{pull-superseded-77UZ7CHH.js → pull-superseded-6HADGGC5.js} +3 -3
  174. package/dist/{release-command-55RTR674.js → release-command-RBUOXIH7.js} +60 -59
  175. package/dist/{release-ns-command-5XPZ2B6N.js → release-ns-command-LDN5DOKQ.js} +78 -77
  176. package/dist/{retry-command-S5QALD5Z.js → retry-command-LFZYEVRU.js} +7 -7
  177. package/dist/{routes-manifest-ET2TTSCL.js → routes-manifest-BMAOL6WN.js} +6 -6
  178. package/dist/{routes-manifest-file-42FTJHRY.js → routes-manifest-file-MPOVKD6N.js} +9 -9
  179. package/dist/scaffold.d.ts +0 -5
  180. package/dist/scaffold.js +2 -2
  181. package/dist/{secrets-file-N5IF265R.js → secrets-file-7QM3ORGX.js} +15 -14
  182. package/dist/{secrets-fill-command-35WKBURT.js → secrets-fill-command-OZ537VOD.js} +49 -48
  183. package/dist/{seed-5YLQRT2D.js → seed-ATGBOEJP.js} +6 -6
  184. package/dist/{source-resolve-JXGOVJD3.js → source-resolve-QYSWA3QR.js} +17 -17
  185. package/dist/{static-host-TQP3FXPI.js → static-host-MO4VDHL7.js} +4 -4
  186. package/dist/{status-command-G3DFRMU7.js → status-command-IEB4K7ME.js} +60 -34
  187. package/dist/{store-ZE5BXCOW.js → store-AJX4MC7Y.js} +5 -5
  188. package/dist/{store-BM7SQcUt.d.ts → store-DspGMsFY.d.ts} +112 -118
  189. package/dist/{sync-baseline-JGAAOS25.js → sync-baseline-IB7MABZO.js} +7 -7
  190. package/dist/{sync-contributions-7T4CSPVQ.js → sync-contributions-DLV5JZUK.js} +8 -8
  191. package/dist/{sync-record-ILWS44DG.js → sync-record-NE62ERA3.js} +9 -9
  192. package/dist/{table-V3LTQUY6.js → table-TFD4ZQXA.js} +8 -8
  193. package/dist/{tables-command-7NUOZBHX.js → tables-command-IMCVPUFY.js} +35 -34
  194. package/dist/{tenant-7WUS7Q6V.js → tenant-IIYECNWO.js} +9 -9
  195. package/dist/{tenant-command-JGEHRKN7.js → tenant-command-77KG76MU.js} +83 -82
  196. package/dist/{test-command-2LNEA6GK.js → test-command-NSPU4RUO.js} +32 -31
  197. package/dist/{tests-ENFUACKD.js → tests-JWQRHFCT.js} +5 -5
  198. package/dist/{token-DWNH44NW.js → token-BDHD7GU3.js} +9 -8
  199. package/dist/{toolchain-hooks-QIFGPGH2.js → toolchain-hooks-QHJRDCRW.js} +8 -8
  200. package/dist/{toolchain-modules-F4DUMWTO.js → toolchain-modules-LY7BMYG6.js} +4 -4
  201. package/dist/{toolchain-peers-K44IINPG.js → toolchain-peers-FQJBTKEB.js} +7 -7
  202. package/dist/{tracked-backend-ZFXVLBBJ.js → tracked-backend-BIR7YJCE.js} +30 -29
  203. package/dist/{update-check-KBHT63GJ.js → update-check-JDARCXAX.js} +48 -47
  204. package/dist/{upgrade-command-CI543AZP.js → upgrade-command-YCADQCIA.js} +51 -50
  205. package/dist/{whoami-command-77DXENWD.js → whoami-command-IZCTUPM4.js} +12 -11
  206. package/dist/{workspace-RI5C77BZ.js → workspace-TK52V7WO.js} +4 -4
  207. package/dist/{workspace-binding-PR57NBGH.js → workspace-binding-3UT6PP4B.js} +11 -10
  208. package/dist/{workspace-command-6HHVFQKW.js → workspace-command-46OCB6XT.js} +79 -78
  209. package/dist/{workspace-env-2APJEASO.js → workspace-env-PVPOWFNZ.js} +12 -11
  210. package/dist/{workspace-export-GHMUSX2P.js → workspace-export-PUEXKZNS.js} +4 -4
  211. package/dist/{writable-Y6CE2CGK.js → writable-LMMG4AFZ.js} +3 -3
  212. package/dist/{xano-2A2GT7EH.js → xano-EOUVXNQX.js} +7 -7
  213. package/dist/{xanosdk-import-HBQH3ZBS.js → xanosdk-import-XXJT365U.js} +5 -5
  214. package/dist/{xanosdk-project-W45IR3Q7.js → xanosdk-project-CJKRLQ6U.js} +13 -12
  215. package/guides/README.md +3 -3
  216. package/guides/authoring.md +11 -11
  217. package/guides/bundle.md +2 -2
  218. package/guides/cli.md +179 -176
  219. package/guides/codegen.md +17 -17
  220. package/guides/codes.md +3 -3
  221. package/guides/coverage.md +2 -2
  222. package/guides/deploying.md +123 -123
  223. package/guides/environment.md +30 -30
  224. package/guides/marketplace.md +24 -24
  225. package/guides/module-contract.md +9 -9
  226. package/guides/object-kinds.md +4 -4
  227. package/guides/project-structure.md +4 -4
  228. package/guides/scaffold.md +22 -22
  229. package/guides/typed-frontend.md +3 -3
  230. package/llms/client.md +4 -4
  231. package/llms/errors.md +2 -2
  232. package/llms/fields.md +1 -1
  233. package/llms/kinds-agent-mcp.md +1 -1
  234. package/llms/kinds-realtime.md +2 -2
  235. package/llms/lock.md +3 -3
  236. package/llms/statements-calls.md +1 -1
  237. package/llms/statements-catalog.md +57 -57
  238. package/llms/statements-runtime.md +2 -2
  239. package/llms/tests.md +3 -3
  240. package/llms/toolchain.md +2 -2
  241. package/llms-full.txt +113 -110
  242. package/llms.txt +35 -32
  243. package/manifest.json +82 -152
  244. package/package.json +1 -1
  245. package/skills/xano-backend/SKILL.md +7 -7
  246. package/dist/promote-command-O2NRRFLK.js +0 -147
@@ -4,7 +4,7 @@ Authentication, ephemeral environments, static hosting, releasing to production,
4
4
 
5
5
  ## Signing in & deploying (in depth)
6
6
 
7
- **Sign in once** with `xanosdk login`. It runs the standard authorization-code + PKCE
7
+ **Sign in once** with `npx @xano/sdk login`. It runs the standard authorization-code + PKCE
8
8
  browser flow (powered by the OpenID-certified [`openid-client`](https://github.com/panva/openid-client)):
9
9
  opens your browser, you approve, and the CLI captures the redirect on a `127.0.0.1`
10
10
  callback. On first use it dynamically registers its own OAuth client (RFC 7591) so the
@@ -15,20 +15,20 @@ read from the token's own `aud` claim.
15
15
  `login` also **pins the numeric workspace** you consented to into the credential, so every
16
16
  later command acts on exactly that workspace without looking it up again. There is **no
17
17
  `--workspace` flag** — a credential addresses exactly one instance and one workspace. Run
18
- `xanosdk workspace details` to see which.
18
+ `npx @xano/sdk workspace details` to see which.
19
19
 
20
20
  The credential caches by default in a **shared** `~/.xanosdk/auth.json`, reusable
21
- from **any** project directory — so a single `xanosdk login` covers all your projects.
21
+ from **any** project directory — so a single `npx @xano/sdk login` covers all your projects.
22
22
  Override the OAuth host with `--origin`/`$XANO_ORIGIN` and the loopback port with `--port`.
23
23
 
24
24
  **Named profiles.** That file holds any number of credentials, each under a name.
25
- `xanosdk login --profile staging` adds one without touching the others; `--profile <name>`
25
+ `npx @xano/sdk login --profile staging` adds one without touching the others; `--profile <name>`
26
26
  (or `-p`) selects one for a single command. See [Credential profiles](#credential-profiles)
27
27
  below.
28
28
 
29
29
  **When the browser can't reach this machine** — a remote shell, a container, a
30
30
  Codespace — the `127.0.0.1` redirect lands nowhere and `login` waits five minutes for a
31
- callback that will never arrive. Run `xanosdk login --paste` instead. It binds nothing:
31
+ callback that will never arrive. Run `npx @xano/sdk login --paste` instead. It binds nothing:
32
32
  it prints the authorize URL, you finish signing in in whatever browser you have, and
33
33
  your browser then fails to load the `127.0.0.1` callback — which is expected. Paste that
34
34
  URL back from the address bar (or just the `code=` value out of it) and the sign-in
@@ -54,14 +54,14 @@ already has `prod` proceeds to consent: the guard is per profile, not per file.
54
54
  `auth.json` holds a map of **named profiles** under a versioned envelope. Each profile is
55
55
  one credential — one instance, one workspace — in one of two shapes:
56
56
 
57
- - **`oauth`** — written by `xanosdk login`. Refreshes and rotates. Do not hand-edit.
57
+ - **`oauth`** — written by `npx @xano/sdk login`. Refreshes and rotates. Do not hand-edit.
58
58
  - **`token`** — a meta API bearer token for the same meta APIs, for automation. No login
59
- flow, no refresh, no rotation. Store one with `xanosdk profile add <name> --instance <url>
59
+ flow, no refresh, no rotation. Store one with `npx @xano/sdk profile add <name> --instance <url>
60
60
  --workspace-id <n>`, which prompts for the token (or reads it piped on stdin) rather than
61
61
  taking it as a flag (a secret on a command line lands in the process list and the shell
62
62
  history), and checks it against the instance before storing it. The token
63
- itself stays valid until you revoke it wherever you minted it — `xanosdk logout` and
64
- `xanosdk profile delete` only remove the CLI's copy.
63
+ itself stays valid until you revoke it wherever you minted it — `npx @xano/sdk logout` and
64
+ `npx @xano/sdk profile delete` only remove the CLI's copy.
65
65
 
66
66
  Both shapes work at **either** location (project-local `./.xano/auth.json` or global
67
67
  `~/.xanosdk/auth.json`) on the same file precedence ladder below.
@@ -71,15 +71,15 @@ Both shapes work at **either** location (project-local `./.xano/auth.json` or gl
71
71
  1. `--profile <name>` / `-p <name>` on the command line.
72
72
  2. `xano.profile.json` at the project root — a committed, secret-free pointer naming one
73
73
  profile, found by walking up from the working directory and stopping at the first
74
- `package.json`. Write it with `xanosdk profile use <name>`. Nothing ambient outranks it:
74
+ `package.json`. Write it with `npx @xano/sdk profile use <name>`. Nothing ambient outranks it:
75
75
  a `$XANO_PROFILE` left in a shell rc cannot retarget a pinned project.
76
76
  3. `$XANO_PROFILE`.
77
- 4. The credential file's own `default` key. Set it with `xanosdk profile set-default <name>`.
77
+ 4. The credential file's own `default` key. Set it with `npx @xano/sdk profile set-default <name>`.
78
78
  5. The literal name `default`.
79
79
 
80
- `xanosdk profile use` pins **this project**; `xanosdk profile set-default` changes **this
81
- machine**. `xanosdk profile list` shows every profile with the default and the active one
82
- marked, and `xanosdk whoami` and `xanosdk status` both report which profile is in play and
80
+ `npx @xano/sdk profile use` pins **this project**; `npx @xano/sdk profile set-default` changes **this
81
+ machine**. `npx @xano/sdk profile list` shows every profile with the default and the active one
82
+ marked, and `npx @xano/sdk whoami` and `npx @xano/sdk status` both report which profile is in play and
83
83
  which rung chose it.
84
84
 
85
85
  Writes are serialised on a lock and merge one profile at a time, so signing in, signing
@@ -97,7 +97,7 @@ as a fallback**: it uses `./.xano/auth.json` when present, otherwise `~/.xanosdk
97
97
  so a `--local-auth` project keeps working without repeating the flag. `login` and `logout` do
98
98
  **not** fall back: they target the shared global cache unless you pass `--local-auth`. A `logout`
99
99
  naming a profile that only `./.xano/auth.json` holds exits 8 (not found in the shared file)
100
- and names `xanosdk logout --local-auth -p <name>` — it does not report the session as gone. A
100
+ and names `npx @xano/sdk logout --local-auth -p <name>` — it does not report the session as gone. A
101
101
  logout clears stored profiles only: with the `XANO_*` credential variables still set, it
102
102
  says so, and commands keep authenticating with them. An explicit
103
103
  `--config`/`$XANO_CONFIG` wins over both default file locations; only the three-variable
@@ -131,15 +131,15 @@ Present only when they apply: `engine` (in place of `ephemeral`), `keepDataSkipp
131
131
  merge lists (see [Keeping your data between deploys](#keeping-your-data-between-deploys)),
132
132
  `static` (`url`; `canonical`, the build's identity, and `verified` when the frontend was
133
133
  confirmed live serving it; `staticEnv` — `{ injected, keys, documents, skipped?, reason? }` — when config was
134
- injected; or `error` with `retry`, the `xanosdk publish` that retries only the static step),
134
+ injected; or `error` with `retry`, the `npx @xano/sdk publish` that retries only the static step),
135
135
  `microservices` (or `microservicesError`, `{ message, remedy }`, when their status could not be
136
136
  read after the deploy), `testRun` (`total` — the whole suite, `passed + failed + notRun` —
137
137
  `passed`, `failed`, `notRun`, and `tests[]` each with `kind`,
138
- `name`, `qualified` — the `type:object/name` form `xanosdk test run` takes (a query's object is its
138
+ `name`, `qualified` — the `type:object/name` form `npx @xano/sdk test run` takes (a query's object is its
139
139
  lock key, `query:<group>|<verb>|<name>/<test>`), `workflow:<name>` for a workflow test — `object` for a
140
140
  unit test (a query's carries `group` and `verb`), `status`, `message` (the first failure),
141
141
  `expectations` for a unit test — every expectation in order, `{ index, status, message? }`, `index`
142
- from 0 — and `timing` for a workflow test — the engine reports none for a unit test; plus `error` and `retry`, the `xanosdk test run-all` to run
142
+ from 0 — and `timing` for a workflow test — the engine reports none for a unit test; plus `error` and `retry`, the `npx @xano/sdk test run-all` to run
143
143
  again, when the suite could not be run — exit 6 — and `unreachable`, the tests it never reached
144
144
  (as `test run` takes them), when it stopped answering part-way; the same `N passed, M failed,
145
145
  K not run` line `test run-all` prints closes the run), `landingRecord` (`{ destination, file,
@@ -150,7 +150,7 @@ exists), `unconfigured`, and `passwordHashesUnverifiable` (below). The raw
150
150
  workspace blob is deliberately never dumped: it carries per-tenant secrets that must not land
151
151
  in shell history or CI logs.
152
152
 
153
- `xanosdk test run-all --json` (and `test run`, `test list`) writes the same per-test entries at
153
+ `npx @xano/sdk test run-all --json` (and `test run`, `test list`) writes the same per-test entries at
154
154
  the top level, beside the backend they ran on: `kind`, `env` (the ephemeral's or tenant's handle;
155
155
  `null` for a Xano Engine or a workspace), `name` (the backend's own name whatever its kind — the
156
156
  same handle on an ephemeral or tenant, the engine's name on a Xano Engine) and `display` (its display
@@ -169,9 +169,9 @@ out and named (`--env-var GREETING`) — pass them again, or keep them in `xano/
169
169
  `xano/.secrets.json`, which a deploy reads. The same text is the `--json` error's `message`.
170
170
 
171
171
  **Where it goes** — the instance your **token is bound to** (the token's `aud`), never a
172
- flag. `xanosdk deploy --ephemeral` create-or-refreshes an **ephemeral**; a bare `xanosdk deploy`
172
+ flag. `npx @xano/sdk deploy --ephemeral` create-or-refreshes an **ephemeral**; a bare `npx @xano/sdk deploy`
173
173
  runs the code on the Xano Engine on this machine instead ([below](#deploying-locally)). Reaching your real workspace is the separate release flow: cut a release from
174
- what ran, then `xanosdk promote <release>` lands it there as a new branch, leaving live
174
+ what ran, then `npx @xano/sdk promote <release>` lands it there as a new branch, leaving live
175
175
  untouched until you say otherwise.
176
176
 
177
177
  **Static host** — `deploy --static <dir>` archives a directory and deploys it to a
@@ -188,13 +188,13 @@ path, a file, an empty directory, or a build whose compressed archive is over th
188
188
  cap is refused and nothing is deployed (`publish` checks the cap before it asks, too). An upload that fails
189
189
  after the backend landed leaves the backend in place and still writes the deploy's own `--json`
190
190
  summary (not a failure document), with `static` holding `error` (the reason, as printed),
191
- `retry` (the `xanosdk publish` that retries only the static step) and `completed`. The exit
191
+ `retry` (the `npx @xano/sdk publish` that retries only the static step) and `completed`. The exit
192
192
  code says whether the frontend is up: `3` with `completed: "no"` when nothing was sent or the
193
193
  host refused it, `9` with `completed: "unknown"` when the upload was sent and its answer lost
194
194
  (a 5xx, a timeout, a dropped connection) — run `retry`, which settles it either way.
195
195
 
196
196
  A **replacing** deploy clears the target's static hosting — whatever the flags, the replace
197
- removes it — so a later plain `xanosdk deploy`, or `deploy --to … --replace` (a workspace, a
197
+ removes it — so a later plain `npx @xano/sdk deploy`, or `deploy --to … --replace` (a workspace, a
198
198
  tenant, or an ephemeral named as one), takes a published frontend down. Before the import (and
199
199
  in a `--dry-run` plan) it reads which frontends the target is serving from the platform — one
200
200
  another project or the dashboard published included — warns naming each URL, and reports them
@@ -240,25 +240,25 @@ prebuilt `frontend/dist` can retarget any environment with no rebuild.
240
240
  > copy — `curl -s "$URL/?nocache=$(date +%s)"` — and check the fetched HTML for the injected
241
241
  > `window.XANO_HOST` line rather than retrying the same cached URL.
242
242
 
243
- `xanosdk status` prints the same **environment base URL** out of band, for cases where you'd
243
+ `npx @xano/sdk status` prints the same **environment base URL** out of band, for cases where you'd
244
244
  rather bake it in at build time — along with the environment's name and expiry, without your
245
- having to know either. (`xanosdk whoami` prints the *instance* base URL, i.e. the account's
245
+ having to know either. (`npx @xano/sdk whoami` prints the *instance* base URL, i.e. the account's
246
246
  origin rather than the environment.) A static failure after a committed backend deploy **does not roll
247
- back**: it exits `3` (`9` when the upload was sent and its answer lost) and prints the `xanosdk publish` command that retries just that
247
+ back**: it exits `3` (`9` when the upload was sent and its answer lost) and prints the `npx @xano/sdk publish` command that retries just that
248
248
  step, without re-importing the backend.
249
249
 
250
- **Publishing a frontend on its own** — `xanosdk publish <dir>` uploads an already-built
250
+ **Publishing a frontend on its own** — `npx @xano/sdk publish <dir>` uploads an already-built
251
251
  directory and nothing else: no compile, no backend import. `--to` picks the destination —
252
252
  `ephemeral[:<name>]`, `workspace`, or `tenant:<name>`; left off, the backend this project last
253
253
  deployed to — and a workspace or tenant asks before replacing what its users are served
254
254
  (`--yes` in CI). After a local deploy it publishes to that engine (`--to local`
255
- names it), server half included — the upload `xanosdk deploy --local --static <dir>`
255
+ names it), server half included — the upload `npx @xano/sdk deploy --local --static <dir>`
256
256
  makes, without re-importing the backend (below). Scaffolded projects carry it as
257
257
  `npm run xano:deploy:frontend`, which rebuilds first.
258
258
 
259
259
  ```bash
260
- xanosdk promote v2 --set-live # the backend, landed and live
261
- xanosdk publish ./frontend/dist --to workspace --release v2 --branch <label> --yes
260
+ npx @xano/sdk promote v2 --set-live # the backend, landed and live
261
+ npx @xano/sdk publish ./frontend/dist --to workspace --release v2 --branch <label> --yes
262
262
  ```
263
263
 
264
264
  The destination's own URL is injected as `window.XANO_HOST` at publish time (under any
@@ -286,7 +286,7 @@ in `--json` `warnings` naming the build step.
286
286
 
287
287
  `deploy` reuses cached tokens and **refreshes them automatically** when the access token
288
288
  expires (Xano rotates the refresh token on every use; the new one is persisted). A rejected
289
- refresh (`invalid_grant`) clears the stale cache and tells you to `xanosdk login` again.
289
+ refresh (`invalid_grant`) clears the stale cache and tells you to `npx @xano/sdk login` again.
290
290
 
291
291
  **CI & agents** run non-interactively. The credential to reach for is the **meta credential
292
292
  as three environment variables** — the `type: "token"` record above, with no file:
@@ -295,7 +295,7 @@ as three environment variables** — the `type: "token"` record above, with no f
295
295
  XANO_INSTANCE_URL=https://your-instance.xano.io \
296
296
  XANO_WORKSPACE_ID=3 \
297
297
  XANO_META_TOKEN=your-meta-api-token \
298
- npx xanosdk deploy ./xano/index.ts --ephemeral
298
+ npx @xano/sdk deploy ./xano/index.ts --ephemeral
299
299
  ```
300
300
 
301
301
  Nothing is read from or written to disk, and nothing rotates, so the same three secrets keep
@@ -312,18 +312,18 @@ All three are required **together**. Setting some but not others is a hard error
312
312
  rest, rather than a quiet fallback to another credential — a workflow with one misspelled
313
313
  secret must not deploy against whatever happens to be on the runner.
314
314
 
315
- > **Automated agents:** do **not** invoke `xanosdk login` — it blocks on interactive browser
315
+ > **Automated agents:** do **not** invoke `npx @xano/sdk login` — it blocks on interactive browser
316
316
  > consent. Use the three variables above.
317
317
  >
318
318
  > The older `$XANO_REFRESH_TOKEN` + `$XANO_CLIENT_ID` pair still works (both copied once
319
- > from the profile in `auth.json` after a local `xanosdk login`; the target instance is read from the refresh
319
+ > from the profile in `auth.json` after a local `npx @xano/sdk login`; the target instance is read from the refresh
320
320
  > token's `aud` and the workspace resolved per run), but Xano **rotates refresh tokens on
321
321
  > use** — a stored one is spent by its first exchange, so a job that runs twice fails the
322
322
  > second time. Prefer the meta credential.
323
323
 
324
- ## Checking against a live instance (xanosdk preflight)
324
+ ## Checking against a live instance (npx @xano/sdk preflight)
325
325
 
326
- `xanosdk preflight` proves your compiled output against a **real, running Xano
326
+ `npx @xano/sdk preflight` proves your compiled output against a **real, running Xano
327
327
  instance** — not a static snapshot. It compiles your workspace, imports it into a
328
328
  **fresh ephemeral environment created for that run**, exports it back, and diffs it
329
329
  against what you compiled, so you catch three classes of problem a local build can't:
@@ -346,7 +346,7 @@ short expiry, so even a killed process leaves nothing permanent behind. A fresh
346
346
  environment per run is also what makes the diff trustworthy: the objects read back
347
347
  can only have come from this bundle, never from what a previous run left.
348
348
 
349
- **Setup** — nothing, if you have run `xanosdk login`. With no `XANO_VALIDATE_*`
349
+ **Setup** — nothing, if you have run `npx @xano/sdk login`. With no `XANO_VALIDATE_*`
350
350
  variable set, `preflight` uses the credential the rest of the CLI already acts on
351
351
  and creates its ephemeral under the workspace that credential pins.
352
352
 
@@ -363,11 +363,11 @@ XANO_VALIDATE_TOKEN=your-meta-bearer-token
363
363
  ```
364
364
 
365
365
  ```bash
366
- xanosdk preflight ./xano/index.ts # import + round-trip diff, reports per object (every authored kind)
367
- xanosdk preflight ./xano/index.ts --runtime # + run each deployed function
368
- xanosdk preflight ./xano/index.ts --capture # + write fetched JSON to ./validate-out (fixture candidates)
369
- xanosdk preflight ./xano/index.ts --instance http://localhost:8080 # override the target for one run
370
- xanosdk preflight --bundle ws.json # check an already-exported bundle
366
+ npx @xano/sdk preflight ./xano/index.ts # import + round-trip diff, reports per object (every authored kind)
367
+ npx @xano/sdk preflight ./xano/index.ts --runtime # + run each deployed function
368
+ npx @xano/sdk preflight ./xano/index.ts --capture # + write fetched JSON to ./validate-out (fixture candidates)
369
+ npx @xano/sdk preflight ./xano/index.ts --instance http://localhost:8080 # override the target for one run
370
+ npx @xano/sdk preflight --bundle ws.json # check an already-exported bundle
371
371
  ```
372
372
 
373
373
  Two sources, and the environment wins. Set any `XANO_VALIDATE_*` variable (or
@@ -395,7 +395,7 @@ const HOST = (typeof window !== "undefined" && window.XANO_HOST) || import.meta.
395
395
  ```
396
396
 
397
397
  `window.XANO_HOST` is the **environment** URL your deployed APIs answer at (the same value
398
- `xanosdk status` prints as the environment's URL); it is *not* `xanosdk whoami`, which prints
398
+ `npx @xano/sdk status` prints as the environment's URL); it is *not* `npx @xano/sdk whoami`, which prints
399
399
  your account's instance origin. Because injection happens at deploy time, a prebuilt
400
400
  `frontend/dist` retargets any environment with **no rebuild** — ideal for headless agents.
401
401
  Add your own public config (base URLs, *publishable* keys) with `--static-env KEY=VALUE`
@@ -436,16 +436,16 @@ retrying the bare URL.
436
436
 
437
437
  | Command | Where it goes |
438
438
  |---|---|
439
- | `xanosdk deploy` | The **Xano Engine** on this machine — the default, with no flag and no Xano account needed ([below](#deploying-locally)). `--local` spells it out. |
440
- | `xanosdk deploy --ephemeral` | A disposable **ephemeral** environment on Xano's cloud — create-or-refreshed each run, auto-expiring, with its own URL. |
441
- | `xanosdk promote <release>` | Your **main Xano instance** workspace — the production target. Lands a release on a branch named for it (`--set-live` serves it). Its table changes reach live as it lands — see [what a landing does to tables](#what-a-landing-does-to-tables). |
442
- | `xanosdk tenant deploy <tenant> <release>` | A **customer tenant** — the same release, landed on someone else's deployment. It **replaces** what the tenant serves: anything the release does not carry is removed. Static hosting is kept. |
443
- | `xanosdk deploy --to <dest>` | The **escape hatch**: merges a local build straight into `workspace` or `tenant:<name>`, skipping the release record. |
444
- | `xanosdk test` | Nothing — it only reads. Runs the tests an already-deployed backend carries; `--on` picks which one, `local` and `workspace` included. |
439
+ | `npx @xano/sdk deploy` | The **Xano Engine** on this machine — the default, with no flag and no Xano account needed ([below](#deploying-locally)). `--local` spells it out. |
440
+ | `npx @xano/sdk deploy --ephemeral` | A disposable **ephemeral** environment on Xano's cloud — create-or-refreshed each run, auto-expiring, with its own URL. |
441
+ | `npx @xano/sdk promote <release>` | Your **main Xano instance** workspace — the production target. Lands a release on a branch named for it (`--set-live` serves it). Its table changes reach live as it lands — see [what a landing does to tables](#what-a-landing-does-to-tables). |
442
+ | `npx @xano/sdk tenant deploy <tenant> <release>` | A **customer tenant** — the same release, landed on someone else's deployment. It **replaces** what the tenant serves: anything the release does not carry is removed. Static hosting is kept. |
443
+ | `npx @xano/sdk deploy --to <dest>` | The **escape hatch**: merges a local build straight into `workspace` or `tenant:<name>`, skipping the release record. |
444
+ | `npx @xano/sdk test` | Nothing — it only reads. Runs the tests an already-deployed backend carries; `--on` picks which one, `local` and `workspace` included. |
445
445
 
446
446
  Not every instance has ephemeral environments enabled. Where they are off, `deploy --ephemeral`
447
- says so and names who can turn them on. A bare `deploy` (the Xano Engine), `xanosdk export` and
448
- `xanosdk preflight` still work meanwhile.
447
+ says so and names who can turn them on. A bare `deploy` (the Xano Engine), `npx @xano/sdk export` and
448
+ `npx @xano/sdk preflight` still work meanwhile.
449
449
 
450
450
  Every `deploy` is a **full replace** of the disposable environment — always fresh — unless
451
451
  you pass `--keep-data`. Landing somewhere real is the opposite by design: it changes what
@@ -461,7 +461,7 @@ object in `details.outOfScope`, and the rerun with `--yes` printed).
461
461
 
462
462
  ### Keeping your data between deploys
463
463
 
464
- `xanosdk deploy --keep-data` redeploys to your ephemeral or Xano Engine by **merging** into
464
+ `npx @xano/sdk deploy --keep-data` redeploys to your ephemeral or Xano Engine by **merging** into
465
465
  what an earlier deploy put there, instead of replacing it. Code and schema changes land,
466
466
  objects removed from the project are deleted, and the rows already in the tables stay. Seed
467
467
  rows are not written again.
@@ -517,7 +517,7 @@ Before it writes, a merge prints what it will cost, without prompting:
517
517
  - every index it adds or drops;
518
518
  - every new table whose seed rows it does not write;
519
519
  - every env var whose project value differs from the live one — a merge keeps the live
520
- value (`xanosdk env set <NAME> <value>` changes it). Only names are printed, never values;
520
+ value (`npx @xano/sdk env set <NAME> <value>` changes it). Only names are printed, never values;
521
521
  - every other object it deletes, named `<kind>:<name>` (`function:old_helper`,
522
522
  `query:GET ping (apiGroup shop)`).
523
523
 
@@ -530,7 +530,7 @@ and `omittedInsertsFail` / `setInsertsFail` when inserts fail; see below),
530
530
  `narrowedEnums` (`{ table, column, removed }`), `retargetedRefs` (`{ table, column, from, to }`),
531
531
  `indexChanges` (`{ table, index, action, unique }`), `notNullTightened` (`{ table, column, type }`),
532
532
  `removed`, `unseededTables` (new tables whose seed rows the merge did not
533
- write), `renamedTables` (each `{ from, to }`: renamed through `xanosdk lock rename`, rows kept),
533
+ write), `renamedTables` (each `{ from, to }`: renamed through `npx @xano/sdk lock rename`, rows kept),
534
534
  `unchangedEnv` and `canonicalChanges` (each `{ kind, name, from, to }`: a public URL slug a
535
535
  changed `canonical` moved — every endpoint under `from` stops answering). A realtime server's
536
536
  moved slug, or a channel renamed in place, also leaves its `conversation` transcript and
@@ -539,7 +539,7 @@ the name back restores them. Columns are named
539
539
  `table.column` everywhere.
540
540
 
541
541
  The limits, in one place: rows survive only in tables and columns that keep their identity
542
- (a table renamed through `xanosdk lock rename` keeps its rows; an unrecorded rename is refused,
542
+ (a table renamed through `npx @xano/sdk lock rename` keeps its rows; an unrecorded rename is refused,
543
543
  below); changed env values and a new table's seeds need `--reset`;
544
544
  a Xano Engine's rows last as long as its process (an engine update restarts it empty, and the
545
545
  next run seeds); and a test whose `datasource` is `"live"`
@@ -551,8 +551,8 @@ the environment keeps its data. Each refusal is exit 2 and names its remedy:
551
551
  - **A rename the lock was not told about** (`SDK_IDENTITY_CONFLICT`, `details.refused:
552
552
  "renamePending"`): the merge would drop a table `xano.lock` still pins, with its rows, while
553
553
  the project adds a new one. Each is in `details.renames[]` as `{ table, guid, candidates,
554
- rename, prune }` — `rename` is the `xanosdk lock rename …` to run if it was renamed (the merge
555
- then renames it and keeps its rows), `prune` the `xanosdk lock prune …` if it was deleted.
554
+ rename, prune }` — `rename` is the `npx @xano/sdk lock rename …` to run if it was renamed (the merge
555
+ then renames it and keeps its rows), `prune` the `npx @xano/sdk lock prune …` if it was deleted.
556
556
  Run one, then deploy again. When the new table's def pins its own `guid:`, `setGuid: { table,
557
557
  guid, pins }` replaces `rename`: set that def's `guid:` to `guid` — a def's guid replaces any
558
558
  lock entry, so a `lock rename` would not keep the rows. The lock marks such an entry
@@ -573,7 +573,7 @@ the environment keeps its data. Each refusal is exit 2 and names its remedy:
573
573
  a `canonical` written in code is served as declared or the merge is refused. The usual cause
574
574
  is an api group (toolset, realtime server) renamed while keeping its `canonical`: a merge
575
575
  creates the renamed object beside the old one, which still holds the slug. The entry carries
576
- `heldBy` and `rename` — the `xanosdk lock rename …` that makes the merge rename it in place,
576
+ `heldBy` and `rename` — the `npx @xano/sdk lock rename …` that makes the merge rename it in place,
577
577
  keeping its URL. Otherwise pick another `canonical`, or `--reset`.
578
578
  - **A unique index the rows already there break** (`SDK_IMPORT_REFUSED`, `details.refused:
579
579
  "uniqueViolation"`, the indexes the merge adds in `details.indexes[]` as `{ table, index }`,
@@ -613,7 +613,7 @@ with `--to` (`--seed`, `--prune`, `--dry-run`, …) stay refused alongside it.
613
613
 
614
614
  ### Deploying locally
615
615
 
616
- A bare `xanosdk deploy` deploys to an engine running on this machine — no network round-trip
616
+ A bare `npx @xano/sdk deploy` deploys to an engine running on this machine — no network round-trip
617
617
  per deploy. `--local` is that default spelled out, needed only to name an engine:
618
618
  `--local=<version|url|path>` runs that one instead of the pinned version. It needs nothing
619
619
  configured:
@@ -630,7 +630,7 @@ configured:
630
630
  `XANOSDK_NO_UPDATE_CHECK=1`). In an interactive terminal the deploy asks whether to update,
631
631
  defaulting to no — a version you declined is only noted afterwards, not asked again. In CI,
632
632
  piped output or `--json` it prints a one-line notice and keeps the pin. The pin never moves
633
- without a yes or an explicit `xanosdk local update`.
633
+ without a yes or an explicit `npx @xano/sdk local update`.
634
634
  - **A running engine on a different version** than the one the project now resolves to — after
635
635
  an update, or after a teammate moved the pin — is stopped and replaced, and the deploy says
636
636
  so.
@@ -644,18 +644,18 @@ An engine update restarts the engine, and a restarted engine starts **empty**: t
644
644
  rather than merging, so rows entered through your app do not survive the upgrade.
645
645
 
646
646
  **Operating on it.** After a local deploy, the engine is the backend this project
647
- tracks, so bare `xanosdk test run-all`, `env set`, `env pull`, `tables`, `impersonate` and
647
+ tracks, so bare `npx @xano/sdk test run-all`, `env set`, `env pull`, `tables`, `impersonate` and
648
648
  `status` reach it — none of them needs a Xano account. Name it explicitly as `local`,
649
- or `local:<name>` for another one from `xanosdk local list` (the full grammar is in
649
+ or `local:<name>` for another one from `npx @xano/sdk local list` (the full grammar is in
650
650
  [the CLI guide](cli.md#naming-a-backend)). `publish` puts a built frontend on it without
651
651
  re-importing the backend. One command cannot serve it and refuses it by name: `release create`
652
652
  (the cut runs on the instance — pass `--from ephemeral`).
653
653
 
654
654
  | Command | What it does |
655
655
  |---|---|
656
- | `xanosdk local update` | Moves the pin to the latest engine (`--version <v>`: that one, downgrades included), downloads it, and restarts the project's running engine on it. Commit `package.json`. |
657
- | `xanosdk local cache list` | Each cached engine version, its size on disk, and the engines running on it. |
658
- | `xanosdk local cache clear` | Removes every cached engine (`--version <v>`: just that one). An engine running on a removed version is stopped first; the next deploy fetches it again. |
656
+ | `npx @xano/sdk local update` | Moves the pin to the latest engine (`--version <v>`: that one, downgrades included), downloads it, and restarts the project's running engine on it. Commit `package.json`. |
657
+ | `npx @xano/sdk local cache list` | Each cached engine version, its size on disk, and the engines running on it. |
658
+ | `npx @xano/sdk local cache clear` | Removes every cached engine (`--version <v>`: just that one). An engine running on a removed version is stopped first; the next deploy fetches it again. |
659
659
 
660
660
  #### Connecting a coding agent
661
661
 
@@ -663,9 +663,9 @@ The Xano Engine serves an MCP server for coding agents, and a local deploy print
663
663
  for looking at the deployed backend (objects, table schemas, rows, run history), seeding and
664
664
  editing rows, and running functions, tasks, triggers, endpoints and tests by hand, each
665
665
  answering its result and logs. It never changes a primitive: tables, endpoints, functions and
666
- every other object change in `xano/` and ship with `xanosdk deploy`.
666
+ every other object change in `xano/` and ship with `npx @xano/sdk deploy`.
667
667
 
668
- `xanosdk init` connects Claude Code (`.mcp.json`) and Cursor (`.cursor/mcp.json`) to it with one
668
+ `npx @xano/sdk init` connects Claude Code (`.mcp.json`) and Cursor (`.cursor/mcp.json`) to it with one
669
669
  server, `xano-local`, that launches a bridge. This is the Claude Code `.mcp.json` entry; Cursor's
670
670
  appends `--project ${workspaceFolder}`, since Cursor does not promise to launch it inside the project:
671
671
 
@@ -679,29 +679,29 @@ before `npm install`). The config holds no url and no token. The engine may come
679
679
  always mints a new bearer, so the bridge looks both up when it needs them, and again when the
680
680
  engine stops answering or refuses the bearer. Before the first deploy the server connects and
681
681
  lists no tools; once an engine is up it tells the agent its tools changed. A call cut off after
682
- it reached the engine is reported as unknown, never sent twice. `xanosdk local mcp` prints the
682
+ it reached the engine is reported as unknown, never sent twice. `npx @xano/sdk local mcp` prints the
683
683
  details and each agent's config line, and `init` in an existing project adds the server beside
684
684
  the ones a config already declares. An engine too old to serve MCP says so on deploy, and
685
- `xanosdk local update` moves the project to one that does. Claude Code asks once before it
685
+ `npx @xano/sdk local update` moves the project to one that does. Claude Code asks once before it
686
686
  starts a project's server; a Cursor version that does not pick up the tool change needs the
687
687
  `xano-local` server refreshed in its MCP settings after the first deploy.
688
688
 
689
689
  #### A frontend on the Xano Engine, and server rendering
690
690
 
691
- `xanosdk deploy <entry> --local --static <dir>` publishes a built frontend to the
691
+ `npx @xano/sdk deploy <entry> --local --static <dir>` publishes a built frontend to the
692
692
  engine's own static host after the import, as on an ephemeral, and reports it as `static.url`:
693
693
  `http://<prefix>.localhost:<port>`. Chrome, Firefox and Safari 26 resolve `*.localhost` to this
694
694
  machine by themselves (Safari on macOS 15 and earlier does not); a tool that does not resolve it
695
695
  can call the engine's own URL with a `Host: <prefix>.localhost:<port>` header. The engine needs a release
696
696
  that hosts static sites: an older one answers the upload with a 501, which the deploy reports
697
- without failing the backend (exit `3`), and `xanosdk local update` moves the pin on.
697
+ without failing the backend (exit `3`), and `npx @xano/sdk local update` moves the pin on.
698
698
 
699
699
  The engine hosts built output only, and refuses a build of more than 20,000 files or 256 MB unpacked.
700
700
  The deploy checks both before the import, so an oversize directory stops the run with nothing
701
701
  written. A symbolic link in the directory is not uploaded.
702
702
 
703
703
  A SvelteKit app can also render on the server there. Build it with the SDK's adapter (it needs
704
- `esbuild` in the app: `npm i -D esbuild`). In a project `xanosdk init` scaffolded, SvelteKit's
704
+ `esbuild` in the app: `npm i -D esbuild`). In a project `npx @xano/sdk init` scaffolded, SvelteKit's
705
705
  config is the object passed to `sveltekit()` in `vite.config.ts` (a `svelte.config.js` is ignored
706
706
  there), and it already builds with this adapter: stop prerendering the routes that should render
707
707
  per request (the scaffold prerenders every route from `frontend/src/routes/+layout.ts`):
@@ -763,14 +763,14 @@ its unpacked runtime files, its logs, and the records of running engines — bes
763
763
  fails names it.
764
764
 
765
765
  Expect it to reach roughly 600 MB after the first deploy, and to grow by a similar amount for
766
- each engine version you run, since every version unpacks its own copy. `xanosdk local cache
767
- list` shows its size, and `xanosdk local cache clear` (with no `--version`) removes it with the
766
+ each engine version you run, since every version unpacks its own copy. `npx @xano/sdk local cache
767
+ list` shows its size, and `npx @xano/sdk local cache clear` (with no `--version`) removes it with the
768
768
  engines once none is running — it names any engine still up; stop it and clear again. The next
769
769
  deploy recreates what it needs.
770
770
 
771
771
  Versions before this layout unpacked the same runtime into your own per-user cache directory.
772
772
  Nothing runs from that copy now; `cache list` shows it when it is there, and
773
- `xanosdk local cache clear --legacy-runtime` removes it after asking (`--yes` without a
773
+ `npx @xano/sdk local cache clear --legacy-runtime` removes it after asking (`--yes` without a
774
774
  terminal).
775
775
 
776
776
  #### Running a different engine without moving the pin
@@ -806,21 +806,21 @@ unset XANOSDK_ENGINE_OVERRIDE # next deploy is back on the pinned version
806
806
  `XANOSDK_ENGINE_RELEASES_URL` points version lookups at a different engine release service. Its
807
807
  engines are downloaded fresh on every deploy and kept apart from the version cache, and the
808
808
  deploy runs its latest without reading or writing the pin or checking for updates;
809
- `xanosdk local update` refuses while it is set.
809
+ `npx @xano/sdk local update` refuses while it is set.
810
810
 
811
811
  ### The release flow
812
812
 
813
813
  This is the path to a real destination. Each step leaves something the next one can name:
814
814
 
815
815
  ```bash
816
- xanosdk deploy ./xano/index.ts --ephemeral --test # 1. stand it up on an ephemeral, run its tests
817
- xanosdk release create v1 # 2. cut a release from what just ran (after a local deploy: --from ephemeral)
818
- xanosdk promote v1 # 3. land it in your workspace, on a branch named for it
819
- xanosdk tenant deploy acme v1 # …or on a customer tenant
816
+ npx @xano/sdk deploy ./xano/index.ts --ephemeral --test # 1. stand it up on an ephemeral, run its tests
817
+ npx @xano/sdk release create v1 # 2. cut a release from what just ran (after a local deploy: --from ephemeral)
818
+ npx @xano/sdk promote v1 # 3. land it in your workspace, on a branch named for it
819
+ npx @xano/sdk tenant deploy acme v1 # …or on a customer tenant
820
820
  ```
821
821
 
822
822
  Step 2 is what makes the rest re-runnable. A release is a stored record that this code came
823
- up and answered, so `promote v1` a week later lands the same bytes — and `xanosdk release
823
+ up and answered, so `promote v1` a week later lands the same bytes — and `npx @xano/sdk release
824
824
  list` says what you have. Cut a release per merge, per tag, or per deploy you want to keep;
825
825
  an existing name is refused rather than replaced, because a tenant may be running it.
826
826
 
@@ -945,8 +945,8 @@ it on failure as well as success, once it knows what it was about to write. Ever
945
945
  { "name": "land", "completed": "unknown" },
946
946
  { "name": "verify", "completed": "skipped" }
947
947
  ],
948
- "resolveWith": "xanosdk workspace branch list --json",
949
- "resolveSteps": ["If \"v1-…\" is absent, nothing landed: re-run as `xanosdk promote v1 --branch v1-… --yes`.", "…"],
948
+ "resolveWith": "npx @xano/sdk workspace branch list --json",
949
+ "resolveSteps": ["If \"v1-…\" is absent, nothing landed: re-run as `npx @xano/sdk promote v1 --branch v1-… --yes`.", "…"],
950
950
  "startedAt": "2026-09-22T14:00:00.000Z",
951
951
  "resolveNotBefore": "2026-09-22T14:10:00.000Z",
952
952
  "error": { "code": "SDK_ERROR", "message": "…", "exitCode": 9 } // only when the run failed
@@ -1053,12 +1053,12 @@ extra flags is not a release "without tables" — it has all of them.
1053
1053
  What it does not carry, unless you ask for it, is any table's **rows**:
1054
1054
 
1055
1055
  ```bash
1056
- xanosdk tables # id, guid, and name — of what this project deployed to
1057
- xanosdk tables ephemeral:e4f2-9ab1 # …or a named env (its name, not its display name)
1058
- xanosdk tables tenant:acme # …or a tenant
1059
- xanosdk tables workspace # …or your workspace
1060
- xanosdk release create v1 --seed # every table's rows ride along
1061
- xanosdk release create v1 --seed=<guid>,<guid> # only those two tables' rows
1056
+ npx @xano/sdk tables # id, guid, and name — of what this project deployed to
1057
+ npx @xano/sdk tables ephemeral:e4f2-9ab1 # …or a named env (its name, not its display name)
1058
+ npx @xano/sdk tables tenant:acme # …or a tenant
1059
+ npx @xano/sdk tables workspace # …or your workspace
1060
+ npx @xano/sdk release create v1 --seed # every table's rows ride along
1061
+ npx @xano/sdk release create v1 --seed=<guid>,<guid> # only those two tables' rows
1062
1062
  ```
1063
1063
 
1064
1064
  Rows are opt-in because a release is durable and can be landed on another environment; data
@@ -1080,7 +1080,7 @@ pointer without the file — on the backend it lands on, the row's file would be
1080
1080
  icon would answer 404. So `release create` refuses (`SDK_RELEASE_FILES_NOT_CARRIED`, exit 2) a
1081
1081
  cut whose source serves `hostedFile()` icons, or whose `--seed` selects a table with a file
1082
1082
  column while the source holds files. Land a project like that by deploying it directly, which
1083
- ships its files: `xanosdk deploy --to tenant:<name> --seed`.
1083
+ ships its files: `npx @xano/sdk deploy --to tenant:<name> --seed`.
1084
1084
 
1085
1085
  List from **the source you are cutting from**, not from your workspace. A table this project
1086
1086
  deployed carries the guid `xano.lock` pins for it wherever it landed, but one created anywhere
@@ -1112,7 +1112,7 @@ list of them could not be read back reliably.
1112
1112
  >
1113
1113
  > What changes one is a **rename** — the name is what the guid derives from. A 32-hex guid that
1114
1114
  > no longer matches usually means the table was renamed or removed in code since it was noted;
1115
- > `xanosdk lock rename` carries the identity across a rename you meant. A guid in the engine's own
1115
+ > `npx @xano/sdk lock rename` carries the identity across a rename you meant. A guid in the engine's own
1116
1116
  > shape (about 27 base64url characters) belongs to a table this project did not deploy, and does
1117
1117
  > not travel between backends.
1118
1118
 
@@ -1121,7 +1121,7 @@ source's real tables if one does not match, and names the listing verb for that
1121
1121
 
1122
1122
  ### The alternative: merging a local build
1123
1123
 
1124
- `xanosdk deploy <entry> --to workspace` (or `--to tenant:<name>`) skips the release record and
1124
+ `npx @xano/sdk deploy <entry> --to workspace` (or `--to tenant:<name>`) skips the release record and
1125
1125
  merges the build on your disk straight into the destination. Reach for it when you want the
1126
1126
  pre-flight the release path does not have — a plan preview, a prune scope, loss warnings —
1127
1127
  or when you are deleting objects, which a release does not do.
@@ -1180,11 +1180,11 @@ replace deletes them like any other.
1180
1180
 
1181
1181
  `--yes` does not cover this; it waives the confirmation, not the loss. To go
1182
1182
  ahead, pass `--allow-branch-deletion`. To keep the work first, export each branch
1183
- on its own — a bare `xanosdk workspace export` reads the **live** branch, which is
1183
+ on its own — a bare `npx @xano/sdk workspace export` reads the **live** branch, which is
1184
1184
  the one a replace restores anyway:
1185
1185
 
1186
1186
  ```sh
1187
- xanosdk workspace export --branch branch2
1187
+ npx @xano/sdk workspace export --branch branch2
1188
1188
  ```
1189
1189
 
1190
1190
  Or drop `--replace`: the default merge leaves other branches untouched. Tenants
@@ -1199,7 +1199,7 @@ read, which is not the same as nothing to lose.
1199
1199
  ### Where a release lives
1200
1200
 
1201
1201
  A release is always a record **in your workspace**, whatever it was cut from —
1202
- that is what `xanosdk release list`, `promote`, and `tenant deploy` all read.
1202
+ that is what `npx @xano/sdk release list`, `promote`, and `tenant deploy` all read.
1203
1203
 
1204
1204
  Cutting from an environment is one call. The platform reads that environment's
1205
1205
  live state and writes the record here — **nothing is written to the
@@ -1208,9 +1208,9 @@ sandbox you cut from is left exactly as it was.
1208
1208
 
1209
1209
  Only a throwaway environment may be a source. `--from tenant:<name>` is accepted
1210
1210
  for an ephemeral or a sandbox, and refused for a `standard` or `run` tenant: that
1211
- is a live deployment. `xanosdk tenant get <name>` names the last release landed
1211
+ is a live deployment. `npx @xano/sdk tenant get <name>` names the last release landed
1212
1212
  there, which lands anywhere as it is — but a `deploy --to` merge since may have
1213
- changed what the tenant runs. To start from what it runs now, `xanosdk pull` it,
1213
+ changed what the tenant runs. To start from what it runs now, `npx @xano/sdk pull` it,
1214
1214
  deploy that to an ephemeral, and cut from there.
1215
1215
 
1216
1216
  Cutting `--from workspace` packages a branch directly — whatever the workspace
@@ -1224,18 +1224,18 @@ contents are not what its name claims.
1224
1224
 
1225
1225
  ### Moving a release to another workspace or instance
1226
1226
 
1227
- `xanosdk release transfer <name> --to-profile <profile>` copies a stored release into the
1227
+ `npx @xano/sdk release transfer <name> --to-profile <profile>` copies a stored release into the
1228
1228
  workspace a stored credential profile is bound to — another workspace, or another
1229
1229
  instance. It moves the archive and nothing else: no compile, no branch, nothing lands.
1230
1230
  Run `promote` on the destination afterwards, exactly as you would at the source.
1231
1231
 
1232
1232
  ```bash
1233
- xanosdk release transfer v1 --to-profile prod --dry-run # is it already there?
1234
- xanosdk release transfer v1 --to-profile prod --yes # copy it
1235
- xanosdk promote v1 --profile prod # land it there
1233
+ npx @xano/sdk release transfer v1 --to-profile prod --dry-run # is it already there?
1234
+ npx @xano/sdk release transfer v1 --to-profile prod --yes # copy it
1235
+ npx @xano/sdk promote v1 --profile prod # land it there
1236
1236
  ```
1237
1237
 
1238
- `--to-profile` names a profile from `xanosdk profile list`; the run's own credential is the
1238
+ `--to-profile` names a profile from `npx @xano/sdk profile list`; the run's own credential is the
1239
1239
  source. A profile bound to the same instance and workspace is refused.
1240
1240
 
1241
1241
  A transfer decides "already there" by content, never by name or size: the sha256 of the
@@ -1257,15 +1257,15 @@ removes it.
1257
1257
 
1258
1258
  ### Pulling a backend into a project
1259
1259
 
1260
- `xanosdk pull <source>` refreshes `xano/` in a project that already has a frontend, a lockfile,
1261
- and a git history — where `xanosdk init --from <source>` writes a whole new project instead. It
1260
+ `npx @xano/sdk pull <source>` refreshes `xano/` in a project that already has a frontend, a lockfile,
1261
+ and a git history — where `npx @xano/sdk init --from <source>` writes a whole new project instead. It
1262
1262
  takes the same source vocabulary everything else does: `release:<name>`, `ephemeral:<name>`,
1263
1263
  `tenant:<name>`, `workspace`, or a bundle path.
1264
1264
 
1265
1265
  ```bash
1266
- xanosdk pull release:v1 # refresh xano/ from a release (keeps files you added)
1267
- xanosdk pull workspace # …or from the live workspace
1268
- xanosdk pull release:v1 --yes # skip the confirmation and the dirty-tree refusal (CI)
1266
+ npx @xano/sdk pull release:v1 # refresh xano/ from a release (keeps files you added)
1267
+ npx @xano/sdk pull workspace # …or from the live workspace
1268
+ npx @xano/sdk pull release:v1 --yes # skip the confirmation and the dirty-tree refusal (CI)
1269
1269
  ```
1270
1270
 
1271
1271
  `pull` **replaces** and cannot merge: a file the previous decode wrote that this one does not
@@ -1287,7 +1287,7 @@ commands that record one are `deploy --to workspace`, a verified `promote`, `pul
1287
1287
  and `init --from workspace`. Commit it with the rest of the lock.
1288
1288
 
1289
1289
  ```bash
1290
- xanosdk workspace diff ./xano/index.ts --json
1290
+ npx @xano/sdk workspace diff ./xano/index.ts --json
1291
1291
  ```
1292
1292
 
1293
1293
  ```jsonc
@@ -1357,9 +1357,9 @@ serves the branch until you promote it.
1357
1357
  `promote` lands a release on a branch and takes the same flag:
1358
1358
 
1359
1359
  ```bash
1360
- xanosdk promote v1 --branch staging # land the release there, live untouched
1361
- xanosdk workspace branch list # see what exists, and what is live
1362
- xanosdk workspace branch set-live staging # promote when you are happy
1360
+ npx @xano/sdk promote v1 --branch staging # land the release there, live untouched
1361
+ npx @xano/sdk workspace branch list # see what exists, and what is live
1362
+ npx @xano/sdk workspace branch set-live staging # promote when you are happy
1363
1363
  ```
1364
1364
 
1365
1365
  A promote **always** lands on a branch, named or not: without `--branch` the label is derived
@@ -1371,17 +1371,17 @@ deleted afterwards, so the CLI names it rather than letting that happen.
1371
1371
  stage first and cut over immediately, or on its own as the one-shot to production:
1372
1372
 
1373
1373
  ```bash
1374
- xanosdk promote v1 --set-live # land on a derived branch and serve it
1374
+ npx @xano/sdk promote v1 --set-live # land on a derived branch and serve it
1375
1375
  ```
1376
1376
 
1377
1377
  The merge path takes it too, when you want the preview a release cannot run:
1378
1378
 
1379
1379
  ```bash
1380
- xanosdk deploy ./xano/index.ts --to workspace --branch staging --dry-run # preview against the branch
1381
- xanosdk deploy ./xano/index.ts --to workspace --branch staging # land it, live untouched
1380
+ npx @xano/sdk deploy ./xano/index.ts --to workspace --branch staging --dry-run # preview against the branch
1381
+ npx @xano/sdk deploy ./xano/index.ts --to workspace --branch staging # land it, live untouched
1382
1382
  ```
1383
1383
 
1384
- There, `--backup-branch` snapshots live first, so the way back is `xanosdk workspace branch
1384
+ There, `--backup-branch` snapshots live first, so the way back is `npx @xano/sdk workspace branch
1385
1385
  set-live <backup-label>`. That restores **logic only**: tables are shared by every branch, so a
1386
1386
  column or table the deploy dropped stays dropped, with its data, after the switch back. The
1387
1387
  data-safe path is before landing: read `droppedColumns` in the `--dry-run` plan, and keep the
@@ -1410,9 +1410,9 @@ are applied — even while the logic that reads them is staged on a branch. No o
1410
1410
  a half-data, half-logic change atomic; one order is simply less bad than the other:
1411
1411
 
1412
1412
  ```bash
1413
- xanosdk workspace reset-tables ./index.ts --table <guid> # dry run, per-table counts
1414
- xanosdk workspace reset-tables ./index.ts --table <guid> --write # then apply
1415
- xanosdk promote v2 # then the logic
1413
+ npx @xano/sdk workspace reset-tables ./index.ts --table <guid> # dry run, per-table counts
1414
+ npx @xano/sdk workspace reset-tables ./index.ts --table <guid> --write # then apply
1415
+ npx @xano/sdk promote v2 # then the logic
1416
1416
  ```
1417
1417
 
1418
1418
  Rows first, then logic: new rows under old logic break only a feature you are removing, while
@@ -1466,7 +1466,7 @@ no longer defines is work to do, so that is not a no-op either.
1466
1466
 
1467
1467
  On the merge path, anything destructive is **previewed first** — the CLI fetches the plan,
1468
1468
  prints what would change, and asks (an ephemeral never does). `--yes` skips the prompt for CI but never skips the
1469
- preview. Start with `xanosdk deploy ./xano/index.ts --to workspace --dry-run` to see the plan
1469
+ preview. Start with `npx @xano/sdk deploy ./xano/index.ts --to workspace --dry-run` to see the plan
1470
1470
  without committing to it. (`promote` runs no preview — the platform lands the release — which
1471
1471
  is the trade the release flow makes and says so before writing.)
1472
1472
 
@@ -1519,12 +1519,12 @@ by hand, or defined again, deployed, and then removed. A prune with no lock at a
1519
1519
  either, so it is the same refusal — `SDK_PRUNE_OUT_OF_SCOPE`, exit `2`, the refusal document
1520
1520
  under `--json` — saying there is no lock; reaching that usually means `--no-lock` suppressed
1521
1521
  it, and the remedy is the same one landing without `--prune` (and without `--no-lock`), then
1522
- committing the lock. A lock alone does not unlock a prune: `xanosdk export` writes one with no
1522
+ committing the lock. A lock alone does not unlock a prune: `npx @xano/sdk export` writes one with no
1523
1523
  landing record. Deploying a pre-exported `--bundle` carries no entry file to find a lock beside,
1524
1524
  so name it with `--lock=<path>` — without one that is a usage error (exit `1`). None of
1525
1525
  that applies to an ephemeral: its record is `.xano/ephemeral.json` in the project the run is in —
1526
1526
  the directory you deploy from when it is a project (it has `.xano/` or its own `xano/` entry),
1527
- otherwise the entry's (`suites/alpha/.xano/` for `xanosdk deploy suites/alpha/xano/index.ts` typed
1527
+ otherwise the entry's (`suites/alpha/.xano/` for `npx @xano/sdk deploy suites/alpha/xano/index.ts` typed
1528
1528
  from a repository root holding no project) — written lock or not, so a prune there needs no lock,
1529
1529
  and one refused there names that file and asks for a landing of that entry, with nothing to
1530
1530
  commit. The credential in `.xano/auth.json` is read from the same project. Commands that default
@@ -1569,7 +1569,7 @@ object this project would create under a name the workspace already holds with a
1569
1569
  identity is refused: the import would not update it, it would create a **second** object beside
1570
1570
  it under a suffixed name and report success — with an auth table, that binds every endpoint to
1571
1571
  one table while tokens are minted against the other. Three ways forward, all named in the
1572
- message: adopt the objects that are already there with `xanosdk lock import` and commit the lock,
1572
+ message: adopt the objects that are already there with `npx @xano/sdk lock import` and commit the lock,
1573
1573
  rename yours, or release into a workspace that does not hold them. A workspace that could not be
1574
1574
  read refuses too — a failed read is not evidence that there is no collision.
1575
1575
 
@@ -1627,7 +1627,7 @@ and `XANO_META_TOKEN`, [above](#signing-in--deploying-in-depth) — no browser,
1627
1627
  nothing that rotates:
1628
1628
 
1629
1629
  ```bash
1630
- XANO_INSTANCE_URL=… XANO_WORKSPACE_ID=… XANO_META_TOKEN=… npx xanosdk deploy ./xano/index.ts --ephemeral
1630
+ XANO_INSTANCE_URL=… XANO_WORKSPACE_ID=… XANO_META_TOKEN=… npx @xano/sdk deploy ./xano/index.ts --ephemeral
1631
1631
  ```
1632
1632
 
1633
1633
  > ⚠️ A deploy without `--keep-data` is a full replace of the target environment, including