HomeVideos

Performing Your Daily Workflow with AI Agents

Now Playing

Performing Your Daily Workflow with AI Agents

Transcript

277 segments

0:09

Hi there. This is Graham from Open

0:11

Hands. And like everybody else, I'm kind

0:14

of navigating this world of AI-driven

0:17

development. And I try to use

0:20

AI agents to do many of the jobs that I

0:23

do every day to, you know, accelerate

0:26

and be able to build more things that I

0:29

wouldn't have been able to do otherwise.

0:32

And you know, we're all trying to figure

0:34

out out how to best utilize AI in our

0:37

workflows, but I've learned a few things

0:40

over the process of doing it myself. So

0:42

I thought I'd start this video series to

0:44

share them.

0:45

So the first one that I'd like to share,

0:49

and you know, of course get feedback on

0:51

it. I'd love to hear what people think,

0:53

is how I've been trying to orchestrate

0:57

my daily workflow so that I mostly do my

1:00

daily workflow through prompting AI

1:02

agents,

1:03

as opposed to me managing my own daily

1:06

workflow and then asking an AI agent to

1:08

do parts of it. So it's basically an

1:10

agent-driven workflow where I pop out

1:13

and do other things occasionally.

1:16

So

1:17

in order to manage this workflow, you

1:20

need a number of tools. I'd say the very

1:22

bare minimum is you need to be able to

1:25

manage your to-do list, your

1:26

communication, and your

1:29

code or the products that you're

1:30

generating.

1:32

And to manage my to-do list, typically I

1:34

use Linear. Jira's another popular tool

1:37

for that.

1:38

But for the purpose of this demo, I'm

1:40

I'm just going to use GitHub issues as

1:42

the source of my tools essentially.

1:47

Um

1:48

and

1:49

for communication, I typically use

1:51

Slack. People use other things like

1:54

Teams or things like that, but I'll I'll

1:55

use Slack for this demo.

1:57

And then for the source of my source

2:00

code, I'm going to use GitHub, and of

2:01

course GitLab and Bitbucket are popular

2:03

alternatives for that.

2:06

So, the basic idea behind this workflow

2:08

is you first start up your agent, uh

2:10

whichever one you like, but I'll use the

2:13

OpenHands Agent Canvas uh to

2:16

run agents in a a way that allows you to

2:19

uh kind of visualize them

2:21

and uh and manage them. So,

2:23

here we go. Uh grab the agent canvas URL

2:26

and and put it in here.

2:28

And so, now now I have my uh

2:31

you know, agent control center. And

2:35

as I mentioned, you need to use several

2:37

tools in order to get this sort of

2:38

workflow to work. And so, I'll jump over

2:41

and add uh MCPs to customize

2:45

and provide external access to uh

2:48

various external tools.

2:50

So, uh first is GitHub. Uh just pop over

2:53

to GitHub, go to the settings page,

2:56

scroll down to developer settings,

3:00

and uh personal access tokens, get a

3:02

fine-grained token,

3:04

generate a token,

3:05

do like OpenHands Bot Token,

3:09

choose the resource you want to handle,

3:11

which is like OpenHands,

3:14

uh the OpenHands organization,

3:16

and then I can do uh OpenHands OpenHands

3:21

is one repo, which is our main repo, and

3:23

then software agent SDK, which is our uh

3:26

SDK repo.

3:28

And give the appropriate permissions.

3:30

So, I'd need things like content, pull

3:33

requests,

3:35

uh issues,

3:38

and workflows. And so, that's pretty

3:41

good set of things to give my uh

3:45

personal access token.

3:47

So, I generate the token.

3:50

And uh don't worry, I'll delete this

3:52

after uh the demo here.

3:59

And then um we'll also add Slack. And

4:02

so, in order to add Slack, you need a

4:03

team ID, uh which you can grab by just

4:06

going to your uh

4:08

team.

4:10

Um going to Slack uh on

4:13

your

4:15

uh

4:16

web browser.

4:17

And then you can also uh set up a Slack

4:20

bot. So, I I set up this Slack bot, new

4:23

big bot, for my own personal bot.

4:25

And you can uh connect it to your

4:27

favorite workspace,

4:28

add the channels, and then grab the bot

4:31

token.

4:33

So, I'll put that in here as well.

4:38

So, now I I have the two connections.

4:41

And this is where the fun begins. Uh up

4:42

until now was pretty vanilla if you've

4:44

used agents before.

4:46

But, the interesting thing about my

4:49

workflow is um I actually have a skill

4:52

that

4:53

basically walks through all of the tasks

4:55

that I was doing in my daily work. And

4:57

so, um before I had the skill, what I

4:59

would do is every day I would go out to

5:00

our task management software like

5:02

Linear,

5:03

um browse issues on GitHub, uh look at

5:06

my Slack communications, and try to

5:08

organize all of that stuff.

5:10

Um but, the great thing about this is

5:12

that this will now organize all the

5:13

stuff for me.

5:15

And since I have a skill installed in my

5:17

workspace, I can just tell the agent

5:21

do my daily workflow.

5:24

And so, typically this will work.

5:26

And um but, in this case I'm doing

5:29

something a little bit different than my

5:31

daily workflow cuz I'm not going to uh

5:33

use Linear because I have some private

5:35

stuff on there.

5:36

So, instead, what I will say is

5:39

make sure to use your MCP tools for

5:42

GitHub and Slack looking only at private

5:45

information.

5:48

At the end, give me a structured report

5:51

of all of the things to do today, and

5:53

then give me my first task to do.

6:03

And so, uh the nice thing about skills

