Chatobby Runtime 0.5.4

Chatobby 0.5.4

• Workspace permissions: choose Read-only, Workspace or Full access, with saved workspace choices and one-time approval requests. These controls operate within Chatobby; OS sandboxing remains unavailable.
• Context and memory: report all open tabs accurately, keep useful task memory through tool calls, show clearer session summaries and refresh Memory across tabs.
• Page and tool fixes: open subagent conversations reliably, load Vault Events history and report stopped commands correctly.
• Updated model data, dependencies and bundled attribution.

Update the plugin, then use Chatobby's runtime update action. Chats, Projects,
memory and model connections are retained. macOS and Linux remain experimental;
macOS packages are not notarized.

Chatobby Runtime 0.5.3

Chatobby 0.5.3

Sandboxing is temporarily unavailable in this release. Chatobby runs with
Full file, command and network access under your operating-system account.
Read-only, Workspace and Network controls are hidden until sandboxing returns.

• Tools: file, shell and web tools no longer depend on native sandbox setup or cleanup. This addresses the startup and Stop failures reported after 0.5.2.
• File search: fix first-use setup on Windows when paths contain spaces or Unicode. Setup failures now identify the failed step, and downloads no longer delay Stop.
• Project history: memory and session-search tools stay scoped to the current Project or Vault chat. These query filters do not restrict Full-access file or shell tools.
• Streaming: responses update incrementally without repeatedly rebuilding completed text. Long reasoning stays in a scrollable panel and folds when finished.
• Memory retrieval: reduce repeated search work before prompts while preserving ranking and workspace filters.
• Permissions: show the current Full-access behavior directly. Obsidian app access and enabled MCP tools remain separate choices.

Update the plugin through Obsidian Community plugins, then choose Update in
Chatobby if the runtime version differs. Updating stops current work, including
subagents. Chats, Projects, memory, model connections and saved access choices
are retained; saved Read-only, Workspace and Network choices are inactive in 0.5.3.

macOS and Linux remain experimental. macOS packages are not notarized. Default
web search may still encounter search-provider bot challenges.

Report a problem or share feedback

Chatobby Runtime 0.5.2

Chatobby 0.5.2

• First installation: fix permission initialization that could prevent chats and tools from working in a new vault.
• Search continuation: fix cursor-only web and image searches being rejected after input validation.
• Parallel tools: fix a startup race that could report an MCP disconnect when tools connected at the same time.
• Windows workspace access: fix unchanged Project records being mistaken for corrupt data while sandboxed tools run together. Reduce repeated startup checks that delayed tool connections.
• Linux tools: fix a missing startup dependency that prevented sandboxed file and web tools from starting. Report child startup errors with their actual exit code.
• macOS tools: include the system paths and resolver access needed by sandboxed commands, and preserve verified filesystem aliases through runtime startup.
• Runtime updates: show both versions and an Update action when the plugin and runtime differ. Updating stops current work, including subagents, so saved agents cannot block installation.
• Accurate progress: show success only after the new runtime connects. Report a failed stop or installation and keep the previous package available for recovery.
• Interrupted work: show abandoned tool calls as interrupted after reopening a chat, rather than leaving them marked as preparing.
• Restarting: correctly restart if Chatobby is still connecting after a plugin reload.
• Tool failures: distinguish missing files, denied access, connection failures and sandbox errors. Keep a matching diagnostic category in the local runtime log.
• Agent context: report the actual runtime version separately from the plugin version.

Update the plugin through Obsidian Community plugins, then choose Update in Chatobby if the runtime version differs. Runtime updates are manual. Chats, Projects, memory and model connections are preserved; interrupted agents do not restart automatically.

This update includes the 0.5.1 Windows path, command-startup, cancellation and web-search fixes. Default web search can still encounter provider bot challenges. macOS and Linux remain experimental; macOS packages are not notarized.

Report a problem or share feedback

Chatobby Runtime 0.5.1

Chatobby Runtime 0.5.1

