clisbot 0.1.50 → 0.1.51

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.
package/README.md CHANGED
@@ -69,8 +69,8 @@ It is not just a tmux bridge with chat glued on top. `clisbot` treats Slack and
69
69
  ### I Just Want To Know What Changed Recently
70
70
 
71
71
  - start with [Recent Release Highlights](#recent-release-highlights)
72
- - then read [v0.1.50 Release Notes](docs/releases/v0.1.50.md) or the
73
- [v0.1.50 Release Guide](docs/updates/releases/v0.1.50-release-guide.md)
72
+ - then read [v0.1.51 Release Notes](docs/releases/v0.1.51.md) or the
73
+ [v0.1.51 Release Guide](docs/updates/releases/v0.1.51-release-guide.md)
74
74
 
75
75
  ## Why I Built This
76
76
 
@@ -89,7 +89,7 @@ The challenge is not whether AI is useful. It is how to make it work at enterpri
89
89
  - Team-first by design, with `AGENTS`, `USER`, and `MEMORY` context bootstrapping shaped for shared team reality instead of only personal solo-assistant flows.
90
90
  - Shared-surface permission control is a first-class feature: a bot can be in a team group but still answer only the specific people you allow there, while sensitive control actions stay behind explicit auth roles and permissions.
91
91
  - Useful for coding, operations, teamwork, and general assistant work, with fast chat controls such as `!<command>`, `/bash <command>`, `/queue`, `/loop`, `/streaming`, and `/mention`.
92
- - New in `v0.1.50`: the AI-native control experience is much better. You can increasingly ask the bot in normal chat to update itself and explain what changed, help with onboarding, add or configure bots and agents, or create recurring schedules and loops for you instead of relying only on slash commands.
92
+ - New in the `v0.1.50` to `v0.1.51` stable line: the AI-native control experience is much better, and `v0.1.51` also stretches the default runner startup window to 60 seconds so slower Codex, Claude, and Gemini launches do not time out so early.
93
93
 
94
94
  ## Who This Fits Best
95
95
 
@@ -185,12 +185,12 @@ Next steps:
185
185
  - `clisbot` also has a smart autopairing path to reduce first-run friction. If
186
186
  you send the bot a DM within the first 30 minutes, you can usually claim the
187
187
  owner role immediately and start using it without a separate pairing round.
188
- - New from `v0.1.50`: the AI-native operator experience is much stronger. You
188
+ - New from the current `v0.1.50` to `v0.1.51` stable line: the AI-native operator experience is much stronger. You
189
189
  can increasingly ask the bot through chat to explain how to use it, update
190
190
  itself and summarize what's new, help onboard you, create or add a new bot or
191
191
  agent, or set up loops and schedules for recurring work instead of relying
192
192
  only on slash commands.
193
- - Existing configs from any version before `0.1.50` update directly to `0.1.50` automatically on first run. clisbot writes a backup first under `~/.clisbot/backups/`, then rewrites the config to the current shape.
193
+ - Existing configs from any version before `0.1.50` still update directly on first run when you install `v0.1.51`. clisbot writes a backup first under `~/.clisbot/backups/`, then rewrites the config to the current `0.1.50` schema shape.
194
194
  - Shared Slack channels, Slack groups, Telegram groups, and Telegram topics are a separate gate: normal users need an explicit route such as `group:<id>` or `topic:<chatId>:<topicId>` before the bot will talk there. Legacy Slack `channel:<id>` input still works for compatibility.
195
195
  - After a shared surface is admitted, per-surface sender control comes from the bot's default shared rule `groups["*"]` plus any route-local `allowUsers` or `blockUsers`.
196
196
  - With that permission model, a bot can be added to a team group but still be
@@ -237,6 +237,9 @@ What happens next:
237
237
 
238
238
  ## Recent Release Highlights
239
239
 
240
+ - `v0.1.51`: raises the default runner startup window to 60 seconds across the
241
+ standard CLI families and the shared runner fallback, so slower fresh launches
242
+ are less likely to fail before the first prompt can be submitted.
240
243
  - `v0.1.50`: a much more AI-native operator experience, where you can
241
244
  increasingly talk to the bot to manage itself; plus safer personal and team
242
245
  bots in real Slack and Telegram groups, automatic direct updates from older
@@ -245,7 +248,7 @@ What happens next:
245
248
  streaming/session isolation.
246
249
  - `v0.1.43`: more durable runtime recovery, clearer routed follow-up controls, more truthful tmux prompt submission checks, better queued-start notifications, and safer Slack thread attachment behavior.
247
250
 
248
- What `v0.1.50` most likely means for you:
251
+ What the current stable line most likely means for you:
249
252
 
250
253
  - The headline is AI-native control: ask the bot in chat to queue work,
251
254
  schedule recurring briefs, help update itself, explain release changes, or
@@ -268,6 +271,7 @@ Read the full notes here:
268
271
 
269
272
  - [CHANGELOG.md](CHANGELOG.md)
270
273
  - [Release Notes Index](docs/releases/README.md)
274
+ - [v0.1.51 Release Notes](docs/releases/v0.1.51.md)
271
275
  - [v0.1.50 Release Notes](docs/releases/v0.1.50.md)
272
276
  - [v0.1.43 Release Notes](docs/releases/v0.1.43.md)
273
277
  - [v0.1.39 Release Notes](docs/releases/v0.1.39.md)
@@ -302,7 +306,11 @@ Update note for existing installs:
302
306
  - Older installs before `v0.1.50` now update directly on first run with a
303
307
  backup written first, so most people can update and restart without a manual
304
308
  migration pass.
305
- - After you are on `v0.1.50`, future upgrades should feel much more AI-native:
309
+ - `v0.1.51` keeps that direct-upgrade path and does not introduce a new config
310
+ schema bump; the main runtime change is a longer default runner startup
311
+ window.
312
+ - After you are on the `v0.1.50` schema line, future upgrades should feel much
313
+ more AI-native:
306
314
  in many cases you can simply ask the bot to update `clisbot` to the latest
307
315
  version, and it can follow the update guide, perform the upgrade flow, then
308
316
  brief you on what changed.
@@ -410,7 +410,7 @@
410
410
  "--approval-mode=yolo",
411
411
  "--sandbox=false"
412
412
  ],
