Build your personal assistant with Claude Cowork

30th June 2026October 3th 2026Flavien BessetAgents

Article published in June 2026, updated on September 27, 2026: Cowork It now runs in the cloud and has merged with the chat. Passages over memory, scheduled tasks, Dispatch, and permission modes have been updated.

With Claude Cowork When configured correctly, you can build the professional equivalent of Jarvis: an assistant that understands your role, processes, and preferences, is connected to all your tools, and prepares your workspace every morning without you having to ask. This article—which complements our series on Cowork from a more personal and everyday perspective — shows you exactly how. If you're starting out, the Cowork goes back to basics.

One crucial point to make from the outset, because it changes everything. What distinguishes a Jarvis from a simple tool can be summed up in one word: the proactivity based on the overall contextA tool is waiting to be used. An assistant that you know and that acts on a rhythm becomes a presence. To use a fitting phrase: a good assistant doesn't wait for you to ask for your morning briefing — they have already prepared it when you sit down.

Let's see how to build this, pillar by pillar.

The four pillars of a professional Jarvis

A Jarvis rests on four foundations, which must be built in order:

Omniscience — he knows who are you et what matters : your knowledge base.
Mastering your processes — he knows how you worknot just what you do.
The connected senses — he reaches all your tools : the connector layer.
Proactivity — he acts at a rhythm, without being asked: programmed rituals.

The first three pillars give Jarvis his knowledge. The fourth brings it to life. Let's build them.

Pillar 1 — Omniscience: giving your Jarvis a brain

It all starts with what Jarvis knows of you. And the quality of everything that follows depends on the quality of that foundation. As we explained in the first article of the series, Cowork It doesn't just work with what you type, but with everything it can read in the folder you give it access to. Your task here is to fill that folder with genuine knowledge about your work.

The most effective structure consists of three files, which answer three distinct questions:

"Who I am." Your role, your organization, the size of your team, your responsibilities. The difference in wealth is striking between "sales manager" and "sales director of a Series B SaaS publisher, team of twelve, target mid-market The more precise it is, the more accurately Jarvis's reasoning is.

"How I work." Your preferences, your style, your quirks — we will come back to this in detail in the next pillar, because it is the heart of the matter.

"What matters right now." Your three to five priorities for the quarter. That's what gives Jarvis a all filter brewing methods. To distinguish the urgent from the noise: "finalize the Acme contract by the end of March, recruit a senior salesperson before the end of the quarter, reduce the sales cycle from 45 to 35 days." This file, by its very nature, updates weekly.

An often unexpected benefit of this exercise: even before Jarvis does anything, Explicitly articulating your working methods already has value.The real skill to acquire is not to "prompt" better, but to state one's own processes precisely enough for a machine to execute them. Few people have ever done this for themselves.

Persistent memory: integrate your Jarvis once, not every morning

Without persistence, a Jarvis would suffer from amnesia every morning. Cowork It gives it two forms. The account memory, shared between the cat and Cowork Since August 25, 2026, it remembers who you are and your preferences from one conversation to the next. Projects add a workspace that stores files, instructions and memory specific to a construction site, through the sessions. Think of it as the from your assistant — you do it once, instead of having to explain everything again for each task.

And this memory composeOver time, Jarvis learns what you've worked on, what you prefer, and the diagrams you've created. The more you use it, the less you have to explain. And since September 16, 2026, the chat and Cowork now form a single interface (progressive deployment): there is no longer a mode to open to find this context, Claude decides himself when a request deserves a task with files and tools.

Pillar 2 — Processes: teaching your Jarvis how to you work

This is where the difference between a generic assistant and business assistant. Encoding facts is not enough; you must encode your way.

In practical terms, the "How I work" file should capture what an excellent colleague would take months to learn from you through observation:

Your communication style, with real examples. "Short sentences. No exclamation marks in work emails. I end each meeting by restating the action items. Slack for internal communication, email for external." (For an email draft) sounds like youGive Jarvis real emails that you have written.
Your decision rules. What makes a subject a priority, what you delegate, what you always want to validate yourself.
Your rituals. The order in which you tackle your day, the format of your reports, your reporting frequency.

Skills for your recurring processes

Beyond context files, your most stable processes benefit from becoming... Skills & Tools — these markdown modules that activate automatically when the context warrants it (we detailed them in the second article). A "prepare meeting minutes" skill encodes your exact template once, and Jarvis applies it without being asked again.

