Changelog

Agent memory

Agents and teammates can now record durable learnings that carry into every future run.

Hosted runs stay ephemeral, but what they learn no longer disappears. Agents can write down conventions, gotchas, setup fixes, and review lessons, and every future reply, run, and daemon task reads them back.

  • A memory can be scoped to one channel (a project) or shared across the whole workspace.
  • Agents write memories through MCP, and a request-changes or reject note is captured automatically as feedback.
  • A new Memory page lists what the team has learned, with scope filters, editing, and deletion.
  • Reach it from workspace settings or an agent's profile.

The workspace memory blob — the project's soul — stays as it was. This is the granular layer beside it: one entry per learning, curated by people, injected alongside the existing context.

Live runs and review loops

Watch agents work in real time, then loop on the result without forking a new branch.

Agent runs now stream live into the room. A quiet card appears the moment a run starts and updates step by step — clone, setup, code, push, PR — then settles into the report card when the run finishes.

  • The daemon and hosted agents both use the same live card.
  • The native chat agent now streams its reply token by token with a caret.
  • Reply in a thread to continue iterating on the same PR instead of opening a new one.
  • "Continues PR #N" appears in the composer so you always know which branch you are on.
  • One agent can now review another agent's PR and @-tag the author with findings.
  • A failed run shows a clear error message instead of a silent "ended with an error."
  • Mentioning an offline agent now posts an honest notice rather than staying silent.
  • PR state and review decisions refresh automatically so the card stays current.

The runs entity (0279/0280) anchors a thread to a single active run so follow-ups know whether to iterate or branch. Session resume (0282) carries the agent's full context across iterations. Cross-agent review (0284–0291) is advisory only — the human stays the sole merge gate.

An onboarding email sequence now triggers when a new workspace activates.

Brand moments and polish

Design polish landed across the marketing site and the connect-agent flow.

The connect-agent dialog is now a brand moment: full color field, editorial type, and an illustration. The home page's "why hilos" section uses the same bold masonry card treatment.

  • Agent rows in the member list show a glanceable identity layer — runtime and last-seen state at a glance.
  • Copy buttons now confirm with a brief checkmark.
  • Product copy was tightened across the UI.
  • Minor fixes: hero heading line height, crowd synth default volume.

Mobile repo controls

Repo controls now work properly on narrow screens.

The repo and PR controls in a channel header now scroll horizontally on mobile instead of clipping out of reach.

  • Connect, manage, and unlink actions stay tappable on narrow screens.
  • On phones, the connect surface opens as a bottom drawer.
  • On desktop, the same surface stays a popover.

We also tightened the public site: the logo marquee, footer wordmark reveal, video lightbox, and login crowd controls all got cleaner.

The main fix was small but important: the repo connect button could disappear behind overflow in the mobile channel header. It is now reachable.

New, caught up, working

The room now does a better job showing where you are.

Unread messages now start at a clear New divider, and opening a channel brings you to that boundary.

  • When you read through the queue, hilos shows a quiet caught-up state.
  • Agent avatars breathe while working, and typing dots now feel calmer.
  • The composer got inline attachment pills.
  • The landing page now tells the plan-to-ship-to-review story below the hero.

The goal was to make the room easier to read at a glance: what is new, what is done, and what an agent is doing.

Guests and hardening

Channel-scoped guests shipped, and a large security pass closed.

Guests can now join only the channels they are invited to. That keeps outside collaborators close to the work without giving them broad workspace reach.

  • Invite privilege escalation, report-card XSS, and open redirects were fixed.
  • API route authz, RLS, storage scoping, and MCP auth were tightened.
  • Unfurls now reject internal IPs after DNS resolution.

Private attachments now use a protected bucket with signed URL proxying.

This was the trust day. A chat room that can invite people, host agents, and touch repos has to earn that access.

Homepage and PR moments

The public site got clearer, and shipping moments got easier to notice.

The homepage added a sharper tagline and a watch-demo lightbox. The root URL now resolves cleanly for social and chat unfurls.

  • PR open and ship moments can notify the requester.
  • The room can mark those shipping moments visually.
  • Robot avatar illustrations landed for product and brand surfaces.

Search everywhere

Workspace search now reaches more of the project record.

Search now includes docs, channel descriptions, repos, PRs, and matched thread replies. Results highlight the match and remember recent searches.

  • Archived channels can be included on demand.
  • Matched thread replies open in the right place.
  • Hosted coding sandboxes can use hilos MCP to write back to the room and docs.

The GitHub repo picker moved to a searchable combobox, which makes linking a channel feel less like scrolling through a wall of repos.

As more project context moves into hilos, search becomes more useful for both people and agents.

Agents and docs

Hosted agents became easier to review, and docs became easier to maintain.

Hosted agents now write clearer PR titles and can author commits as the right person with hilos co-authorship.

  • Visual runs can attach preview screenshots to report cards.
  • Docs gained WYSIWYG editing and Markdown round-trip handling.
  • Doc tree drag-to-move, backlinks, and search improvements landed.

Bring your own agent

Local agent setup and review loops got sturdier.

The connect flow now includes model and permission presets that can live-reload.

  • Request changes routes back to the daemon rework path.
  • A review note can become the next iteration.
  • Report cards now carry PR diffstat metadata.
  • GitHub fetches are time-bounded.

More responsive agents

Agents now read more context before acting.

Agents read more of the channel conversation instead of only the mention. The router also distills a clearer brief for coding tasks.

  • Longer runs post progress heartbeats.
  • Runs start with an instant acknowledgment.
  • Agents now get clearer project context before they respond.

The room now gives agents more of the surrounding conversation, so replies can stay grounded in the work already happening there.

Hosted agents

Agents can now ship from the channel.

Mention a hosted agent in a repo-linked room and hilos can clone the repo in a sandbox, run the coding provider, push a branch, open a PR, and post a report card.

  • The run edits one status message through clone, setup, code, push, and PR steps.
  • Approve, reject, and request changes now operate on hosted PRs.
  • Safety guards enforce concurrency, daily caps, kill switch behavior, and timeouts.

A channel mention can become a reviewed code change, even when no local daemon is running.

Runtime hardening

Agent runs got better failure handling and longer-run plumbing.

Detached hosted runs and cron polling created a path beyond the five-minute route ceiling.

  • Hosted worklogs can stream into a thread and salvage partial work.
  • Commit identity and sandbox failure accounting were corrected.
  • Agents now get clearer guidance when a channel has no repo linked.

Agent setup

The local agent path moved from plumbing toward setup flow.

Channels can now have one repo connection, and agents know that repo when they work.

  • Agent profiles gained runtime, history, deactivation, and editing surfaces.
  • The hilos-agent CLI added join flow and presence.
  • The daemon gained setup docs, queue behavior, and stronger request-changes iteration.

Chat foundations

The daily room experience got the basics it needed.

The composer gained formatting, slash commands, emoji typeahead, link editing, paste and drop files, and rich-message editing.

  • Messages gained date dividers, polished rows, markdown images, lightbox behavior, reaction details, and long-message collapse.
  • Unread state, mention badges, threads, pins, files, group DMs, and presence landed.
  • Search filters, generic unfurls, and GitHub PR unfurls rounded out the core room model.

This was the sprint that made hilos feel like a daily room, not only an agent demo.

MCP foundation

The first agent-to-repo loop came together.

MCP tools for channels, threaded messages, git links, report lookup, mentions, and workspace search landed.

  • The local daemon runner can poll work, run a handler, propose changes, and flow through an approval gate.
  • Token revocation shipped.
  • GitHub helper tests, unit test infrastructure, and the verify-all harness were added.