Before you start
You need a project. A project appears under Memory after your coding agent makes its first request in a folder, using a key from API keys (see your client’s page under Clients). Until you have one, the Slack page says so and Connect a channel stays off.Set it up
Open Slack in the dashboard and follow Setup:- Add the nemonist app to your Slack workspace. Once per Slack workspace. Some workspaces let only an admin approve apps; send them the link Slack shows.
- Link your Slack account. Sign in with Slack, so nemonist knows your messages are yours.
- Connect a channel to a project. In Project channels, choose Connect a channel, then pick the channel and the project. If a channel is missing from the list, run
/invite @nemonistin it and reload the page. You can also run/nemonist connectin the channel itself. - Pick a channel for alerts (optional). Without one, alerts go by email.
Using the channel
- Post a question or an instruction. nemonist marks your message with :eyes: when it is queued, and with :white_check_mark: once the reply is in the thread.
- A project answers on its next request. Each message you post, in the channel or in a thread, gets a note only you see: it says the message is queued, when the project was last active, and that the reply comes within minutes if a coding session is running, otherwise when the next one starts (or within 10 minutes, if the project answers Slack itself).
- When a session picks up several messages at once, each thread gets the answer to its own message.
- If the coding session picks your message up but nemonist cannot answer it (for example, the Free plan’s requests for the day are used), the thread says why, and the message stays queued for the next request that can answer it.
- Only people who may write the project reach it. A teammate whose Slack account is not linked, or who has no access, sees a note saying why their message was not sent.
- If you mention
@nemonistin a channel connected to no project, only you see a note saying so, with the link to connect it. - Slack lets two apps have the same name, so
/invite @nemonistcan list more than one nemonist. Only one of them is ours, and a message or mention sent to the other one reaches nobody. To be sure the right one is in a channel, run/nemonist connectthere instead of inviting by name: it adds our app itself./nemonist statussays when our app is not in the channel, even before the channel is connected. - If someone removes nemonist from a connected channel (for example with
/remove @nemonist), Slack stops sending that channel’s messages to nemonist, so messages posted there no longer reach the project. The project’s owner gets a direct message from nemonist saying so, the channel shows App removed in Project channels, and/nemonist statusthere says the app is not in it. Run/invite @nemonistin the channel to bring it back; the channel stays connected, and nemonist says in it that messages reach the project again. Messages posted while it was away are not delivered, so post them again.
Commands
/nemonist status: which project this channel talks to, and whether the nemonist app is still in it./nemonist connectand/nemonist disconnect: connect this channel to one of your projects, or undo it./nemonist new-channel <project>: make a private channel for a project.