Context Pack is portable memory for agent workflows. Turn prompts, plans, decisions, project context, and hard-won know-how into reusable packs you can fetch across agents and threads. Keep them private, share them with your team, or publish them for the community, so others can reuse proven context instead of starting from scratch. Works across MCP and CLI, with support for cloud agents, local setups, Slack, and Discord.
We built Context Pack because valuable context keeps getting trapped inside one chat, one tool, or one moment.
That leads to a lot of manual work:
moving context between agents,
re-explaining the same project in new threads,
pasting old prompts again,
or rewriting good discussions into docs just to share them.
Context Pack makes that reusable.
A pack is a title + content set.
You can use it for prompts, plans, decisions, project context, or hard-won know-how. You can fetch titles first, load full content only when needed, and use your context window more efficiently.
One of the most exciting parts is that packs are not limited to private use.
You can keep them private, share them with your team, or publish them for the community.
That means Context Pack is not just about saving your own memory. It is also a way to reuse proven context from others. AI power users can publish the memory behind their workflows, prompts, research habits, and playbooks, and others can build on that instead of starting from scratch.
To get started, you can simply tell your agent:
`Set up Epismo access and load the Skills from https://github.com/epismoai/skills`
The Skills are designed for both MCP and CLI, so you can use Context Pack with cloud-based agents like ChatGPT or Claude, local setups like Claude Code or Codex, and even Epismo agent on Slack or Discord.
For a first example of how to share a Context Pack:
`/context-pack @hirokiyn/context-pack`
Would love to hear how you’d use it.
how do you handle context conflicts when multiple agents write to the same memory pack?
The part about reusing context from other people's workflows is interesting. If I load someone's published context pack, does it just give me their prompts or does it actually carry over the decisions and reasoning behind why they built it that way?
About Epismo Context Pack on Product Hunt
“Portable memory for agent workflows”
Epismo Context Pack launched on Product Hunt on April 6th, 2026 and earned 105 upvotes and 11 comments, placing #12 on the daily leaderboard. Context Pack is portable memory for agent workflows. Turn prompts, plans, decisions, project context, and hard-won know-how into reusable packs you can fetch across agents and threads. Keep them private, share them with your team, or publish them for the community, so others can reuse proven context instead of starting from scratch. Works across MCP and CLI, with support for cloud agents, local setups, Slack, and Discord.
Epismo Context Pack was featured in Productivity (649.7k followers), Developer Tools (511k followers) and Artificial Intelligence (466.1k followers) on Product Hunt. Together, these topics include over 278.6k products, making this a competitive space to launch in.
Who hunted Epismo Context Pack?
Epismo Context Pack was hunted by Hiroki. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Epismo Context Pack stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Hiroki