The best method for extracting these processes is not to write them down from memory—where one always describes an idealized version of oneself—but to get interviewed by ClaudeAsk them to ask you questions, one at a time, about how you produce a particular deliverable or make a specific decision, and then to create the file based on your answers. The result is much more faithful to your actual process.

Pillar 3 — The senses: connecting your Jarvis to all your tools

A blind and deaf Jarvis is useless. connectors are his senses: they give him access, in reading and sometimes in action, to the tools where your work really lives — messaging, calendar, document space, note management, team messaging.

Activation is done from the personalization area of CoworkThis is usually done via an OAuth authorization that takes one minute per service. The most cost-effective connections for an everyday assistant are: your email, calendar, file storage, note-taking tool, and team messaging. The real power emerges when multiple systems collaborate: comparing a meeting transcript with your notes, or cross-referencing an email thread with your calendar to prepare for an appointment.

To go faster, start from Productivity plugin Published by Anthropic, it's designed specifically for this purpose: managing tasks, calendars, daily workflows, and personal context by connecting to common tools. You then adapt it to your own vocabulary and processes.

Two rules of caution from the outset. Opt for connectors made of read only Wherever possible: a Jarvis who reads your email is valuable; a Jarvis who can send on your behalf is a risk. Authenticate each connector before programming Whatever the case may be: the most frequent cause of failure of an automated ritual is simply an unauthenticated service.

Pillar 4 — Proactivity: The rituals that make Jarvis feel alive

This is the heart of the reactor. Everything above gives Jarvis his knowledge; these are the scheduled tasks which set it in motion. You describe a recurring task once, and Cowork It executes automatically at the chosen rate, utilizing all the context you have built. To create one, type /schedule in a task, or open "Scheduled" in the sidebar.

Here are the rituals that make a true professional Jarvis.

The morning briefing — the signature ritual

It is le Jarvis moment. A task triggers every morning before you arrive, scans your sources, and drops a structured point waiting for you. Rather than digging through your email and scrolling through your channels, you read what matters in two minutes.

An effective instruction template looks like this:

Every workday at 7:30 a.m.: I review emails received since 6:00 p.m. yesterday and categorize them as URGENT (from my direct managers or marked important), ACTION REQUIRED (response expected), or FOR INFORMATION. For urgent emails, I prepare a draft of a short reply. I check my agenda for the day; for each meeting with external participants, I note who is attending and retrieve the last email exchange with them. I review the #general and #product channels for long or heavily commented threads. I compile everything in /Daily/YYYY-MM-DD-briefing.md with the sections Urgent, Agenda, Team Points, and Action Items.

When you open your computer, the document is there. For many users, this transforms 45 minutes of scattered gathering into 5 minutes of pre-sorted reading.

Meeting preparation

Before each meeting, Jarvis gathers the context: who is participating, what was discussed last time (by reviewing transcripts or recent threads), and the preparation you should do. You arrive at the meeting knowing exactly where you left off.

Smart inbox sorting

Jarvis reads your email, categorizes each message (reply / for info / action / ignore), and prepares drafts that sound like you. The golden rule, non-negotiable: he records drafts, he never sends them. The decision to send remains yours.

The weekend review

Every Friday, Jarvis gathers what happened during the week — meetings, decisions, commitments made — and writes a summary. Better yet: he identifies patterns that daily rituals, taken in isolation, would not have seen.

Recurring monitoring

Once a month, Jarvis checks a list of competitor websites, notes changes in features, pricing, or messaging, and adds them to a tracking document. This monitoring becomes a self-improving asset.

Things you need to know from the design stage. Since the passage of Cowork In the cloud, in July 2026, a scheduled task runs on Anthropic's infrastructure, even when the computer is turned off Your briefing is ready at 7:30 AM without your laptop being left on. Exception: a ritual that reads files or connectors located only on your machine requires the desktop application to be open on a powered-on computer; for these, keep a machine active or move the source files into a Project. And Always trigger a task manually the first time to verify that it draws from reliable sources before trusting it. The initial briefing will be useful but imperfect; after a week of adjustments, it becomes precise.

Jarvis in your pocket: trigger remotely