• Fix Windows folder-name casing and system path aliases that could prevent constrained file reads, shell commands and web tools from starting.
• Refresh callable tools during an ongoing chat when access changes. Keep new pages and MCP connections working after a server stops with completed cleanup.
• Fix an intermittent Windows clock comparison that could prevent a running command from stopping cleanly.
• Handle short commands that exit before stdin closes, without losing actual input or process errors.
• Improve default DuckDuckGo search with regional rankings, separate queries for selected sites, exclusions, usable-result filtering and real pagination. Pace requests and preserve useful results when a later page fails.
• Preserve actual connection, permission and startup errors. Validate the selected Obsidian vault before CLI execution, including errors returned with exit code zero.
• Clarify agent guidance for direct shell invocation, search queries, continuation and evidence reporting.

Update the Chatobby connector to 0.5.1, then install the matching runtime update through Chatobby. Chats, Projects, memory and model connections are preserved. The protocol and stored-data schemas are unchanged.

Default search works without an API key. DuckDuckGo can still return bot challenges; Chatobby reports that cause and retains other successful results where available. No new search provider is added in this patch.

Runtime packages include matching native component inventories, notices, build recipes and applicable source material. All five targets must pass native and package qualification before publication. Windows receives interactive Obsidian acceptance. macOS and Linux remain experimental; representative physical-device acceptance, including macOS 11, is not established. Linux targets ordinary glibc desktops; Flatpak, Snap and musl remain unverified.

Packages are Ed25519-signed. Windows has no Authenticode signature; macOS uses ad-hoc signing and is not notarized. Obsidian app tools retain their separate app-access boundary.

Installation and updates · Report an issue

Chatobby Runtime 0.5.0

Chatobby Runtime 0.5.0

Vault and Project workspaces

• Read-only and Workspace access work in ordinary Vault chats as well as Projects. Network access starts On and can be switched independently.
• Windows supports compatible existing PowerShell installations. Stop cancels foreground work and cleans up its owned processes, including longer commands.
• Full access uses the permissions available to your operating-system account.
• Archive Projects with their chats and restore them later. Permanent Project deletion removes Chatobby data while keeping attached note folders.

Models and connections

• Use ChatGPT, GitHub Copilot and xAI subscription connections with Chatobby's harness, alongside API keys and supported token plans.
• Discover and test models from a running local server. Use reported context limits and server output defaults, or set individual overrides.
• Subscription model lists refresh from the connected account. Sign-in opens the default browser.

Agents, Channels and memory

• Keep specialist agents available across turns, with custom prompts, models and skills.
• Invite agents into Channels to plan and coordinate. Address selected participants or send direct messages; invitations can wake available sessions.
• Combine steering messages waiting at the next intake. Agents have improved guidance for parallel tools, background work and finishing the user's task.
• Maintain editable memory, search earlier sessions with richer read-only queries and schedule recurring Events.
• Use expanded native guidance for Obsidian commands, API discovery, tabs, editors, settings and local-model setup.

Obsidian interface

The paired Chatobby 0.5.0 connector
adds named native tabs, a redesigned sidebar, bounded streaming reasoning,
simpler Memory and Permissions pages, improved Channels, onboarding and update
highlights. The core harness remains free, stores chats and memory locally and
has no telemetry.

Install or update

Update Chatobby through Obsidian Community plugins, then confirm the runtime
installation or update inside Chatobby. Both components use version 0.5.0.
See INSTALL.md. The runtime verifies package signatures and file
hashes before activation and preserves the previous installation for recovery.

Native components and platforms

This release packages Landstrip built from pinned inputs. The runtime bundles
include matching component inventories, notices, build recipes and applicable
source material. Required sandbox qualification runs during development and
release testing; users do not need to run a device-verification checklist.

All five native/package targets passed release qualification. Interactive
Obsidian acceptance was performed on Windows. macOS and Linux remain
experimental; representative physical-device acceptance, including macOS 11,
is not established. Linux targets ordinary glibc desktops; Flatpak, Snap, musl
and other confinement environments remain unverified.

Runtime packages are Ed25519-signed. Windows has no Authenticode signature;
macOS uses ad-hoc signing and is not notarized. Chatobby does not change OS
security settings. Obsidian app tools execute in Obsidian and are controlled
separately from native file and shell restrictions.

Chatobby Runtime 0.4.3

Chatobby Runtime 0.4.3