6:05

and stuff like this is that you can

6:07

actually, um you know, start out with a

6:10

base and then diverge in any uh way that

6:12

you need to. So, this will uh take a

6:15

little while. Uh because it takes a

6:17

little while,

6:18

and I typically don't like waiting,

6:21

I will um

6:24

it set up an automation to run it at the

6:27

beginning of the day.

6:29

Uh

6:30

typically 6:00 a.m. every workday. So,

6:33

that when I start working in that day, I

6:35

have a list of all of the things that I

6:37

could uh possibly be doing. And um the

6:41

OpenLens Agent Canvas has a few things

6:42

that make that really uh easy and nice

6:44

to do. Like, we have an automation's

6:46

thing where you can kind of set up a

6:47

cron job like thing

6:49

uh to do that sort of uh automation, but

6:52

I'll maybe talk about that in a future

6:53

video.

6:55

So, anyway, I'll let this run for a

6:57

little while. Um it should take uh a

7:01

bit, so I might fast forward through

7:03

this part. But when it's ready, we can

7:05

circle back and uh try to take a look at

7:08

the result. So, the workflow finished.

7:10

It took a a couple minutes, but not too

7:12

bad. And uh this is what it looks like

7:15

here. So, you can see it says, "I've

7:17

gathered everything from GitHub and

7:19

Slack. Here's your structured report."

7:20

And I kind of specified the structure.

7:23

Um these are

7:25

uh you know, immediate action. Um it's

7:29

uh kind of the types of things that uh

7:32

you know, we could work on immediately.

7:34

Um PRs awaiting your attention, PRs

7:36

requesting your review, um and assigned

7:39

to issues.

7:41

Uh Slack highlights,

7:43

and uh GitHub notifications requiring

7:46

action.

7:47

So, this is good, but I personally um

7:51

get a little bit overwhelmed with all of

7:53

the stuff that I have on my plate. So,

7:55

now that we're all moving at agentic

7:57

speed, it's kind of hard to manage this

8:00

huge list of things. And so, uh

8:03

I personally find it more useful to have

8:06

the agent tell me one by one which thing

8:08

I should be working on.

8:10

Um when I'm using something like Jira or

8:12

Linear, it gives me a priority order of

8:15

all of the things that I want to work

8:17

on, so I can walk through it in priority

8:19

order. And so, this is an example of uh

8:22

that. So, it gave me my first task, and

8:24

it said um you just got CI unstuck by

8:27

removing the unused uh clock three

8:29

import. Uh the build is rerunning now.

8:31

Once it's green, um unblocks uh feature

8:34

work for the week.

8:36

Um and then uh this is the only PR open

8:39

with changes requested status. It's a

8:42

substantial 623-line PR uh that a team

8:45

mate needs to wait to move forward on.

8:47

So, um give me like I can say uh give me

8:50

links to those.

8:56

And it will give me links, and I can

8:58

click through and start working on them.

9:04

And another thing that I uh like to do

9:07

in this workflow

9:08

is um

9:11

to

9:13

start another agent working in the

9:15

background to resolve any

9:17

easy-to-resolve issues while I do the

9:19

work myself. So, another thing that I

9:21

often do, and it's actually part of my

9:23

normal workflow, is

9:26

dispatch another sub agent via the agent

9:29

canvas

9:30

to

9:32

remediate all of the failing CI or

9:35

unaddressed review comments

9:37

on

9:39

my open PRs.

9:42

And so, I can get this agent to kind of

9:46

um dispatch another agent to start

9:48

working.

9:50

And so, then I go through, I take a look

9:52

at uh these PRs, and I I start working

9:55

on them. Um I'm not going to actually

9:57

bore you with the details of me working

9:58

on them, but uh I can do that. And then,

10:01

in the meantime, while I'm working on

10:03

these, uh I can have the agent go

10:06

through and dispatch uh dispatch an

10:09

agent to work on the other parts. Then,

10:12

when I finish this, uh typically what I

10:14

will do uh then is I'll go back, and

10:17

I'll say, "Okay, I finished those. Uh

10:19

give me the next issue to work on." And

10:21

then, I can just continue doing this,

10:23

you know, essentially all day. Um as I

10:27

uh I get next issue, next issue, next

10:30

issue. And on good days, I will not have

10:33

to leave this interface at all. I can

10:35

just, you know, mostly work uh through

10:37

the agent uh agent canvas here.

10:41

So, um

10:42

yeah, that that's the majority of the

10:45

work uh that I do here.

10:47

And uh

10:49

I I love to have more feedback on this.

10:52

In future videos, uh I will talk about

10:55

how I scale up parallel workflows, um

10:59

how I get more security and safety when

11:01

I'm running all of these agents in the

11:03

background, uh you know, how to do uh

11:05

credential control, um how to improve

11:08

agents uh as they work more and more on

11:11

these tasks, how to automate repetitive

11:13

tasks, and other things like that. So,

11:15

hopefully this was helpful. I'd love to

11:17

have any comments. I have people uh

11:19

comment on YouTube or join the Slack

11:21

community or other things like that.

11:23

Thanks a lot.

11:26

>> [music]

Interactive Summary

Graham from OpenHands explains his agent-driven daily workflow, which uses AI agents to organize tasks by integrating tools like GitHub and Slack via an 'Agent Canvas'. Instead of managing his tasks manually, he uses his AI agent to scan communications and issues, providing a structured report and guiding him through his work priority by priority. He also demonstrates how to dispatch sub-agents to handle background tasks, such as fixing failing CI builds, to maximize productivity.

Suggested questions

3 ready-made prompts