PushContext — Your team's living memory
Not a chatbot. Not a wiki. Not another search box.
PushContext reads the conversations where a team decides things — Slack, Jira, GitHub, Notion and Asana — notices when a thread settles something, and keeps it as a versioned page: the current position, the reasoning, the history, and who decided it. Anyone can ask what was decided, why, and by whom, in Slack or from a coding agent. Nobody writes anything down. Built by Lupus Creed Private Limited.
What it does
- Pages: when a thread settles something, memory writes a page (PC-n): the current position, why, what follows, a history that only grows, and links to every source thread. A later thread that changes the position writes a new version of the same page.
- Answers: ask /pc ask, mention @PushContext, DM it, or ask a plain question in a thread. It answers from the pages the asker can see, names the page, who decided it and when, and links the source. Median answer time in the last lab week: 4 seconds. When it does not know, it says so.
- The heads-up: a thread that starts to contradict a settled page gets one sentence in the thread, citing the page. Once per thread. Never on a first message.
- The map: topics as bubbles, pages as discs in the colour of the tool they were decided in, and around each page the threads that started, backed, moved, questioned or reopened it.
- The nightly pass: reviews the day's versions, merges duplicates, marks dormant pages, precomputes answers, and sends a short weekly note of what was decided.
Sources
- Slack: channels it is invited to; answers there.
- Jira: issues and their comments; read, never written to.
- GitHub: pull requests, reviews, issues and comments; read, never written to.
- Notion: page discussions; can answer there behind a switch that is off by default.
- Asana: tasks and their comments; read, never written to.
- Coding agents: an MCP server with two read-only tools, search_pages and get_page, keyed to a person and seeing exactly what they see.
Who it helps
- Engineering and platform teams — cutover dates, rollout rules, incident lessons, the reasoning behind configuration
- Product and design — deferrals with their reasons, scope calls, mockup reviews decided in Notion
- Marketing, operations and support — campaign briefs, playbooks, refund and retention rules carried in Asana and Jira
- Coding agents — precedent before a change, over MCP
Trust
- A person sees a page only when they share a channel with the page's sources, or the page is org-public
- A private channel never merges into a page from anywhere else; a private decision is never answered in public
- Every delivery from every source is signature-verified; tokens encrypted at rest with AES-256-GCM; TLS in transit; row-level security on every table
- Jira, GitHub and Asana are read, never written to; the MCP server is read-only
- Message text is never used to train models and is deleted when a workspace disconnects
NVIDIA Inception Program Member
PushContext is a member of the NVIDIA Inception program for AI-powered enterprise solutions.