Chatobby Runtime 0.4.3 is a focused long-session reliability update. Automatic
compaction can now occur during multi-step agent work and continue the same
request, rather than waiting indefinitely for the complete turn or leaving a
session unusable after a rejected checkpoint.

Compaction that continues the work

• When the configured threshold is crossed during a tool-driven turn,
  Chatobby waits for all results from the current tool boundary, checkpoints,
  and resumes the same agent turn from an explicit continuation handoff.
• The tool that reached the boundary is neither terminated nor replayed.
• The handoff restates the current objective, unresolved user requests, and
  concrete next actions so the resumed agent does not wait for the user to
  repeat the request.
• User messages arriving during maintenance remain queued after the accepted
  checkpoint and are not summarized into the older snapshot.

Defined checkpoint quality

Checkpointing now has three explicit success levels:

1. Full fidelity preserves authoritative continuity plus useful active
   skills, capabilities, and retained-result handles within their quotas.
2. Continuity safe preserves every unresolved request, active or blocked
   work item, decision, evidence state, operational handle, authority receipt,
   and next action while dropping optional working context when needed.
3. Host-reconciled minimum deterministically rebuilds conservative
   continuity from the runtime's immutable inventory if the model exhausts its
   bounded correction attempts.

Checkpoint validation keeps one immutable inventory revision, provides
field-specific repairs, and asks the model to drop optional retained results,
capabilities, and skills before sacrificing continuity. Cancellation and
provider failures remain fail-closed: the original context stays authoritative
and usable.

Platform status

Windows remains the primary physically tested desktop path. Native macOS and
Linux packages continue as best-effort experimental support pending a broader
physical-device acceptance matrix.

Chatobby Runtime 0.4.2

Chatobby Runtime 0.4.2

Chatobby Runtime 0.4.2 improves long-session continuity, skill and capability
discovery, memory maintenance, and safe Obsidian automation.

Context and compaction

• Mutable Project, permission, task, memory, runtime, channel, subagent, and
  Obsidian state now advances at the end of the conversation context, preserving
  a stable prompt prefix for providers that support prompt caching.
• Context compaction explicitly reconciles active skills, discovered
  capabilities, retained-result handles, work, decisions, requirements, and
  evidence before committing a checkpoint.
• Failed compaction preserves the original usable context and reports the last
  maintenance stage plus a bounded provider or validation cause.
• New unnamed sessions receive a concise title before their first normal
  response. Private bootstrap and checkpoint tools remain outside the feed,
  exports, permission settings, and ordinary tool discovery.

Skills, memory, and retrieval

• Native and managed skill loaders now identify their separate catalogues and
  guide the agent toward the other loader when a skill is requested from the
  wrong source.
• Capability search supports explicit domains and bounded exact, prefix,
  ranked, and fuzzy discovery without loading every specialist schema into the
  initial prompt.
• Memory search adds structured filters, typo-tolerant ranked pagination,
  bounded multi-record reads, and atomic revision-checked maintenance.
• Explicit follow-up commitments can be retained as typed obligations with
  revisioned completion evidence and current-policy enforcement.

Obsidian automation and safety

• Chatobby can discover a version-pinned Obsidian API catalogue and attach
  focused symbol guidance when an obsidian eval task needs it.
• Eval output is parsed as bounded structured JSON. Catastrophic operations are
  denied through the canonical permission gate without broadly blocking
  ordinary scripting.
• Obsidian application reload and restart require a fresh user decision, even
  under Full access or after an earlier generic CLI approval.
• An empty AGENTS.md now falls back to compatible CLAUDE.md guidance;
  non-empty AGENTS.md retains precedence.

Removed

The retired subagent-only Flows surface has been removed from the active
runtime tools, permissions, agent guidance, and native skills.

Alpha platform status

Windows remains the primary physically tested desktop path. Native macOS and
Linux packages remain best-effort experimental support pending a broader
physical-device acceptance matrix. macOS packages are ad-hoc signed and not
Apple-notarized; Linux packages initially target glibc desktop environments.

Chatobby Runtime 0.4.1

Chatobby Runtime 0.4.1

Chatobby Runtime 0.4.1 is a focused reliability update for long-running
sessions, automatic context compaction, and the runtime-owned Obsidian command
surface.

Fixed