A Jarvis shouldn't be stuck at your desk, and he isn't anymore. Since July 2026, Cowork It can also be used from the mobile app (iOS and Android): a task launched from your phone runs in the cloud, even when your computer is off. For tasks that require your local machine (local files, local connectors, browser control), there are... DispatchCurrently in limited beta on the Pro and Max plans: you text Claude from your phone, "Launch the competitive audit on the Monitoring file," and he works on your desktop computer, which must be turned on with the application open. You return to the finished work. The trigger fits in your pocket; the execution takes place in the cloud or on your machine, depending on the task's requirements.

The most powerful effect: a Jarvis that strengthens itself

Here's what the most advanced users observe, and what separates an assistant from a simple set of automations: The rituals feed off each other. The morning briefing incorporates a commitment extracted from the previous day's meeting follow-up. The email draft draws on the context gathered during meeting preparation. The weekly review identifies trends across all other data streams.

Each system feeds into the others, and the more you use them, the richer the context becomes and the more refined the results. This is the fundamental difference between a prompt and systemsYour Jarvis doesn't stay static: it becomes, week after week, more accurate about your work.

The safeguards of a trusted Jarvis

Giving an assistant broad access to your professional life requires discipline. Four principles:

Drafts by default, never sent automatically. Everything that goes outwards — emails, messages, posts — goes through your approval. Jarvis prepares; you decide.
The right permission mode. Cowork We offer three options: manual approval, where Claude asks for your agreement before each action, for new or sensitive flows; automatic approval, where each action is checked and those deemed dangerous are blocked, for tried and tested rituals; and the no-approval mode, where nothing checks the actions, to be reserved for low-stakes tasks that you supervise.
Reading alone as the default posture on the connectors, expanded on a case-by-case basis.
Refreshing the context. A Jarvis is only useful if it is up to date: update the "what matters right now" file every week, and code new patterns as soon as they are repeated.

Your Jarvis, and beyond

Building a professional Jarvis isn't just about personal productivity gains. It's a change in your relationship to your own work.

First, because the exercise forces you to achieve a rare clarity. Putting into words who you are, how you work, and what truly matters—precisely enough for a machine to execute—is an act of professional lucidity that most people never undertake. The Jarvis is the pretext; the clarity is the real benefit.

Secondly, because what Jarvis gives you is not abstract time, it's...attentionBy taking over information gathering, formatting, and operational monitoring, it frees up mental space for what a machine cannot do: decide, create, judge, and connect. This is precisely the human-AI collaboration we advocate—not an AI that replaces, but an AI that takes the tedious layer off your shoulders to return you to your true self.

Finally, because the individual Jarvis is the gateway to collective transformation. When each employee has an assistant who understands their work and tools, the entire organization shifts its paradigm. This is precisely the link between this article and the previous one in our series: today's personal Jarvis is the building block of tomorrow's enterprise AI operating system.

One final recommendation, valid regardless of your level: don't try to build everything at once. Start with the morning briefing. Build its context files, connect two or three tools, program it, live with it for a week, and adjust. Once this first ritual has become essential, add the next. Jarvis is built in layers, and each layer interacts with the previous ones.

Your roadmap: a Jarvis in one weekend

Create a dedicated project : it retains Jarvis's own files, instructions and memory, in addition to your account's memory.
Write the three context files : "who I am", "how I work", "what matters right now" — ideally via interview.
Encode your recurring processes into Skills, with real examples of your style.
Connect your senses : messaging, calendar, files, notes, team messaging — read-only by default, and authenticated.
Start with the Productivity plugin and adapt it to your vocabulary.
Schedule the morning briefingtriggered manually once initially to validate it.
Establish the rule "drafts only" for everything that goes outwards.
Add one ritual per week : meeting preparation, inbox sorting, Friday review, monitoring.
Install the mobile app to launch your rituals from your phone, and activate Dispatch (beta, Pro and Max) for those who need your post.
Refresh the context every week and let memory compose.

Sources. Claude Help Center (accessed September 27, 2026): Use Claude Cowork on web, desktop, and mobile, Claude Cowork and chat are one Claude, Use Claude's chat search and memory, Organize your tasks with projects, Schedule recurring tasks in Claude Cowork, Use Claude Cowork safely.

To go further: the difference between Copilot Cowork and Claude Cowork, how transform Cowork factory-made deliverables and the steps for configure Claude Cowork for the first time.