Interlatch 0.29.7

• Fixed: the dashboard could hang on a chat with a long tool output: a ChatGPT chat whose Python run printed a
  long text without spaces (a base64 image, say) took hours to save, and the dashboard answered nothing meanwhile. It
  now takes a fraction of a second. Linking chats to projects is faster too, and the browser extension gives up on a
  dashboard that doesn't answer within a minute and tries again later.

Interlatch 0.29.6

• Which project a web chat is about: a claude.ai or ChatGPT chat's session page suggests the coding project it most
  likely belongs to (by rules, screening or its analysis), with Confirm or Change. A project's page lists the
  chats you confirmed, with their knowledge (Which project a chat is about).

Interlatch 0.29.5

• Analysis usage chip removed: the status bar's usage chip and its panel from 0.29.3 are gone, with the pause at a
  plan limit (analysis.plan_limit_pct, now ignored). Sessions per run and the budget per call stay settable in
  config.toml.

Interlatch 0.29.4

• claude.ai and ChatGPT chats, saved as you use the sites: a browser extension for Chrome, Edge and Brave sends
  your chats to the dashboard while a claude.ai or chatgpt.com tab is open, so new chats need no new export. Chats in
  ChatGPT projects keep their project's name. Settings › Browser extension walks you through installing it
  (Saving chats as you use the sites).

Interlatch 0.29.3

• Analysis usage on every page: the status bar shows your Claude plan's session (5hr) and weekly (7 day) usage, as
  Claude Code names them, and what analysis spent today. Click it to see what's left and when each resets, this month's
  and all-time spend, and to set the analysis limits: sessions per run, the budget per call, and a new cap that pauses
  automatic analysis at a percent of your plan limit (Configuration).

Interlatch 0.29.2

• A project's page on a team hub: the team's knowledge leads. Each knowledge base entry and lesson names whose
  sessions taught it, lessons two people found separately sit side by side, Since your last visit lists new and
  replaced lessons, Start here greets someone new to the project, People shows who has worked on what (never
  a count per person), and Who's working on it draws each person's sessions over eight weeks. Tokens and cost
  move to an admin-only Usage tab, and the Systems map is no longer offered where it would be empty or refused
  (On a team hub).
• A project's glossary and mindmap on a team hub: a project's page there has a Glossary & map tab: its terms
  as a list or a mindmap. Teammates limited to some projects now see it too, with the terms their projects use and
  what their projects say of them, never what another project wrote
  (On a team hub).

Interlatch 0.29.1

• The interview, your job goal's final boss: three questions a day, written from the job description and from
  your own past lessons, graded strong, fair or weak with what a strong answer covers and a better one from your own
  work. It's practice until every must-have tower is lit; then two strong answers and none weak beat it and crown
  the castle (The interview).
• A job goal brings its own monsters: practice battles written for each of its requirements, more where your gap
  is bigger, roam their zones marked ♜ and count toward each module's gate like your own lessons, so even a skill with
  no past lessons has a way in. The world map flags each requirement, the field shows the next tower to work on, and
  your hero now leads the party in battle (Job monsters).

Interlatch 0.29.0

• You are the hero in Innerlatch: the Party now starts with a character you make (a name and a pixel look) on a
  career path you choose: a roadmap track, or the Generalist path of the modules most tracks share. Your hero levels
  up only from the lessons you answer right in study battles (past answers count too), and shows your readiness in each
  of your path's modules. Your coding agents become your companions, their levels unchanged
  (You, the hero).
• Gate bosses in Innerlatch: five lessons understood in a module open its gate, a stone arch on the field and a
  link on your hero's card. Rank 1 asks for an explanation in your own words; ranks 2 to 4 for your own pull requests,
  commits or documents and what they show. The analysis model judges it against the module's check: a pass raises your
  rank there and your hero's XP, a "not yet" says what's missing and the gate opens again tomorrow. Your hero now leads
  the party on the field (Gates).
• A job goal in Innerlatch: paste a real job description and your analysis model maps it to the roadmap modules
  and ranks it asks for, each with the line it came from; what the roadmap doesn't cover is listed apart. The job is a
  castle whose towers light only with the ranks you show at gates, with the track that fits it best and the gates to
  take next; its modules lead the field (Job goal).

Interlatch 0.28.8

• A sign-in page that looks like Interlatch: opening a hub's sign-in or invite link now shows the dashboard's own
  card, with the person you'll sign in as, a full-width Sign in as … button, and the light/dark and language
  buttons, in place of a bare unstyled page. The page still asks before it signs anyone in.

Interlatch 0.28.7

• Feedback: report a problem or suggest an idea from wherever you use Interlatch: interlatch feedback (or
  interlatch bug), Settings › Feedback and the Feedback link in the dashboard's status bar, or Interlatch:
  Send Feedback in VS Code (extension 0.4.0). Each opens a new GitHub issue, or a discussion in Ideas, with your
  install's details filled in (versions, system, how it was installed), never your paths, addresses or sessions.
  Nothing is sent until you post it there (Command line).
• interlatch status checks every agent: it has a line for each coding agent found on this computer (Claude Code,
  Codex, Copilot, Bob, Antigravity, OpenCode, Cursor and the other MCP clients) saying whether Interlatch's MCP server
  is in it, and flags one whose command is gone or runs another install, such as an old chronicle or a checkout's
  .venv; interlatch connect <name> points it back (Troubleshooting).
• New sessions get whole notes, never a cut-off one: the knowledge digest a new session receives
  (interlatch install --inject-context) now fits its length limit by leaving out the least useful notes and the
  oldest sessions whole, and its last line says how many it left out so the agent knows to search for them. It is also
  checked for secrets once more on its way out (Configuration).
• Agents can pick up where the last session left off: the new resume MCP tool tells an agent starting in a project
  what the last session set out to do, how it went and what it left open, what waits on you, and what other agents did
  and learned since its own previous session there, all from the archive and within a length limit
  (MCP server).
• Lessons say when their code has changed: a lesson now records the files it was learned from (those the session
  read or changed), and when one of them changes, the SessionStart digest and the MCP search mark it may be out of
  date and name the file, so an agent checks it before relying on it
  (When a lesson may be out of date).