KOVE Komputing logo

Workshop 260908

Agentic AIYPO logo

Who already has their own AI chief of staff?

A 120-minute working session on what makes an AI agent useful, usable and ready for real work.

By the end of the workshop, each participant will have a first AI Chief of Staff ready to use.

120 minutes · Live demo · Guided installation · Hands-on workshop

Agentic AI · Recent signals

Last month many disruptive news.

Front page

THE AGENTS BROKE OUT

During a cyber evaluation, OpenAI research agents bypassed isolation, created an unauthorised communication channel and compromised parts of Hugging Face’s infrastructure.

“A warning shot for agentic security.”

Front page

GROK BOT GETS ITS OWN COMPUTER

xAI launched always-on AI teammates with cloud computers, app access, memory, routines and the ability to work across real tools.

AI colleagues that keep working when you step away.

Front page

AI AGENTS GET THEIR OWN SOCIAL NETWORK

Thousands of autonomous agents began posting, debating and creating communities on Moltbook, a Reddit-style network built for agents rather than people.

Agents talking to agents, at scale.

Front page

50 AGENTS REVIEW 466 MILLION LINES OF CODE

466,000,000

The Government of Alberta used Claude agents to examine a vast code estate in 20 hours, while engineers retained approval over production changes.

Front page

AGENTS CAN NOW RENT HUMANS

RentAHuman, a Y Combinator-backed marketplace, lets AI agents hire real people to complete tasks in the physical world, from deliveries to on-site checks.

Agents gain hands in the real world.

Agents now have memory, tools, computers and other agents to talk to.

0115 min

What is an agent, and how does it differ from an LLM

From LLM to Agentic AI to Physical AI

LLM

Generates answers and content

AGENTIC AI

Autonomous systems able to act in the real world — digital

PHYSICAL AI

Autonomous systems able to act in the real world — physical

  • From generating content to delegating real work.
  • A useful agent needs a clear objective, relevant context, tools, memory, boundaries and human approval.
  • An agent needs an operating framework, not only a capable model.

01 · What is an agent, and how does it differ from an LLM

Prompt → Work
PromptWork
01Objective
02Context
03Tools
04Memory
05Boundaries
06Approval
An agent is a system, not just an LLM: a car's parts (power unit, energy, drivetrain, steering, braking, control unit) compared to an agent's parts (LLM, connectors, memory, objectives, constraints, approval, actions)

An agent is a system, not just an LLM — like a car, it becomes useful when its parts work together.

0215 min

What we want from an agent

  • Works where you work: chat, browser, desktop and mobile.
  • Own environment, scoped connectors and useful memory.
  • Human approval before any external action.

02 · What we want from an agent

Agent system layers
  1. L01

    Channels

    TelegramWhatsAppDiscordSlackBrowser
  2. L02

    Dedicated environment

    Isolated VMSeparate dataPersistent context
  3. L03

    Connectors

    Scoped accessPer userHuman approval
  4. L04

    Memory & control

    Knowledge basePreferencesLive sourcesRetrieval
  5. L05

    Brain

    LLMReasoningInstructionsPlanning

Workflow

Multi-step automations triggered by a command or event, so recurring work runs without manual input.

Cronjob

Scheduled tasks that keep reports, reminders and background checks moving on a fixed cadence.

0315 min

Live Demo

  • A visible example from request to published output.
  • A real working workflow: send the KOVE agent a photo and a voice note.
  • The workflow drafts an article following defined guidelines, constraints and tone of voice, then publishes it on the website blog and on LinkedIn with business page references.

03 · Live Demo

Live workflow: photo + voice note → published content

Input

Photo

Sent to the agent

Voice note

Spoken instructions and context

KOVE SuperAgent logo

KOVE SuperAgent

Runs the writing workflow: guidelines, constraints, tone of voice

0415 min

Installation

KOVE SuperAgent logoKOVE SuperAgent
  • Activate the agent on each participant's phone with a tested QR code or link.
  • Confirm access and show the first useful interaction.
QR code: scan to open kovesuperagent.com/onboarding?plan=business

KOVE260908

Set up

Link your email and calendar

Ask KOVE SuperAgent to connect the tools you use every day. Say it out loud or type it as a message.

Connect my emails

“Connect to my emails”

“Connect to my emails”

Connect my calendar

“Connect to my calendar”

“Connect to my calendar”

Now we are ready for the most practical part of the workshop — let us see if the agent was paying attention.

0545 min

Hands-on workshop

  • First 15 minutes: define the expected outcome. Each participant selects one real process, available information, desired output, approval point and success measure.
  • Next 30 minutes: participants prepare a first delegation, workflow or agent brief based on their own activity.
  • Goal: leave with one simple, testable use case.

LIVE EXERCISES

TWO THINGS TO BUILD AND TRY

Create one workflow. Schedule one briefing.

EXERCISE 1 · WORKFLOW

Turn a voice note into prepared actions.

Send your agent a short voice note with:

  • one email you need to send to a real client contact, with the content you want to include;
  • a calendar reminder you need to set.

The agent should:

  1. identify the contact and relevant context;
  2. draft the email in your usual tone;
  3. prepare the calendar reminder with title, date and details;
  4. show everything for approval before sending an email or creating the calendar event.

The agent prepares the work. You decide what goes out.

EXERCISE 2 · CRON JOB

Schedule your morning briefing.

Create a weekday briefing, delivered at 08:00. It should include:

  • today’s calendar and any preparation needed;
  • important unread emails that need a reply or decision;
  • three relevant news items on topics you choose;
  • priorities, deadlines and decisions for the day.

Run it once during the workshop, then decide whether to keep, edit or remove it.

A workflow responds to a request. A cron job works for you on a schedule.

BUILD · TEST · KEEP WHAT IS USEFUL

12
0615 min

Wrap-up and results

  • Review selected use cases and outputs.
  • Identify the owner, first verifiable action, access required and next step for the most promising cases.
  • Distinguish a short pilot from a full implementation.
  • Participants may keep their demo account after the workshop or request its deletion.

Leave with a use case you can test.

The workshop ends with a concrete starting point: one process, one first delegation and a clear next action.

QR code: scan to open this presentation

Link to this presentation