Can Memtro change anything in Slack or GitHub?

Only when you ask, and only where an administrator has granted it: Slack can post a message to a channel or thread, as the app or as you, when you ask for it, send a direct message to one person, opening the conversation if need be, add an emoji reaction to a message, edit a message it sent, replacing the whole wording, delete a message it sent, which cannot be undone; GitHub can open an issue in a repository, comment on an issue or pull request, change an issue's title, labels, assignees or state (close or reopen), commit files to a branch, creating the branch if it does not exist, open a pull request from a branch, review a pull request: approve, request changes, or comment on lines, change a pull request's title, body, target branch, draft state, or close it, merge a pull request, optionally deleting the branch. Every other tool reads, searches or lists.

Do I need both to be useful?

No, but the questions on this page need both. Connect one and it answers what that system knows; connect the second and the agent cross-references them by default, because it anchors records from both into the same memory.

How does Memtro know a record in Slack is the same customer as one in GitHub?

By resolving them to one entity in your organisation's graph — matched on email, domain, name and the identifiers each system exposes. That is what makes a question about a company reach both systems rather than searching twice.

How long does connecting take?

Minutes each. User token, bot token or OAuth for Slack, Token or OAuth for GitHub, pasted on the Connections page. Each connection is personal or shared, and a shared one is granted to teams tool by tool.

Find the decision behind the code

Connect Slack and GitHub to one company memory, and a single question reads both.

Why the retry policy is three attempts was decided in a thread in March. The code says what it does and never says why, and the person who knows has left or forgotten.

Connect both, free for 7 days Open Connections

Questions that need both

Each of these is unanswerable inside either product on its own. Agent mode reads both, resolves the customer to one entity, and ends with a line per system it consulted.

›Who owns the billing migration, and what did we decide about retries?
›Find the discussion behind this change to the payment handler
›What was decided about the schema change, and did it ship?

What each side brings

Slack

Search messages, read channel history and threads, post when you ask, and answer when mentioned.

Hourly sync: workspace members and your channels join the graph, with new channel messages as events
Search messages
List channels, read channel history and a thread
Post a message to a channel or thread when you ask (the one thing it can change)

All of Slack →

GitHub

Issues, pull requests, code and commits, searchable by anyone who can ask a question.

Search issues and pull requests across your repositories
Read an issue or PR with its comments
Search code and read files at a ref
List repositories and recent commits

All of GitHub →

Who this is for

Other seams worth closing

Ask one question across both

Seven days free. One price per organisation, nothing metered, and model usage stays on your own provider keys.

Start for free Work out the saving