7 min reading · Practice at your pace
Start a Work Task and Review the Result
Give Work a clear brief and take a task through planning, files, review and revision. Start with a small meeting document, then use the checks to decide when it is ready.
From an idea to a deliverable
Work is Gab AI’s workspace for tasks that need tools and files as well as an answer. An agentic workflow can involve planning, actions, checking and revision. Start with one small outcome and decide how you will review it; a plan or progress message is not the finished result.
Choose a small task you can check
Start with something you already understand. Supply the information needed, name the result and choose a check before sending the task. These task briefs are suggestions; the linked lessons contain their own examples and limits.
Choose your first Work task
| Item | Details |
|---|---|
| Document | Supply notes, audience and required sections. Ask for a short brief. Check names, dates, source facts and unanswered questions. |
| Spreadsheet | Supply rows, units and calculations. Ask for a small workbook. Check a known total and whether the result changes correctly after an input changes. |
| Presentation | Supply the audience, message, source facts and slide count. Check the outline, figures and required content on each slide. |
| Research | Supply a question, date range and evidence requirements. Check important claims and quotations against their original sources. |
| Code | Supply a short example, runtime, wrong result and expected result. Ask for a small correction and rerun the relevant tests. |
A real task from brief to revision
Use Work to investigate a bug, edit the code and run checks. Follow a basket-total fix from the first brief through a follow-up in the same conversation.
A Work task from brief to revision
| Item | Details |
|---|---|
| Brief | Correct the basket total and keep the original tests. |
| Actions | Reproduce the wrong total, correct the loop and run the tests. |
| Files | Source code, a test file and notes explaining what changed. |
| Review | The correction passes the four original cases. |
| Revision | Keep the four cases and add validation with five new cases; all nine pass. |
1. Start with one useful deliverable
Open Gab AI, select Work in the composer and supply the brief and permitted inputs. Choose the available model/action options, then send. Define how you will check the finished result.
Outcome: [A specific file or result for a named audience.]
Inputs: [Permitted source files or verified facts and their role.]
Scope: [Files/actions allowed; requirements and exclusions.]
Preserve: [Correct content, interfaces or earlier outputs.]
Review: [Where your input is needed; do not assume a pause occurred.]
Done means: [Actual delivered files, checks and any incomplete work.]2. Follow progress and answer questions
Read the task’s progress and answer requests for missing information or approval. Available tools depend on the workspace, client and permissions. Check the delivered files and results before treating the task as complete.
3. Open and inspect the delivered files
Open a file card and compare its content with the brief. Read the text, inspect the figures or run the relevant tests. In the basket example, code opened in a source viewer and the notes showed test results. Editing, preview, save and export controls depend on the file type and client.
4. Ask for one focused change
Continue in the same task. Name the artifact, new requirement and what must stay unchanged. In the actual follow-up, negative/fractional values were rejected while the interface and original four tests survived; five new tests then passed too.
Revise only this basket project. Reject a negative or non-integer quantity or unitCents with a RangeError. A quantity of zero is valid. Keep totalCents and the CommonJS export, preserve the original four tests byte-for-byte, and add tests for negative quantity, fractional quantity, negative unitCents, fractional unitCents, and a zero unitCents line. Run the full nine-test suite and record the actual result in DEBUGGING.md. Deliver the complete revised source, test file and notes. No external dependencies, browsing, connected accounts, publishing or deployment. Do not describe this bounded validation as comprehensive security or all possible input validation.5. Decide whether the result is ready
Check both the requested change and the details that should stay. Read failed checks and remaining limitations. For a document, compare facts with the notes; for a budget, check a known total; for research, open important sources. The basket’s nine cases illustrate a check you can repeat, not a guarantee for every project.
Try a simple meeting document
The practice below uses a 45-minute community meeting. Keep source facts separate from suggested agenda items, then revise the introductions while preserving the total duration.
Create a one-page planning brief for a community garden meeting.
Supplied facts: Saturday at 10:30; 12 adult volunteers; meeting point: the garden entrance; duration: 45 minutes.
Include the supplied facts, a suggested three-part agenda, a preparation checklist and questions to resolve.
Keep suggestions separate from supplied facts. The calendar date, street address and organizer contact are unknown; do not invent them.
Deliver the brief as a document artifact. Done means all supplied facts are correct, suggestions are labeled and missing details remain explicit.Revise only the suggested agenda so the first 10 minutes are introductions. Keep Saturday at 10:30, 12 adult volunteers, the garden entrance and the 45-minute duration. Make the agenda total 45 minutes and keep the missing calendar date, street address and organizer contact explicit.- Check Saturday at 10:30, 12 adult volunteers, the garden entrance and the 45-minute duration.
- Check that suggestions are labeled and the missing calendar date, address and contact remain explicit.
- After the follow-up, check that introductions take 10 minutes and the whole agenda still totals 45 minutes.
Optional exercise: plan Star Collector
Create a one-page project brief for a browser game called Star Collector. Include the goal, audience, controls, three must-have features, and a checklist for testing. Keep the scope small and deliver the document as an artifact. Identify assumptions or missing facts.Choose cloud or connected-project work
Work requires Plus and uses applicable credits. Browser Work uses a cloud workspace. Local folders and Remote need a supported client, host and permissions; the setup guides explain those connections.
Starting a Work workflow
Keep the first task small enough to inspect.
How is Work different from Chat?
Chat is useful for discussing a question or snippet. Work can use available tools and files toward a multi-step outcome. Tool availability and permissions vary; a Chat answer does not prove a command ran.
Do I need to connect a repository for this example?
No. The basket task used code supplied in the request and a cloud workspace. Connecting a real local repository is a separate supported-client and permission workflow.
Can Work finish every task without my input?
Do not assume that. Work may need a decision, missing facts or approval, and a tool can fail. Follow its state and inspect the delivered result rather than treating the plan as completion.
Is this Work lesson free to use?
The lesson is public to read. Running Work requires Plus or Plus Premium and uses credits. The current plan, tools, model and follow-ups determine access and usage.
Guides and resources
Find more detail and choose your next step.
Your turn
Create a meeting brief in Work.
Use the supplied facts below to request an editable document. Check the source facts, suggested agenda and missing information before the focused revision.
Write a draft and review the checklist.
Your draft saves in this browser. You can leave and come back.
Take the brief into Work
Copy the brief, open Gab AI and choose Work before pasting and sending it. Open the delivered file and check it against the brief.
These buttons open the product and copy your draft. You choose the mode and send the request yourself.
Open Gab AI for WorkMake one change and check the whole result
Review the first answer, then send this follow-up in the same conversation.
Revise the meeting brief so introductions take 10 minutes. Adjust the other suggested agenda durations to keep the total at 45 minutes. Preserve Saturday at 10:30, 12 adult volunteers, the garden entrance and all missing details. Update any surrounding explanation that no longer agrees with the table. Return the complete revised file.Check that the requested change happened and the correct facts, format and missing details survived. For a file, open the revised artifact and inspect nearby paragraphs or formulas too.