DOSIA Monthly Brief · 2026-04 · ByteSpike integration + 5-layer file system goes live

April was the month DOSIA stopped being a single-account client and became a real multi-tenant agent host. ByteSpike provider, a five-layer file system from session to enterprise, and a native-binary SDK that drops startup by ~30%.

April 30, 2026KL6 min read

We ship DOSIA on a two-week cadence and publish a brief every two months covering the meaningful changes — not the patch notes. April 2026 was the first month where the trajectory of the app changed shape: from a single-account agent client into a multi-tenant host with first-class gateway, file, and identity layers.

1. What shipped this month

Five patch releases and one minor — v0.2.0 through v0.2.5. The patches were mostly stability and ergonomics; the minor cut is the one to look at.

MCP service-management panel (#205) — toggle servers per-conversation without restart, see live tool inventory.
sudo-command pre-check (#206) — preview shell commands before approval, with a Yes-once / Yes-always switch.
Rate-limit display in the chat header (#204) — DOSIA surfaces upstream provider's limit and resets countdown, no more guessing why a stream paused.
Open-on-latest-conversation (#203) — opening DOSIA goes to your last thread by default, optional via Preferences.

2. ByteSpike integration milestone

DOSIA now speaks ByteSpike. One key gives you 8 platforms and 23 models — Claude, GPT, Gemini, DeepSeek, Doubao, GLM, Kimi, MiniMax — through the same gateway, with failures-don't-bill semantics and per-request credit estimates surfaced in the DOSIA token-usage strip.

Setup is three clicks: Settings → Providers & Models tab → Add ByteSpike provider. DOSIA pulls the model list from ByteSpike's /v1/models endpoint, hydrates the model picker, and you're routing through the gateway on the next prompt.

DOSIA Settings → Providers & Models pane showing the Add ByteSpike provider dialog with API key field and detected model list — Adding ByteSpike as a provider in DOSIA's settings — the model list hydrates from /v1/models on save.

“We didn't build a separate ByteSpike client. DOSIA's existing Provider abstraction was already shaped right; we taught it the ByteSpike dialect and shipped.”

3. The 5-layer file system goes live

DOSIA's documents and context now live across five layers, each with explicit ownership and sync semantics. The split lets the same DOSIA install serve a solo user and an enterprise team without configuration churn.

Five-layer DOSIA file system diagram — Session, Personal, Project, Role, Enterprise — with arrows showing scope and persistence boundaries — Five layers, one binary — the difference between personal and enterprise mode is configuration, not code.

L1 Session — ephemeral, in-conversation. Cleared when the thread closes.
L2 Personal — your local-disk DOSIA home. Across all your conversations.
L3 Project — a folder you point DOSIA at, with its own context boundary and gitignore awareness.
L4 Role — a sharable persona file (engineer / sales / ops) that loads system-prompt-equivalent context on demand.
L5 Enterprise — NAS or self-hosted shared store, RBAC-gated. Multiple seats, one source of truth.

Personal-edition users stay on L1–L4 against local disk; enterprise-edition users get L5 pointed at their team's NAS or a self-hosted ByteSpike-Enterprise file daemon. The same DOSIA binary handles both; the difference is configuration, not code. PR #154 introduced the layer schema, #159 made the SDK aware.

4. SDK 0.2.113 — native binary, faster startup

Pre-v0.2.5 DOSIA shipped a forked cli.js as the SDK entry point. We've migrated to spawning the official native binary directly, with cross-arch packaging — separate macOS arm64 (M-series) and x64 (Intel) bundles in one universal installer.

Side-by-side comparison: pre-v0.2.5 fork cli.js path vs v0.2.5+ native binary spawn path, with cold-start timing on each — Same DOSIA prompt, two SDK paths — native binary cuts cold start by roughly 30%.

Env-var precedence is now replace (not merge) — the SDK strictly honors the caller's environment, no surprise inheritance from DOSIA's own shell.
Cold-start time dropped ~30% versus the cli.js fork path. First token latency benefits the most.
The native binary is the same one the upstream provider ships — security patches arrive faster, we no longer carry a fork.

5. Roadmap teaser — next two months

DOSIA × ByteSpike full SSO — "Sign in with ByteSpike" flow, one click, no manual API-key paste.
MCP integration panel — image-tools / video-tools / text-writing-tools loaded against the user's ByteSpike permissions, with per-model rate cards inline.
Browser-automation plugin v2 — DOSIA-driven headless Chrome with proper auth-context isolation per role file.

DOSIA is a free download from bytespike.ai/dosia; the source for the open parts lives on GitHub. If you ship agent workflows for a living and want to compare against your current setup, the 30-day Personal trial is the right place to start.

← All posts