413
- "startupDelayMs": 15000,
413
+ "startupDelayMs": 60000,
414
414
  "startupRetryCount": 2,
415
415
  "startupRetryDelayMs": 1000,
416
416
  "startupReadyPattern": "Type your message or @path/to/file",
package/dist/main.js CHANGED
@@ -59472,7 +59472,7 @@ function convertLocalDateTimeToUtcMs(params) {
59472
59472
  var SUPPORTED_AGENT_CLI_TOOLS = ["codex", "claude", "gemini"];
59473
59473
  var SUPPORTED_BOOTSTRAP_MODES = ["personal-assistant", "team-assistant"];
59474
59474
  var SESSION_ID_PATTERN = "\\b[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}\\b";
59475
- var INTERACTIVE_CLI_STARTUP_DELAY_MS = 15000;
59475
+ var INTERACTIVE_CLI_STARTUP_DELAY_MS = 60000;
59476
59476
  var DEFAULT_AGENT_TOOL_TEMPLATES = {
59477
59477
  codex: {
59478
59478
  command: "codex",
@@ -60972,7 +60972,7 @@ var runnerDefaultsSchema = exports_external.object({
60972
60972
  socketPath: "~/.clisbot/state/clisbot.sock"
60973
60973
  }),
60974
60974
  trustWorkspace: exports_external.boolean().default(true),
60975
- startupDelayMs: exports_external.number().int().positive().default(3000),
60975
+ startupDelayMs: exports_external.number().int().positive().default(60000),
60976
60976
  startupRetryCount: exports_external.number().int().min(0).default(2),
60977
60977
  startupRetryDelayMs: exports_external.number().int().min(0).default(1000),
60978
60978
  promptSubmitDelayMs: exports_external.number().int().min(0).default(150),
@@ -61452,7 +61452,7 @@ var agentsDefaultsSchema = exports_external.object({
61452
61452
  socketPath: "~/.clisbot/state/clisbot.sock"
61453
61453
  },
61454
61454
  trustWorkspace: true,
61455
- startupDelayMs: 3000,
61455
+ startupDelayMs: 60000,
61456
61456
  startupRetryCount: 2,
61457
61457
  startupRetryDelayMs: 1000,
61458
61458
  promptSubmitDelayMs: 150,
@@ -61913,7 +61913,7 @@ var clisbotConfigSchema = exports_external.object({
61913
61913
  socketPath: "~/.clisbot/state/clisbot.sock"
61914
61914
  },
61915
61915
  trustWorkspace: true,
61916
- startupDelayMs: 3000,
61916
+ startupDelayMs: 60000,
61917
61917
  startupRetryCount: 2,
61918
61918
  startupRetryDelayMs: 1000,
61919
61919
  promptSubmitDelayMs: 150,
@@ -62042,7 +62042,7 @@ var clisbotConfigSchema = exports_external.object({
62042
62042
  socketPath: "~/.clisbot/state/clisbot.sock"
62043
62043
  },
62044
62044
  trustWorkspace: true,
62045
- startupDelayMs: 3000,
62045
+ startupDelayMs: 60000,
62046
62046
  startupRetryCount: 2,
62047
62047
  startupRetryDelayMs: 1000,
62048
62048
  promptSubmitDelayMs: 150,
@@ -62235,7 +62235,7 @@ var defaultOwnedRunnerFields = {
62235
62235
  ]
62236
62236
  };
62237
62237
  var defaultOwnedRunnerDefaultFields = {
62238
- startupDelayMs: 3000
62238
+ startupDelayMs: 60000
62239
62239
  };
62240
62240
  function isRecord5(value) {
62241
62241
  return typeof value === "object" && value !== null && !Array.isArray(value);
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "clisbot",
3
- "version": "0.1.50",
3
+ "version": "0.1.51",
4
4
  "private": false,
5
5
  "description": "Chat surfaces for durable AI coding agents running in tmux",
6
6
  "license": "MIT",