Your full history of conversations and decisions lives in the context graph—so chat, documents, and plans can draw on everything your team already decided and discussed.
We've been working on the Hamster context graph behind the scenes, and we're excited to share it with you today.
Under the hood, Hamster models your workspace as one graph: conversations, decisions, briefs, documents, initiatives, tasks, and people, with explicit links between them. Retrieval follows those relationships—so the assistant pulls context the way work is actually connected, instead of guessing from keywords alone.
[image: The gravitational solar system canvas visualization showing workspace entities as interconnected nodes with relationship edges]
That model shows up everywhere you already work:
Hamster links document sections as distinct context, not just whole files. Different parts of the same document can map to different entities in your graph, so the system can pull the exact evidence needed for each request—including the conversations and choices that led to each section.
[image: A chat response showing Hamster answering a cross-entity question with source references from across the workspace]
Hamster can also walk neighborhoods in your graph on its own, expanding to related nodes when a question spans more than one part of the workspace.
The graph is team-member aware and time aware, so Hamster can factor in what your team is actively doing right now, what changed recently, and which context is most useful in this moment.
This gives you full traceability across the lifecycle of work: what was said and decided, how that turned into execution, how a brief was delivered, and which release that work ultimately shipped in—so you can always walk back from an outcome to the conversation and rationale behind it.
Initiative lists now show who owns each initiative. Assign a team member directly from the list or from the detail page.
[image: The initiatives list with an Assignee column showing avatar and name for each initiative]
Initiatives now support nesting. Break large efforts into sub-initiatives under a parent, with a tree view that remembers your expand/collapse state.
[image: The initiatives tree view showing parent initiatives with nested sub-initiatives and expand/collapse controls]
hamster sync now accepts a brief directly (UUID, slug, or full Studio URL) and auto-initializes when .hamster/ is missing\n instead of line breaks