Skip to content

ChatWalaʻau v0.92.0

Choose a tag to compare

View all tags
@motojinc25 motojinc25 released this 30 Jun 23:36
v0.92.0
b2bac4c

This release adds one new feature to ChatWalaʻau: Pipeline Jobs (with a native management screen).

Highlights

Pipeline Jobs (v0.92.0)

  • A dedicated screen for data-processing jobs. RAG ingestion -- and future data-processing job types -- now run on an in-process Pipeline Job engine with a native management portal. Open the new Pipelines icon in the sidebar footer (next to Declarative Agents) to submit a job, watch live progress, cancel or delete it, and review a per-job run history with captured logs.
  • Clear separation from Cron. Cron jobs (scheduled scripts) and Pipeline jobs (on-demand data processing) are now distinct surfaces with their own icons. Pipeline jobs run only curated in-process job types (no shell, no coding-workspace gate), so the subsystem is on by default -- unlike the Cron Scheduler, which stays off by default.
  • Run history with logs. Every job execution is recorded with a captured log you can open from the run timeline (previously only a final result was kept).
  • Three ways to run a job. Submit from the portal (a job-type form, e.g. rag-ingest with a PDF path), from the REST API (/api/pipeline/*), or from the assistant via the manage_pipeline tool -- all sharing one engine and store, so chat and portal never diverge.
  • Configurable. PIPELINE_ENABLED (default true), PIPELINE_JOBS_DIR (default .pipeline), PIPELINE_OUTPUT_MAX_BYTES, and PIPELINE_MAX_CONCURRENT_JOBS.

Breaking changes (read first)

No user data is lost: RAG ingestion remains fully available (via the Pipelines portal and the manage_pipeline tool), and your ChromaDB vector data (CHROMA_DIR) is untouched. Upgrading operators MUST act on the following:

  • BATCH_JOBS_DIR is removed, replaced by PIPELINE_JOBS_DIR (default .pipeline). If you set a custom BATCH_JOBS_DIR, rename the key. Existing .jobs contents are not auto-migrated (ephemeral processing records with no run history).
  • The batch background server is removed. If you keep an operator backend/mcp_servers.jsonc, delete the "batch" entry -- otherwise every agent run fails to start it. The bundled default config is already updated.
  • The batch job tools and the in-chat batch dashboard are removed. Use the Pipelines portal, the /api/pipeline/* API, or the manage_pipeline tool instead.

Included in this release

This release includes implementation work from:

  • v0.92.0 through v0.92.0

Notes

  • Internal design management content and architecture control artifacts are intentionally omitted from this release note.

Installation

See the repository README for setup and usage instructions.

Version

  • Release version: 0.92.0
  • Previous release: 0.91.0
Assets 2
Loading