Your Slack history becomes team memory

lore turns Slack conversation history into durable team memory, so the group can recover decisions, find the relevant message, understand what is blocked, and continue work from the context that already exists. It can then use that grounded context for one bounded mission and report the result back in Slack.

Concrete capabilities

• Recover the message behind a past decision.
• Open public web pages in a real browser, read them, take screenshots, and return sourced work.
• Create research briefs, documents, checklists, and follow-ups from what the chat decided.
• Notice open asks and blockers, then prepare the next step.

How it works

1. The team talks in Slack as usual.
2. lore uses the permitted conversation context and connected tools.
3. lore performs one bounded mission and records the evidence.
4. The result comes back to the conversation. External sends, posts, bookings, and purchases require approval.

Limits and approval

lore handles one mission at a time. It cannot use private sources or tools that a team has not connected and permitted. Availability and integrations can change. It prepares internal work, but actions that represent the team or spend money use approval gates.

Questions

What is lore?

lore is an AI teammate that lives in a team group chat. It uses the conversation as working context, remembers decisions, helps with open work, and reports results back in the same thread. The team can keep talking where it already works instead of rebuilding the request in another dashboard.

What can lore do from Slack?

lore can turn a message into bounded work such as research, browser tasks, documents, checklists, and follow-ups. When the required tools are connected and permitted, it performs that work and reports the result in the conversation. The team does not have to copy the original decision and its context into another app.

What requires approval?

External actions such as sending, posting, booking, or buying use approval gates. lore can prepare internal work and show what it found first, but the team stays in control of actions that represent it or spend money. Permission is scoped to the specific action rather than assumed from access to the conversation.

What are the limits?

lore handles one mission at a time. Integrations and availability can change, and it does not claim access to a tool or source unless that team has connected and permitted it. A browser or source can also be unavailable, so lore reports the evidence it used and says when a task is blocked rather than inventing a result.