Set up Elisha and assign it something

1. Create an account

Sign up at /signup. You'll land in the onboarding wizard, which walks through each integration in order and shows a live badge of what's connected.

2. Install the GitHub App

GitHub is the only integration Elisha can't work without — it's where the pull requests go. The App asks for:

• Contents (read & write) — to clone the repo and push a branch.
• Pull requests (read & write) — to open the pull request and comment on it.
• Metadata (read) — required by GitHub for any App.

After the install you pick the repositories Elisha may touch. Access is scoped to that selection; it can't clone anything you didn't choose, and you can change the list later without reinstalling.

3. Connect Notion

Notion's own consent screen decides what Elisha can see — you choose the pages and databases to share, and nothing outside that selection is visible. Then point Elisha at the board you use for engineering work:

• A status property (select or status type) — Elisha writes back to this.
• Optionally an owner property, so it can pick up only the cards assigned to it.

The board picker in onboarding inspects your database and tells you which properties it found, so you can confirm the mapping before anything is written.

4. Connect Slack

Invite the Elisha bot to the channels it should watch — typically the one where bugs get reported. It reads the channels it has been invited to and nowhere else, and it replies in the thread where the work was assigned.

5. Optional: Vercel, Google Workspace, Figma, PostHog

These add context rather than intake. Vercel lets a failed deployment become a task; Figma lets a UI task reference the frame it should match; PostHog puts numbers behind a bug report. All of them can be added later from Settings — see Integrations for what each one is scoped to.

6. Assign your first task

Any of these work, and they all end up in the same queue:

• Drop a card on the connected Notion board.
• Message the bot in a connected Slack channel.
• Create a task from the dashboard.

Write it the way you'd write it for a teammate. A good first task is small, real, and verifiable — a copy fix, an empty state, a bug someone can reproduce.

7. Read the pull request

The pull request Elisha opens carries the evidence for its own change:

• What it understood the task to be, and what it decided at the gate.
• The files it touched and why.
• Which checks ran and what they returned.
• Before/after screenshots when the change is visual.
• Any risk flags that matched, as a heads-up rather than a block.

Review it like any other pull request. If it's wrong, close it — that costs you a click.

Troubleshooting

Elisha says a repository isn't available

The GitHub App's repository selection doesn't include it. Update the selection on GitHub, then reload Settings.

Notion status isn't updating

The board's status property was renamed or its options changed. Re-run the board picker in Settings — it re-inspects the database and shows what it found.

Slack messages aren't picked up

The bot has to be invited to the channel. If you've recently added a scope, reconnect Slack so the stored token receives the updated grant.