Remote Bob v1.0.4

Video: Remote Bob in Slack

Watch the full video (MP4, 1:50, 1080p)
· Download MP4
· Editable source and chapters

An English-only visual tutorial, created with
HyperFrames, covering the
features available in Remote Bob v1.0.4:

Time	Topic
00:00	Remote Bob in Slack
00:10	App setup, tokens, container and invitation
00:24	Request a task without an @mention
00:37	Continue with context in the same thread
00:48	Attach images and documents
01:01	Cancel an active job
01:12	Recurring reports, UTC and channel delivery
01:27	Chat with /jobs versus verification/retry with /run
01:39	Trusted channels, local API and persistent files

Illustrative demo, not a live session recording. Responses and the
schedule ID are examples. No real Slack or IBM tasks were executed to produce
the video. All on-screen text is in English, including example conversations,
channel names and filenames. The video has no audio.

The original release notes are preserved below. The video is hosted in the
repository and linked here as documentation; the published v1.0.4 tag and
runtime code have not changed.

Highlights

• Remote Bob is the new project name. The repository, Compose project,
  image, and container are named remote_bob; the Compose service remains bob.
• Active jobs remain available for polling, streaming, and cancellation when
  BOB_MAX_JOBS is exceeded. Only finished runs are evicted, oldest first.
• Background process launch errors now reach a terminal failure state with
  exit code 126 and a visible diagnostic. A missing executable still uses 127.
• Invalid bytes in background output are replaced instead of leaving a job
  unfinished. Regression tests cover final SSE events and verify/retry flows.
• REMOTE_BOB_URL is the preferred API URL setting for Slack and the scheduler.
  Existing HARNESS_URL settings remain supported as a fallback.
• Updated README, Slack setup guides and manifest, runtime project context,
  OpenAPI export, and Postman collection.

Upgrade Notes

Stop the old deployment using its existing Compose file before switching to
this release, so it releases port 8080:

podman compose down
git remote set-url origin https://github.com/BrUn3y/remote_bob.git
git fetch origin --tags
git switch --detach v1.0.4
podman compose up --build -d

Keep your existing .env and workspace/ directory. The
./workspace:/workspace bind mount is unchanged; attachments and persisted
schedules stay in that directory. A fresh checkout needs those files transferred
before starting. Docker users can replace podman with docker.

The previous BrUn3y/IBM_Bob_Harness repository URL redirects to the renamed
repository. Do not reuse the previous repository name if that redirect should
remain available.

An already-installed Slack app must be renamed separately in Slack's app
settings: app name Remote Bob, bot display name remote_bob. Existing
tokens remain usable; editing the manifest does not rename a live app.

API paths, job types, orchestration markers, IBM's bob command, and .bob/
configuration remain compatible. The API version remains 1.4.0. The pinned
IBM Bob Shell 2.0.5 and Node.js 24.21.0 runtimes are unchanged.

Verification

• 125 tests passed on Python 3.12.14, with unhandled pytest thread
  exceptions treated as errors.
• Includes local Python/bash integration tests for output decoding,
  cancellation, timeout, and verify/retry, without live IBM or Slack calls.
• Python compilation, Bash syntax, Compose configuration, and Git whitespace
  checks passed.
• One existing Starlette/AnyIO deprecation warning remains.

This is a source release. No prebuilt container was published, and the complete
container image was not rebuilt or exercised against live IBM/Slack services
for this release.

Changes

• Job lifecycle reliability: #7
• Rename to Remote Bob: #8
• Full comparison: v1.0.3...v1.0.4