Skip to content

Quickstart

This walkthrough takes you from a new account to a finished piece of work in about ten minutes, with nothing connected. You hand your personal agent a one-off job, open what it made, look at how it got there, correct it once so it remembers, and then turn the job into one that repeats every week. Connecting your tools and creating a dedicated agent come after, once you have seen the loop work.

The example is a sales-pipeline summary, but any job that starts from a file or a web search fits the same steps.

Go to workprentice.ai. Choose Continue with Google, or enter your email and choose Continue with email to receive a sign-in link. New and returning users take the same path, so there is no separate sign-up form.

If your company already uses Workprentice, you land in its organization: an admin invited you, or your email domain has been claimed so matching addresses join automatically. Otherwise, signing up creates an organization of your own with a default workspace, and a short setup wizard opens.

The wizard asks for your company’s name, offers to claim your email domain if you signed up with a work address (so colleagues who sign up later join you automatically), and asks What should Workprentice handle for you? It then shows Start with a team: a list of guilds, ready-made teams of agents with their assignments and working files, ranked by what you described. Pick one and the guild’s enlist dialog takes over; once it is enlisted, the team’s lead agent opens a kickoff session that introduces the team and says what is already running. Build a custom team instead proposes a starter team for you to review before anything is created.

Every step can be skipped, and Skip setup closes the wizard. This walkthrough assumes you skipped the team, so you can learn the loop with the agent you already have. You can enlist a guild at any time later.

Your personal agent is pinned at the top of the sidebar, and the composer on the dashboard talks to it by default. It can already browse the web and read files you give it, so a first job needs no setup. The Setup guide in the sidebar checks off your first steps as you take them and can be dismissed once you’re done with it.

Export last week’s open deals from your CRM as a spreadsheet or CSV, attach it with + → Add files (or drag it onto the composer), and write what you want back:

Here are our open deals. Write a one-page document: a table of pipeline by stage, the five largest deals most at risk and why, and the totals up front.

Sending opens a session, the running record of this piece of work. The agent’s progress appears as it happens.

When the agent finishes, the document appears as a card in the conversation, and the Work products pill at the top of the session lists everything the session produced. Open it to read, copy, or download it. It also appears on the Work Products page, with a link back to this session.

Above the answer, a collapsed line sums up the work. Click it to expand the steps; if a number in the document looks wrong, this is where you find the step that produced it. Checking your agent’s work covers reading the steps, asking the agent about one, and stepping in while it runs.

Suppose the agent counted deals that already closed. Say so in the same session, as a standing rule:

Leave out anything marked Closed Won or Closed Lost. Remember that for future pipeline reports.

The agent redoes the work, and a Remembered step appears in the transcript when it saves the lesson, which then carries into every future session.

It is also worth telling the agent who you are, what you work on, and how you like results delivered. What it learns from conversation becomes memory in the same way.

Once the output is right, choose Save as Assignment in the line of details under the session’s title. The agent reads the conversation and drafts an assignment with a Name and Instructions that capture what you settled on, including your correction. Choose Edit & Save, and the new assignment opens on its own page, where every field saves as you change it.

Run now at the top of the page runs it immediately. To make it weekly, open the Schedule tab, check Run on a schedule, choose Weekly, and pick the day, time, and timezone.

Before you turn the schedule on, note that a later run can’t see the file you attached today. A weekly job needs the agent to fetch fresh data itself, which is what connecting a tool is for. Until then, leave the assignment unscheduled and use Run now while you refine the instructions.

Connecting a tool lets agents pull data and take actions in it on their own. Every connection is made under Skills & integrations → Integrations, and Available to in the connect form says whose account it is.

Your own accounts, such as your mailbox or calendar, are Only you. Only agents you own use them: your personal agent and any private agents you create. Work done with them is labeled Runs as you.

Company accounts, such as the team’s CRM or ticket queue, are shared with This workspace or Everyone in the organization, and a workspace admin connects them. If you created the organization, that admin is you. Every agent in the workspace can use a company account, including agents shared with your team, and work done with one is labeled Runs on a company account.

For the pipeline report, the CRM is usually a company account. Open it from the list and choose Connect. Depending on the provider you either sign in and approve access, or paste an API key into the fields shown. The integrations page covers every option, and the catalog lists what is available.

Once connected, update the assignment’s instructions to pull from the CRM instead of an attachment. There is nothing else to wire: the CRM’s tools appear in the agent’s toolkit automatically. If an agent needs an account that isn’t connected yet, its session says which ones, and whether it would run as you or on a company account.

Your personal agent is general-purpose and private to you. For a job the team relies on, create a dedicated agent: choose New agent on the Agents page (or New agent in the sidebar), give it a Name, and describe it, the way you’d brief a new hire. A Pipeline Analyst might be told:

Report on the sales pipeline every Monday. Lead with the headline figures, flag risks early, and never pad a report.

The agent writes its own personality from that and proposes the recurring work as an assignment.

Skills, integrations, memory, and guardrails are all configured afterward on the agent’s page. To add work by hand, open its Assignments card, choose Add assignment, and write the Instructions the same way. Be explicit about the deliverable; “produce a document with a summary table” beats “summarize the pipeline.” The AI-assist button can draft instructions from a short description. An agent starts private to you, and you can share it with the workspace once it works.

For the complete site index, see llms.txt.