@naturali/sdk 0.135.0 → 0.136.1

package/dist/index.d.cts

@@ -438,7 +438,7 @@ type Address = {
   /**
    * This address's own decision, when it has one — beats every route.
    */
-  action: 'agent' | 'message' | 'silence' | null;
+  action: 'agent' | 'oneshot' | 'message' | 'silence' | null;
   agent_id: string | null;
   text: string | null;
   /**
@@ -448,6 +448,14 @@ type Address = {
     after_seconds: number;
   };
   language: string | null;
+  /**
+   * Conversation config bag — media handling, persona overrides, the Discord allowlist, and how a `oneshot` answers.
+   *
+   * `discord.reply` picks the delivery: `react` (the default) adds `discord.reaction` — `✅` unless named — to the message that triggered the run, `mention` answers beside it addressing whoever asked, `thread` opens a thread and answers inside it, and `none` delivers nothing at all. A run that fails delivers nothing in every mode, so a reaction always means the work was done; there is no failure marker.
+   *
+   * Read only for `oneshot`. A conversational `agent` in a guild *is* its thread — that is what its session is keyed on — so it always opens one.
+   *
+   */
   config: {
     [key: string]: unknown;
   } | null;
@@ -459,13 +467,29 @@ type Address = {
  *
  */
 type AddressActionSet = {
-  action: 'agent' | 'message' | 'silence' | null;
+  /**
+   * What an inbound message becomes.
+   *
+   * `agent` is a dialogue: the identity behind the message gets a session, and every later message on it continues the same one. `oneshot` runs the agent once and keeps nothing — no address, no actor, no session, no conversation — so each message is answered on its own. Choose it for work that is filed rather than discussed; choose `agent` when the answer depends on what came before.
+   *
+   * `message` delivers fixed text without running an agent, and `silence` answers nothing.
+   *
+   */
+  action: 'agent' | 'oneshot' | 'message' | 'silence' | null;
   agent_id?: string;
   text?: string;
   repeat?: 'every' | 'once' | {
     after_seconds: number;
   };
   language?: string;
+  /**
+   * Conversation config bag — media handling, persona overrides, the Discord allowlist, and how a `oneshot` answers.
+   *
+   * `discord.reply` picks the delivery: `react` (the default) adds `discord.reaction` — `✅` unless named — to the message that triggered the run, `mention` answers beside it addressing whoever asked, `thread` opens a thread and answers inside it, and `none` delivers nothing at all. A run that fails delivers nothing in every mode, so a reaction always means the work was done; there is no failure marker.
+   *
+   * Read only for `oneshot`. A conversational `agent` in a guild *is* its thread — that is what its session is keyed on — so it always opens one.
+   *
+   */
   config?: {
     [key: string]: unknown;
   };
@@ -2088,7 +2112,15 @@ type ChannelRoute = {
    * Tiebreak only, after specificity and `surface`.
    */
   priority: number;
-  action: 'agent' | 'message' | 'silence';
+  /**
+   * What an inbound message becomes.
+   *
+   * `agent` is a dialogue: the identity behind the message gets a session, and every later message on it continues the same one. `oneshot` runs the agent once and keeps nothing — no address, no actor, no session, no conversation — so each message is answered on its own. Choose it for work that is filed rather than discussed; choose `agent` when the answer depends on what came before.
+   *
+   * `message` delivers fixed text without running an agent, and `silence` answers nothing.
+   *
+   */
+  action: 'agent' | 'oneshot' | 'message' | 'silence';
   agent_id: string | null;
   text: string | null;
   /**
@@ -2098,6 +2130,14 @@ type ChannelRoute = {
     after_seconds: number;
   };
   language: string | null;
+  /**
+   * Conversation config bag — media handling, persona overrides, the Discord allowlist, and how a `oneshot` answers.
+   *
+   * `discord.reply` picks the delivery: `react` (the default) adds `discord.reaction` — `✅` unless named — to the message that triggered the run, `mention` answers beside it addressing whoever asked, `thread` opens a thread and answers inside it, and `none` delivers nothing at all. A run that fails delivers nothing in every mode, so a reaction always means the work was done; there is no failure marker.
+   *
+   * Read only for `oneshot`. A conversational `agent` in a guild *is* its thread — that is what its session is keyed on — so it always opens one.
+   *
+   */
   config: {
     [key: string]: unknown;
   } | null;
@@ -2111,13 +2151,29 @@ type ChannelRouteWrite = {
     [key: string]: unknown;
   };
   priority?: number;
-  action: 'agent' | 'message' | 'silence';
+  /**
+   * What an inbound message becomes.
+   *
+   * `agent` is a dialogue: the identity behind the message gets a session, and every later message on it continues the same one. `oneshot` runs the agent once and keeps nothing — no address, no actor, no session, no conversation — so each message is answered on its own. Choose it for work that is filed rather than discussed; choose `agent` when the answer depends on what came before.
+   *
+   * `message` delivers fixed text without running an agent, and `silence` answers nothing.
+   *
+   */
+  action: 'agent' | 'oneshot' | 'message' | 'silence';
   agent_id?: string;
   text?: string;
   repeat?: 'every' | 'once' | {
     after_seconds: number;
   };
   language?: string;
+  /**
+   * Conversation config bag — media handling, persona overrides, the Discord allowlist, and how a `oneshot` answers.
+   *
+   * `discord.reply` picks the delivery: `react` (the default) adds `discord.reaction` — `✅` unless named — to the message that triggered the run, `mention` answers beside it addressing whoever asked, `thread` opens a thread and answers inside it, and `none` delivers nothing at all. A run that fails delivers nothing in every mode, so a reaction always means the work was done; there is no failure marker.
+   *
+   * Read only for `oneshot`. A conversational `agent` in a guild *is* its thread — that is what its session is keyed on — so it always opens one.
+   *
+   */
   config?: {
     [key: string]: unknown;
   };
@@ -2268,9 +2324,17 @@ type ChannelList = {
  *
  */
 type ChannelDefaultAction = {
-  action: 'agent' | 'message' | 'silence';
   /**
-   * The agent that answers, when `action` is `agent`.
+   * What an inbound message becomes.
+   *
+   * `agent` is a dialogue: the identity behind the message gets a session, and every later message on it continues the same one. `oneshot` runs the agent once and keeps nothing — no address, no actor, no session, no conversation — so each message is answered on its own. Choose it for work that is filed rather than discussed; choose `agent` when the answer depends on what came before.
+   *
+   * `message` delivers fixed text without running an agent, and `silence` answers nothing.
+   *
+   */
+  action: 'agent' | 'oneshot' | 'message' | 'silence';
+  /**
+   * The agent that answers, when `action` is `agent` or `oneshot`.
    */
   agent_id: string | null;
   /**
@@ -2289,7 +2353,12 @@ type ChannelDefaultAction = {
    */
   language: string | null;
   /**
-   * Conversation config bag — media handling, persona overrides, the Discord allowlist.
+   * Conversation config bag — media handling, persona overrides, the Discord allowlist, and how a `oneshot` answers.
+   *
+   * `discord.reply` picks the delivery: `react` (the default) adds `discord.reaction` — `✅` unless named — to the message that triggered the run, `mention` answers beside it addressing whoever asked, `thread` opens a thread and answers inside it, and `none` delivers nothing at all. A run that fails delivers nothing in every mode, so a reaction always means the work was done; there is no failure marker.
+   *
+   * Read only for `oneshot`. A conversational `agent` in a guild *is* its thread — that is what its session is keyed on — so it always opens one.
+   *
    */
   config: {
     [key: string]: unknown;
@@ -2300,7 +2369,15 @@ type ChannelDefaultAction = {
  *
  */
 type ChannelDefaultActionInput = {
-  action: 'agent' | 'message' | 'silence';
+  /**
+   * What an inbound message becomes.
+   *
+   * `agent` is a dialogue: the identity behind the message gets a session, and every later message on it continues the same one. `oneshot` runs the agent once and keeps nothing — no address, no actor, no session, no conversation — so each message is answered on its own. Choose it for work that is filed rather than discussed; choose `agent` when the answer depends on what came before.
+   *
+   * `message` delivers fixed text without running an agent, and `silence` answers nothing.
+   *
+   */
+  action: 'agent' | 'oneshot' | 'message' | 'silence';
   agent_id?: string;
   text?: string;
   repeat?: 'every' | 'once' | {

package/dist/index.d.mts

@@ -438,7 +438,7 @@ type Address = {
   /**
    * This address's own decision, when it has one — beats every route.
    */
-  action: 'agent' | 'message' | 'silence' | null;
+  action: 'agent' | 'oneshot' | 'message' | 'silence' | null;
   agent_id: string | null;
   text: string | null;
   /**
@@ -448,6 +448,14 @@ type Address = {
     after_seconds: number;
   };
   language: string | null;
+  /**
+   * Conversation config bag — media handling, persona overrides, the Discord allowlist, and how a `oneshot` answers.
+   *
+   * `discord.reply` picks the delivery: `react` (the default) adds `discord.reaction` — `✅` unless named — to the message that triggered the run, `mention` answers beside it addressing whoever asked, `thread` opens a thread and answers inside it, and `none` delivers nothing at all. A run that fails delivers nothing in every mode, so a reaction always means the work was done; there is no failure marker.
+   *
+   * Read only for `oneshot`. A conversational `agent` in a guild *is* its thread — that is what its session is keyed on — so it always opens one.
+   *
+   */
   config: {
     [key: string]: unknown;
   } | null;
@@ -459,13 +467,29 @@ type Address = {
  *
  */
 type AddressActionSet = {
-  action: 'agent' | 'message' | 'silence' | null;
+  /**
+   * What an inbound message becomes.
+   *
+   * `agent` is a dialogue: the identity behind the message gets a session, and every later message on it continues the same one. `oneshot` runs the agent once and keeps nothing — no address, no actor, no session, no conversation — so each message is answered on its own. Choose it for work that is filed rather than discussed; choose `agent` when the answer depends on what came before.
+   *
+   * `message` delivers fixed text without running an agent, and `silence` answers nothing.
+   *
+   */
+  action: 'agent' | 'oneshot' | 'message' | 'silence' | null;
   agent_id?: string;
   text?: string;
   repeat?: 'every' | 'once' | {
     after_seconds: number;
   };
   language?: string;
+  /**
+   * Conversation config bag — media handling, persona overrides, the Discord allowlist, and how a `oneshot` answers.
+   *
+   * `discord.reply` picks the delivery: `react` (the default) adds `discord.reaction` — `✅` unless named — to the message that triggered the run, `mention` answers beside it addressing whoever asked, `thread` opens a thread and answers inside it, and `none` delivers nothing at all. A run that fails delivers nothing in every mode, so a reaction always means the work was done; there is no failure marker.
+   *
+   * Read only for `oneshot`. A conversational `agent` in a guild *is* its thread — that is what its session is keyed on — so it always opens one.
+   *
+   */
   config?: {
     [key: string]: unknown;
   };
@@ -2088,7 +2112,15 @@ type ChannelRoute = {
    * Tiebreak only, after specificity and `surface`.
    */
   priority: number;
-  action: 'agent' | 'message' | 'silence';
+  /**
+   * What an inbound message becomes.
+   *
+   * `agent` is a dialogue: the identity behind the message gets a session, and every later message on it continues the same one. `oneshot` runs the agent once and keeps nothing — no address, no actor, no session, no conversation — so each message is answered on its own. Choose it for work that is filed rather than discussed; choose `agent` when the answer depends on what came before.
+   *
+   * `message` delivers fixed text without running an agent, and `silence` answers nothing.
+   *
+   */
+  action: 'agent' | 'oneshot' | 'message' | 'silence';
   agent_id: string | null;
   text: string | null;
   /**
@@ -2098,6 +2130,14 @@ type ChannelRoute = {
     after_seconds: number;
   };
   language: string | null;
+  /**
+   * Conversation config bag — media handling, persona overrides, the Discord allowlist, and how a `oneshot` answers.
+   *
+   * `discord.reply` picks the delivery: `react` (the default) adds `discord.reaction` — `✅` unless named — to the message that triggered the run, `mention` answers beside it addressing whoever asked, `thread` opens a thread and answers inside it, and `none` delivers nothing at all. A run that fails delivers nothing in every mode, so a reaction always means the work was done; there is no failure marker.
+   *
+   * Read only for `oneshot`. A conversational `agent` in a guild *is* its thread — that is what its session is keyed on — so it always opens one.
+   *
+   */
   config: {
     [key: string]: unknown;
   } | null;
@@ -2111,13 +2151,29 @@ type ChannelRouteWrite = {
     [key: string]: unknown;
   };
   priority?: number;
-  action: 'agent' | 'message' | 'silence';
+  /**
+   * What an inbound message becomes.
+   *
+   * `agent` is a dialogue: the identity behind the message gets a session, and every later message on it continues the same one. `oneshot` runs the agent once and keeps nothing — no address, no actor, no session, no conversation — so each message is answered on its own. Choose it for work that is filed rather than discussed; choose `agent` when the answer depends on what came before.
+   *
+   * `message` delivers fixed text without running an agent, and `silence` answers nothing.
+   *
+   */
+  action: 'agent' | 'oneshot' | 'message' | 'silence';
   agent_id?: string;
   text?: string;
   repeat?: 'every' | 'once' | {
     after_seconds: number;
   };
   language?: string;
+  /**
+   * Conversation config bag — media handling, persona overrides, the Discord allowlist, and how a `oneshot` answers.
+   *
+   * `discord.reply` picks the delivery: `react` (the default) adds `discord.reaction` — `✅` unless named — to the message that triggered the run, `mention` answers beside it addressing whoever asked, `thread` opens a thread and answers inside it, and `none` delivers nothing at all. A run that fails delivers nothing in every mode, so a reaction always means the work was done; there is no failure marker.
+   *
+   * Read only for `oneshot`. A conversational `agent` in a guild *is* its thread — that is what its session is keyed on — so it always opens one.
+   *
+   */
   config?: {
     [key: string]: unknown;
   };
@@ -2268,9 +2324,17 @@ type ChannelList = {
  *
  */
 type ChannelDefaultAction = {
-  action: 'agent' | 'message' | 'silence';
   /**
-   * The agent that answers, when `action` is `agent`.
+   * What an inbound message becomes.
+   *
+   * `agent` is a dialogue: the identity behind the message gets a session, and every later message on it continues the same one. `oneshot` runs the agent once and keeps nothing — no address, no actor, no session, no conversation — so each message is answered on its own. Choose it for work that is filed rather than discussed; choose `agent` when the answer depends on what came before.
+   *
+   * `message` delivers fixed text without running an agent, and `silence` answers nothing.
+   *
+   */
+  action: 'agent' | 'oneshot' | 'message' | 'silence';
+  /**
+   * The agent that answers, when `action` is `agent` or `oneshot`.
    */
   agent_id: string | null;
   /**
@@ -2289,7 +2353,12 @@ type ChannelDefaultAction = {
    */
   language: string | null;
   /**
-   * Conversation config bag — media handling, persona overrides, the Discord allowlist.
+   * Conversation config bag — media handling, persona overrides, the Discord allowlist, and how a `oneshot` answers.
+   *
+   * `discord.reply` picks the delivery: `react` (the default) adds `discord.reaction` — `✅` unless named — to the message that triggered the run, `mention` answers beside it addressing whoever asked, `thread` opens a thread and answers inside it, and `none` delivers nothing at all. A run that fails delivers nothing in every mode, so a reaction always means the work was done; there is no failure marker.
+   *
+   * Read only for `oneshot`. A conversational `agent` in a guild *is* its thread — that is what its session is keyed on — so it always opens one.
+   *
    */
   config: {
     [key: string]: unknown;
@@ -2300,7 +2369,15 @@ type ChannelDefaultAction = {
  *
  */
 type ChannelDefaultActionInput = {
-  action: 'agent' | 'message' | 'silence';
+  /**
+   * What an inbound message becomes.
+   *
+   * `agent` is a dialogue: the identity behind the message gets a session, and every later message on it continues the same one. `oneshot` runs the agent once and keeps nothing — no address, no actor, no session, no conversation — so each message is answered on its own. Choose it for work that is filed rather than discussed; choose `agent` when the answer depends on what came before.
+   *
+   * `message` delivers fixed text without running an agent, and `silence` answers nothing.
+   *
+   */
+  action: 'agent' | 'oneshot' | 'message' | 'silence';
   agent_id?: string;
   text?: string;
   repeat?: 'every' | 'once' | {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@naturali/sdk",
-  "version": "0.135.0",
+  "version": "0.136.1",
   "description": "TypeScript SDK for the naturali.ai API, generated from its OpenAPI specs",
   "type": "module",
   "sideEffects": false,
@@ -31,7 +31,7 @@
   },
   "devDependencies": {
     "@hey-api/openapi-ts": "^0.99.0",
-    "@naturali/api": "0.135.0",
+    "@naturali/api": "0.136.1",
     "@ttoss/openapi-codegen": "^0.3.1",
     "@types/node": "^26.5.1",
     "tsdown": "^0.23.0",