• Prompt requests now wait through runtime-managed compaction rather than
  failing after the connector's former generic 30-second request deadline.
• Completed compaction checkpoints are applied once. A replayed completion can
  no longer make the next user message disappear or leave the session unable
  to continue.
• Context usage is rebuilt and published after compaction, including when a
  queued prompt starts immediately after the checkpoint completes.
• Provider failures that contain no assistant text now produce an explicit
  error result instead of looking like a request that was never sent.
• Obsidian CLI failures now preserve structured command, validation, process,
  and output evidence so the agent can distinguish invalid input from runtime
  and application failures.

Configuration

The model-specific automatic-compaction threshold may now be set from 10 to 95
percent. Existing defaults have not changed; the lower bound is available for
very large context windows and for users who deliberately want earlier
checkpoints.

Agent guidance

• Native Obsidian skills are organized as progressively loaded suites with
  focused references, verification, and recovery guidance.
• Runtime tool and skill discovery exposes compact searchable capability
  summaries rather than placing every specialist contract in the initial
  prompt.

Alpha platform status

Windows remains the primary physically tested desktop path. Native macOS and
Linux packages are published as best-effort experimental support pending a
broader physical-device acceptance matrix.

Chatobby Runtime 0.4.0

Chatobby Runtime 0.4.0

Chatobby 0.4.0 strengthens the full working loop: choosing where a chat works,
connecting models, finding the right capability, preserving useful context,
and verifying results inside Obsidian.

Highlights

• Connect compatible local model servers from Chatobby Settings, including
  Ollama, LM Studio, vLLM, llama.cpp, and OpenAI- or Anthropic-compatible
  endpoints. Optional managed llama.cpp profiles can start, stop, restart, and
  launch on demand without conflating the server process with the model
  connection that chats select.
• Work with existing vault or external Project folders, multiple attached
  roots, an explicit primary working directory, and current Project context.
• Keep prompts submitted during automatic compaction pending until rebuilt
  context is ready. Compaction now has dedicated progress, a durable receipt,
  and an immediate usage refresh.
• Keep large results available through the working turn and query retained
  evidence through stable IDs without recursively producing new result IDs.
• Discover tools, installed Obsidian commands, MCP tools, and eleven maintained
  native skill suites through one ranked capability gateway.
• Prefer ordinary file tools and bounded terminal scripts for durable content,
  while retaining Obsidian CLI for live index, history, link updates, settings,
  plugin lifecycle, command-palette, and developer diagnostics.
• Return typed Obsidian CLI outcomes and recovery instructions instead of a
  generic internal error for invalid screenshot paths, image-model mismatches,
  or render-dependent command sequences.
• Remove retired media/download helpers and their bundled
  Python/Pillow/yt-dlp/NumPy environment.

Alpha platform status

Windows remains the primary tested desktop path. The production-candidate
matrix builds and exercises Windows x64, macOS Apple Silicon and Intel, and
glibc Linux x64 and arm64 packages. macOS and Linux remain experimental until
representative physical-device acceptance is complete; Flatpak, Snap, musl,
and other confined Linux environments remain unverified.

Install and update through the Chatobby Community plugin. Runtime archives in
this repository are signed package inputs for the plugin, not standalone
installers.

Chatobby Runtime 0.3.4

Chatobby Runtime 0.3.4

Chatobby 0.3.4 makes Projects reliable across several vault or external folders
and gives Project chat search durable message-level results.

What changed

• Projects can register one primary folder and several attached folders in one
  atomic operation. External folders are used in place rather than replaced by
  same-named vault copies.
• Primary and attached folders receive the same Project-root permission
  treatment. The primary folder only supplies the default working directory
  and relative-path base.
• Project folder and effective current-chat permission facts are refreshed as
  replaceable runtime context, so the agent sees changes before its next model
  call without persisting local paths into the transcript.
• Safely resolved paths outside a Project use the active policy's ordinary
  external-directory rule instead of producing a false unresolved-root denial.
• Project chat-content search returns bounded, paginated matches with stable
  session and message targets so the connector can resume the right chat and
  navigate to the exact result.

This remains public-alpha software. macOS and Linux support remain experimental
until representative physical-device acceptance is completed.