Agent-Driven Daily Workflow

​

What you will build

1. Collect pull requests, issues, notifications, and relevant Slack activity.
2. Produce a prioritized report with links and a recommended first task.
3. Help you complete that task or start a separate agent to work on another task.
4. Continue with the next task when you are ready.

​

Prerequisites

• Install and start Agent Canvas.
• Complete first-time setup, including an OpenHands agent profile, a connected backend, and an LLM.
• A GitHub account with access to the repositories you want to review.
• A Slack workspace and permission to create or install a Slack app.

​

Step 1: Connect GitHub

​

Create a GitHub token

1. Open GitHub Developer Settings.
2. Select Fine-grained tokens and choose Generate new token.
3. Give the token a name, select Only select repositories when possible, and set an expiration date.
4. Grant the minimum permissions for the work you want the agent to do:

5. Generate the token and copy it. GitHub shows it only once.

​

Add the GitHub MCP server

1. In Agent Canvas, confirm the correct backend in the backend switcher.
2. Open Customize in the left navigation.
3. Open MCP Servers.
4. Select GitHub from the MCP library.
5. Paste the token into the token field.
6. Leave the option to create a secret enabled, then save the server.
7. Wait for the server card to report a healthy connection.

​

Step 2: Connect Slack

​

Create and install a Slack app

1. Open the Slack API dashboard and select Create New App → From scratch.
2. Choose the workspace where the app will read messages.
3. In OAuth & Permissions, add these bot scopes:

4. Select Install to Workspace, approve the permissions, and copy the Bot User OAuth Token.
5. Invite the bot to each channel it should monitor. The bot cannot read channels it has not joined.
6. Find your workspace ID from your Slack workspace URL or Slack’s workspace-ID guide.

​

Add the Slack MCP server

1. In Agent Canvas, open Customize → MCP Servers.
2. Select Slack from the MCP library.
3. Paste the bot token and enter the workspace ID.
4. Keep secret creation enabled and save the server.
5. Wait for a healthy connection, then verify that the bot can access the channels you want to search.

​

Step 3: Start the daily workflow conversation

Do my daily workflow using the connected GitHub and Slack MCP servers.

Gather:
- pull requests that need my attention or review
- assigned issues
- GitHub notifications and failing CI
- Slack mentions, threads, and messages that need a response

Group the results by urgency. For every item, include its title, why it matters,
and a direct link. End with the single highest-priority task for me to start.
Do not make changes or send messages without asking me first.

Also check my assigned Linear issues and current cycle.

​

Step 4: Read the prioritized report

Organize the results into:
1. Immediate action
2. PRs waiting for my response
3. PRs requesting my review
4. Assigned issues
5. Slack highlights
6. GitHub notifications

Sort each section by urgency. Include direct links and finish by recommending one first task.

## Immediate action
- Fix failing CI on PR #123 — blocking the release — <link>

## PRs waiting for my response
- Address requested changes on PR #456 — <link>

## PRs requesting my review
- Review PR #789 — changes authentication behavior — <link>

## Assigned issues
- Document the new API behavior — <link>

## Slack highlights
- Reply to the deployment question in #engineering — <link>

## GitHub notifications
- Workflow failure on repository-name — <link>

## First task
Fix the failing CI on PR #123.

​

Step 5: Work through one task at a time

1. Ask for links if the report does not include them: Give me the links for that task.
2. Tell the agent whether you want investigation, implementation, or only a summary.
3. Set the safety boundary before it changes anything. For example:

Inspect the failing CI on PR #123, explain the root cause, and propose a fix.
Do not edit files, push changes, or comment on GitHub until I approve the plan.

4. After reviewing the result, ask it to implement the approved change, run the relevant checks, and report what changed.
5. When the task is complete, ask:

I finished that task. Re-check the remaining work and give me the next highest-priority item.

​

Step 6: Dispatch parallel work

Start a separate agent to inspect the failing CI and unaddressed review comments
on my other open pull requests. It may modify files in its own workspace and
run tests, but it must not push, merge, or post comments. Return a summary and
proposed changes when finished.

• Which repositories, pull requests, or issues it may access
• Whether it may edit files
• Which tests it should run
• Whether it may push branches or post comments
• What it should return when finished

​

Troubleshooting

• The agent cannot find GitHub work: confirm the GitHub MCP server is healthy, the token includes the required repositories, and the token has not expired.
• Slack results are empty: confirm the bot is installed in the workspace and invited to each channel you want to search.
• The agent reports no tools: start a new conversation after adding or changing an MCP server; MCP configuration is loaded when a conversation starts.
• The report is too broad: name the repositories, Slack channels, date range, or task categories to include.
• The agent tries to act too early: state that it must ask for approval before editing files, pushing, or posting messages.

​

Reference

• Daily workflow video — optional video walkthrough
• Agent Canvas overview
• Agent Canvas first-time setup
• MCP server settings
• Agent Canvas configuration