Early Access

Always-on AI runtime for local Linux work.

Breqy keeps an engine alive independently of any UI, preserves sessions, and lets agent processes do real work with policy and approvals in the loop.

Start locally Inspect the architecture
Mode
Local-first
Channel
TUI now
State
Durable
Stage
Early Access

Runtime control plane

online

Session

resume local-services-audit

message history persisted
tool approval awaiting user
event writer sequential

control

stop

steer

circuit-break

A2A envelope

event_type: tool.invocation
schema_version: v1
agent_id: breqy
status: approval_required

Engine

The durable core stays running.

The engine owns sessions, event history, policy, approvals, task state, and memory boundaries. Clients can disconnect without throwing away the thread.

Agents

Separate processes, explicit permissions.

Agents connect over typed A2A messages, keep their own runtime identity, and execute only the tools policy allows.

available

Engine daemon

Available in Slice 1: long-running engine process with durable sessions and typed event routing.

available

Textual TUI

Available in Slice 1: terminal UI for sessions, chat, tasks, approvals, controls, and logs.

available

Shell and filesystem tools

Available in Slice 1 through policy-mediated local tool execution and approval events.

Continuity

Sessions survive restarts and reconnects.

Breqy treats sessions as first-class operational threads with messages, tasks, participants, approvals, and durable events.

Safety

Tool use is visible before it matters.

Shell, filesystem, browser, and memory tools are routed through explicit policy checks, reusable approval grants, and the event log.

Steering

Stop, steer, or circuit-break.

The user can interrupt work, let an atomic step finish before redirecting, or hard-stop unsafe execution.

control primitive

Stop

Cancel active work as soon as safely possible.

control primitive

Stop and steer

Let the current atomic step finish, then re-plan.

control primitive

Steer

Update context and direction without losing the session.

control primitive

Circuit break

Hard-kill unsafe or stuck agent work and record it.

Topology

Engine, agents, and channels stay separate.

TUI now and future channels later connect only to the engine. Agents register separately and exchange canonical typed envelopes.

node 1

breqy-engine

Owns sessions, event log, memory boundaries, approvals, task state, and routing.

node 2

agent processes

Register over A2A, reason within granted constraints, and request mediated tool execution.

node 3

channel apps

Thin clients such as the Textual TUI. Future channels attach to the same runtime.

message path

Channel apps send typed envelopes to the engine. The engine persists, routes, and audits work before agents execute tools.

Install

Start the daemon, attach the TUI, keep working.

The early-access path is intentionally local: install the Python package, start the engine, launch the Textual TUI, then approve tool work as needed.

terminal sequence

  1. 01 Install dependencies uv sync
  2. 02 Start the engine breqy engine start
  3. 03 Open the TUI breqy tui
  4. 04 Authenticate a runner breqy auth copilot

Scope

Slice 1 first, no mystery claims.

Breqy is focused on the local engine, TUI, sessions, approvals, and native tools before expanding into richer channels and remote operations.

available in the current path

Engine daemon

Available in Slice 1: long-running engine process with durable sessions and typed event routing.

Textual TUI

Available in Slice 1: terminal UI for sessions, chat, tasks, approvals, controls, and logs.

Shell and filesystem tools

Available in Slice 1 through policy-mediated local tool execution and approval events.

deferred roadmap

Rich WebUI channel

Future Slice 2 work; this website is marketing/docs, not the browser channel itself.

SSH operations

Deferred remote-operation capability planned after the local Slice 1 runtime is stable.

Docker inspection workflows

Planned for Slice 2 and later; outside the current Early Access capability set.

Agent delegation depth

Future multi-agent expansion beyond the Slice 1 default runtime path.

Source

Built in the open, with auditability as a design constraint.

The website reflects the same discipline as the runtime: branch-gated delivery, testable contracts, docs, and explicit operational boundaries.

Open repository Run it locally