Disciple 1.1.3

1.1.3 — 2026-07-25

An AI reliability release. Disciple now acts on ordinary phrasing instead
of waiting to be commanded again, and the common organizer requests run
entirely locally with no provider request at all.

Understands ongoing intent

• "remember that I like chocolate" saves visible Assistant Context
  immediately and reports only after the write commits.
• When the assistant asks "Should I remember that for future
  conversations?", answering "yes" executes the saved intent locally —
  no second provider request.
• "I'm starting a project called NEO about minecraft movies" creates the
  project with its description; you no longer have to repeat "create the
  project".
• "schedule 40 hours of work next week" asks one question (weekdays or
  the weekend) and then commits an exact, bounded schedule. "Do it",
  "I need it in my calendar", "Just choose for me, I trust you" all
  continue the same request rather than starting over.
• Batch schedules are written in one transaction, total exactly the hours
  requested, never duplicate on repeat, and undo as a single grouped step.
• Short pending answers ("yes", "AM", "the first one", a time) resume the
  original request with every resolved argument preserved.

Fixed

• A saved memory beyond the always-included budget became permanently
  unreachable: it was excluded from always-included context and from
  relevant retrieval, so Disciple would confirm "Remembered" and later
  behave as though it never happened. Overflow memories are now found by
  relevance.
• An action request with no route (an explicit /do override) exposed
  only three read actions, so a write could never be selected.
• "Schedule 8 hours for X next Monday" was parsed as an appointment with a
  missing start time and would have created a one hour event titled
  "8 hours for X". A named day with an hour count is now a work block; more
  hours than fit in a day asks whether to spread them across the week.
• Event titles no longer keep a leading article or a trailing day
  qualifier ("a dentist appointment next" → "dentist appointment").
• A four-action allowlist silently dropped the no_action escape hatch.
• Removed an unverified hardcoded provider retirement date that would have
  silently hidden a model the provider still lists.
• Restored visible chat streaming, which had been buffered to nothing.

Assistant quality and safety

• Prompts are split into mode-specific sections (conversation, organizer
  action, clarification) with fixed safety cores that editable settings
  cannot remove.
• Capability grounding is generated from the actions actually registered,
  so the assistant cannot invent or deny a Disciple capability, and it
  distinguishes Disciple's internal calendar from external services.
• A normal-chat reply that claims an organizer change, or falsely denies a
  registered capability, is replaced before it is shown or stored.
• Visible success messages are deterministic application text produced
  only after SQLite commits.

Efficiency

• Common organizer requests and every yes/no continuation use zero
  provider requests; batch scheduling never calls per event.
• Routed action requests expose only the relevant actions; malformed
  output gets at most one repair attempt; provider failures never retry a
  paid request or leave a partial write.

Install

• Flatpak (any distro): flatpak install --user disciple-1.1.3.flatpak
• Fedora: sudo dnf install disciple-1.1.3-1.fc44.noarch.rpm
• Debian/Ubuntu: sudo apt install ./disciple_1.1.3-1_all.deb
• Python wheel: pip install --no-deps disciple-1.1.3-py3-none-any.whl (needs system PyGObject/GTK4/Libadwaita)

Verify downloads against SHA256SUMS.txt. AI stays optional — the organizer works fully offline, and your API key is stored only in the Linux keyring, never in a file, database, or backup.