THE VERSION ARCHIVE

Progress, with
the receipts.

The evolution of the current codebase. Each snapshot has its own source, its own tools, and only the changes introduced in that version.

THE JOURNEY / NEWEST FIRST

One capability at a time.

  1. V18

    Tool & Scenario Crafting

  2. V17

    Request Thinking

  3. V16

    Kanban Planning & Execution

  4. V15

    Scenario home automation

  5. V14

    Incoming and outgoing channel messages

  6. V13

    A separate email service

  7. V12

    Edit, test and repair projects

  8. V11

    Projects built by scenario teams

  9. V10

    Personal Calendar

  10. V9

    Personality & Voice

  11. V8

    Local Web Research

  12. V7

    Scenario Memory

  13. V6

    Conditional Workflows

  14. V5

    Timers & Scheduling

  15. V4

    Managed Workspace

  16. V3

    Scenario Sub-agents

  17. V2

    C# Tool Calling

  18. V1

    Local Conversation

05 / DEVELOPMENT

scenario-managed timers and cron jobs

Adds persistent countdown timers, recurring intervals and five-field cron jobs, managed through saved scenarios. The main agent can peek at remaining seconds, next firing time and last outcome. Changes follow boot-fixed Ask/YOLO with exact host-only approvals. Timers begin at approval.

06 / DEVELOPMENT

Conditional steps and nested scenarios

Adds conditional XML steps and explicit nested saved scenarios. The application chooses branches from real workspace existence or input comparisons; each child starts fresh with explicitly bound inputs. The two-run file_branch_demo saves hello to first.txt, then again to second.txt. V5 is preserved as v5.0.0-alpha.1.

07 / DEVELOPMENT

Scenario Memory

Remember a name and simple personal facts across conversations. Conditional and nested scenarios handle storing, searching and forgetting, and returning greetings use the saved name.

08 / DEVELOPMENT

Web research through scenario subagents

Adds local Selenium web research through search, fetch, reader and synthesis scenarios. Bing, DuckDuckGo and Google are default engines; trusted JSON can add more. Five readable pages by default, 1-20 override, bounded replacement attempts. Schema 3 adds result bindings, bounded foreach and structured results. The final cited answer is copied unchanged; research is not automatically saved to memory.

09 / DEVELOPMENT

Five personalities, two voices and a new identity

Adds a persistent assistant profile: name, female/male/other identity, installed Kokoro voice and one of five personalities (default, pirate, space captain, butler or storyteller). Shared local commands and saved scenarios manage settings; automatic voice selection matches the identity while explicit IDs can override it. Scenario children may receive an optional task-specific personality in their system prompt. Empty/default child styles add no character instructions.

010 / DEVELOPMENT

A calendar managed by scenarios

Adds a persistent local calendar managed through saved scenarios: create, update, delete, read, search and today's agenda. Mutations use boot-fixed Ask/YOLO; exact prepared approval covers both event and reminder. Reminder time is requested, never silently defaulted. All-day dates stay dates; timed reminders store UTC with an explicit time zone. Due notices queue behind active chat/speech; missed reminders notify once after restart, with no action replay.

014 / DEVELOPMENT

Incoming and outgoing channel messages

Adds a standalone authenticated localhost messaging bridge and saved scenarios for channel discovery, incoming checks, status, isolated replies and outgoing messages. Incoming messages automatically run a fresh tool-less reply writer. Ask prepares the exact destination/text for a host decision; boot-selected YOLO sends automatically. Durable claims, signed proposals and idempotent send receipts prevent duplicate replies and preserve interrupted work for operator review. The initial dummy-discord transport is entirely local; no Discord account or real recipient is contacted. Agent and record...

015 / DEVELOPMENT

Scenario home automation

Adds task-specific scenarios for configured lights: device discovery, state, power on/off, whole-percent brightness and RGB colour. Boot-fixed Ask/YOLO, durable exact approvals, configuration checks and non-replayable uncertain sends keep network actions host-controlled. The example chat uses an isolated dummy living-room light and clearly labels every result simulated. An ESP32 Arduino sketch implements the authenticated JSON payload contract, with a website field note, raw download and dedicated Arduino/C++ syntax highlighting. Real hardware and firmware compilation/upload are not qualified.

016 / DEVELOPMENT

Kanban Planning & Execution

Adds a local authenticated browser board, PRD-derived component tasks, dependencies, sequential fresh writers/reviewers, persistent pause/resume/cancel, linked repairs and per-task limits. Reuses V11 generation and V12 qualification/publication; Ask/YOLO plan policy never grants code-execution permission. Actual board snapshots replace chat in recording layouts. The live Gemma counter reached its separate execution gate with 11 retained cases; the user deferred execution. Offline regressions and recorder layout checks are separate from live runtime/video tests.

017 / DEVELOPMENT

Request Thinking

17.0.0-alpha.1 on v17. V16 development is preserved at 6df58cd / v16-before-v17, without claiming qualification of its deferred generated-project execution. Natural text requests route through fresh tool-less router, grouped specialist and reviewer scenarios. Host validation precedes one named-scenario execution; three planning rounds are allowed, with no automatic action retry or approval. The original user turn and protected receipts stay intact. See docs/V17_THINKING_DESIGN.md for scope and qualification.