Skip to content
Pilotoo
v0.1

0.1.0 Latest

ChangelogHow versions work

Changelog

All notable changes to the kit are listed here, newest first. The format follows Keep a Changelog.

Unreleased — 0.1.0

Section titled “Unreleased — 0.1.0”

The first public release. The packages are not on a registry yet; see Installation.

Brain (preview)

Section titled “Brain (preview)”
  • @pilotoo/memory-protocol, @pilotoo/memory-core and @pilotoo/memory-server: named memories of three kinds (graph, collection, personal), access by membership and labels, REST routes, a stateless MCP endpoint with six tools and per-memory token grants, PostgreSQL and pgvector stores, Bedrock and OpenAI-compatible adapters, and BrainKnowledgeSource for agents.
  • Graph memories resolve names before writing: pages keep every alias, a source’s names are matched against existing pages its audience can read, and doubtful matches become a possible duplicate for an admin. Compilation is transactional, a recompile is a diff, and sources added with an externalId are versioned.
  • Facts have a life: retired or superseded, never silently deleted, with a history an admin can show; deleting a source rebuilds what other sources still support, and erase removes everything derived. Facts from sources with the same labels consolidate into one entry.
  • Admins curate pages: merge, split, rename, lock, add and edit facts, keep two pages apart, and a Health scan, all with undo. See Curating a memory.
  • Personal memories reconcile a new fact with the old ones and answer add, update, delete or noop.
  • A memory’s knowledge language: pages in the language of their sources by default, or one fixed per memory; answers follow the question.
  • @pilotoo/web-auth: the Google sign-in, signed cookies and identity guard shared by Connect and Brain.
  • apps/brain-api with its web app, as a Docker image. See Brain.

Server

Section titled “Server”
  • @pilotoo/server: a NestJS module, PilotooModule.forRoot, with a Socket.IO streaming gateway, REST routes, PostgreSQL persistence and run replay.
  • Agents defined in YAML files, model profiles and providers, agent templates, and tenant agents managed through the API.
  • Server tools registered in code, with opt-in tools; subagents and background tasks.
  • Skills, attachments (S3 or custom store), scheduled runs, usage reporting and a model gateway.
  • Identity through a resolver, AUTH_IDENTITY_URL, or a fixed local identity.

Client

Section titled “Client”
  • @pilotoo/chat-core: an environment-agnostic client with session, conversation and agent catalogs, stores and a socket.io transport.
  • @pilotoo/chat-protocol: the typed wire protocol, versioned with a major and a minor number.
  • Client tools, blocking and one-way, declared per run.

UI

Section titled “UI”
  • @pilotoo/ui: DOM chat components (ChatProvider, ChatPanel), settings and design tokens for Tailwind v4.
  • @pilotoo/chat-ui: React Native chat components, also rendered on the web.

Voice

Section titled “Voice”
  • @pilotoo/voice: read-aloud and dictation behind ports, with browser engines.
  • @pilotoo/voice-native: a Tauri speech plugin for desktop.

Local backend

Section titled “Local backend”
  • @pilotoo/local-server: the same runtime on SQLite, with no PostgreSQL, for a user’s own machine and the desktop app.

Preview

Section titled “Preview”
  • Workflows: multi-step agent workflows with webhook and schedule triggers.
  • Connections: connect external services (GitHub, Gmail) for agents to use, as a library, over a tools API and MCP, from remote sources, or as the standalone Pilotoo Connect service.

Preview features may change before they are part of a release.