The HubBound Context Bundle ships Memories, Projects and Ink as one add-on: what your team and its agents learn is captured, shared where it belongs, and answered back by Ink with its sources.
The HubBound Context Bundle is the per-seat add-on that gives a team one shared memory for its AI work. It includes three parts that ship together: Memories, Projects and Ink.
Decisions, conventions, gotchas and lessons, captured by your team and by the agents they work with, typed, scoped and kept with every revision.
Shared workspaces owned by a team or the organization. The memories and the Markdown notes a piece of work relies on live in one place, with access you control.
The AI agent that answers questions from all of it and shows the sources it used, only from what the person asking is allowed to read.
Memories, Projects and Ink are one add-on, not three products to buy and wire up. Agents and the CLI capture Memories, Projects hold the memories and notes they belong to, and Ink reads across both.
Coding agents save and search memories through the hubbound-memories MCP server, and the HubBound CLI captures memories for a project, so what your team learns is written down as the work happens.
An agent connects to the server like any other MCP server, then uses six tools to read and write the Context Bundle.
Memories are also captured by the CLI for a project, and each memory records how it got there, so you can always tell where a lesson came from.
Capture source, as HubBound records it
Tool names are the hubbound-memories server's own. Capture sources are the labels HubBound shows on every memory.
HubBound Memories keeps the decisions, conventions and lessons your team and its agents capture, so the reasoning behind your work outlives the session that produced it.
Nine types of memory
See what was added, what was removed and who changed it.
Superseded, refined or built on: the relationship map shows it.
A memory reaches a team or the organization once it has the approvals it needs.
Illustrative sample: the memory, its people and dates are for illustration only. Labels mirror HubBound's Memories page.
A HubBound Project is a shared workspace, owned by a team or by the organization, where people and their agents keep the notes and memories that a piece of work relies on.
A team project belongs to a team, and an organization project belongs to the organization's admins. Ownership decides who can change a project's access.
Give access to people, to teams or to the whole organization, as Owner, Editor or Viewer. People outside your team are invited by email.
Editors and owners write notes in Markdown. Each project also lists its memories, the ones agents and the CLI captured for it, beside the notes.
Every change to a project, its notes and its access appears in its activity log. An archived project can be restored for 30 days.
Illustrative sample: project names, people, notes and dates are for illustration only. Labels mirror HubBound's Projects page.
Ink is the AI agent of the HubBound Context Bundle: ask it anything about what your team has decided and learned, and it answers from your memories, with the sources it used.
Hi, I'm Ink
I read the memories your team and its agents have captured, from decisions to gotchas across your projects, and answer with the sources I used.
Try asking
A private memory never reaches anyone else's answer.
Type, scope, author and last update, so you can check the original.
Requests that try to change how Ink works are not answered.
Good or bad, and what went wrong when it misses.
Illustrative sample: the question, the answer, the sources and the people are for illustration only. Labels mirror HubBound's Ink chat.
Your organization controls it: an admin can turn Memories on or off, private memories stay private, and a memory needs approvals before it reaches a team or the whole organization.
An organization admin can turn Memories on or off in the organization settings. Turning Memories off also turns Ink off.
Organization admins see only the metadata of a private memory. Its content is never shown to them.
A person promotes a memory to a team or to the organization, and HubBound proposes a copy while the original stays active. It reaches that scope once it has the number of approvals required.
An admin can delete a memory for everyone, choosing a reason such as a secret leak or incorrect content, and the reason is recorded.
Illustrative sample: the proposal, the people and the counts are for illustration only. Labels mirror HubBound's Memories proposals.
These are the short answers about Memories, Projects and Ink: what ships together, who can see what, how agents write to it and how it is priced.
The HubBound Context Bundle is a per-seat add-on that includes Memories, Projects and Ink together. Memories keep the decisions, conventions and lessons your team and its agents capture, Projects are the shared workspaces they belong to, and Ink answers questions from all of it with the sources it used.
Link to this answerNo. Memories, Projects and Ink ship together as the Context Bundle, one add-on per seat. They are designed as one product: agents and the CLI capture Memories, Projects hold the memories and notes, and Ink reads across both.
Link to this answerThe Context Bundle is priced per seat as an add-on, and Ink questions are billed on demand once a team passes a threshold of questions. The Pricing page lists the current prices.
Link to this answerA HubBound memory is a decision, convention, architecture note, bugfix, gotcha, procedure, preference, session summary or note, with what happened, why, where and what was learned. It keeps every revision and can link to other memories.
Link to this answerA memory is Private, Team, Organization or Project, and only people who can access that scope can read it. Organization admins see only the metadata of private memories, never their content, and Ink answers only from memories the person asking can access.
Link to this answerCoding agents save and search memories through the hubbound-memories MCP server, and the HubBound CLI captures memories for a project. Each memory records its capture source, such as Agent or CLI.
Link to this answerInk answers from the memories your team and its agents have captured that the person asking can access, and it lists the sources it used. It declines requests that try to change how it works and questions that are out of scope.
Link to this answerYes. An organization admin can turn Memories on or off in the organization settings, and turning Memories off also turns Ink off.
Link to this answerA person promotes a memory and HubBound proposes a copy to a team or to the organization while the original stays active. The proposal needs a number of approvals before the memory takes that scope.
Link to this answerEach piece of HubBound builds on the others. Pick where you want to go next.
See Memories, Projects and Ink working together: what gets captured, where it lives and how Ink answers with its sources.
