Prompt in. Response out.
Useful for answering, drafting, rewriting, summarizing, or explaining something when no further action is required.
Receives a question or prompt.
Uses the context supplied to it.
Returns a result for you to use or edit.
Think-Act turns a defined desktop task into a controlled agentic workflow. Give it the goal, relevant context, and optional success criteria. It works with the skills and tools available to the run, pauses when configured actions need approval, and leaves activity and results for you to review.
Think-Act product screenshot
A normal AI response may finish when text is generated. Agentic work has an objective to complete, context to understand, capabilities to use, boundaries to respect, and evidence you can inspect before deciding the task is done.
Agentic does not need to mean uncontrolled autonomy. The useful pattern here is bounded work + explicit access + human review.
Useful for answering, drafting, rewriting, summarizing, or explaining something when no further action is required.
Receives a question or prompt.
Uses the context supplied to it.
Returns a result for you to use or edit.
Think-Act treats agent work as a controlled process with a defined objective and available capabilities, not an unlimited instruction to act.
Task
Defined outcome
Success
Optional criteria
Context
Real source material
Access
Enabled tools only
Policy
Allow, ask, block
Evidence
Activity + result
The workflow starts with the work itself. Think-Act uses the context and capabilities available to the run, surfaces limitations when something is missing, and keeps important decisions with the user.
Agent workflow screenshot
Define the work
Describe the result you want, what the agent should work with, and any boundaries it should follow. Keep the scope narrow enough that the result can be checked.
Bring context
Selected text, files, PDFs, scans, screenshots, images, recordings, and other supplied material can become working context.
Understand the requirement
Think-Act works out which parts of the task can be handled with the context, built-in capabilities, reusable skills, or enabled tools available to the run.
Use capabilities
Skills can guide the method. Tools provide real capabilities. A workflow cannot perform an external action through a skill alone when the required tool is unavailable.
Human decision
Configured consequential actions can wait for confirmation before they execute. Security policy determines whether a supported action is allowed, asks first, or is blocked.
Inspect the run
Tool observations, supported activity events, and results remain available to inspect after the run. Important output should be checked against its source and success criteria before use.
Think-Act combines a Desktop Agent with focused tools for writing, OCR, document intelligence, and screen recording. Use the focused tool when that is enough, or carry its output into a broader agent task.
Desktop Agent
Provide the request, source material and limits. Think-Act can coordinate the capabilities available to the run, expose supported activity for review and pause where the configured policy requires confirmation.
Work from selected or supplied text, then compare and edit the resulting draft before using it.
Explore writing assistance →Use OCR with supported scans, screenshots and image-based PDFs, then organize checked content into fields, tables or summaries.
Explore document intelligence →Capture a workflow, then prepare a transcript, SOP, checklist or bug report that can be compared with the recording.
Explore screen recording →Skills provide reusable methods. Tools provide real capabilities. Connectors expose those tools to the agent. Policy then decides whether a supported action can proceed, must ask first, or stays blocked.
Layer 1 · Instructions
Local instructions can describe the sequence, checks, prerequisites and expected format for familiar work.
Layer 2 · Capabilities
A tool is the callable capability that can read, create, change, query, or otherwise interact with an allowed resource.
Layer 3 · Local access
A local MCP server can expose tools to Think-Act while it is installed, trusted, enabled, connected, and healthy. Local packages run code on your device and require your trust.
Think-Act limits automation through explicit tool availability, configurable action policies, and reviewable activity. The agent cannot use a tool you have not installed, trusted, and enabled.
Enable only what the task needs
Connectors unavailable to a run cannot be used by it.
Allow, ask, or block per action
Set each supported action type according to its impact.
Review what the agent did
Inspect tool calls, results, and observations after a run.
Unavailable connectors cannot be used
They stay excluded until the connection is restored and re-enabled.
Approval Controls Screenshot
Recommended starting policy
Read selected content
Create or change files
Send or publish
Delete or risky commands
The best starting points are narrow enough to review without guesswork. Keep external writes out of the first run, then add a trusted tool only when the workflow genuinely needs it.
Provide the draft and the tone or format you want. Review the rewrite against the original before sending it.
Rewrite with Think-Act →Attach the source and choose the length and focus. Check the key points before sharing the summary.
Summarize with Think-Act →Attach an image or PDF and list the fields you need. Compare the result with the original document.
Extract receipt and invoice fields →Provide the scan and the clauses or terms to check. Review the summary before making a decision.
Review scanned documents →Record the workflow, with optional narration, then use it to draft a step-by-step SOP or checklist.
Create an SOP from a recording →Define the sorting or naming rules. An appropriate supported connector is required before Think-Act can move or rename files.
Tools and connectors →
PixLab’s LLM and document services can transform source documents into structured material for search, extraction, RAG preparation and downstream application workflows.
Three distinct products, one platform. Think-Act is the desktop agent. PixLab APIs are developer building blocks. Vision Workspace provides browser-based document tools. They share document intelligence capabilities but are used independently.
For supported identity-document extraction, review the separate DocScan API.
Clear answers about bounded tasks, human control, skills, tools, connectors, and developer building blocks. Can't find the answer you need? Contact support.
Think-Act is PixLab's Windows desktop AI workspace for writing assistance, OCR and document review, screen recording, reusable local skills, and bounded multi-step tasks. It is designed to keep work visible and reviewable — not to operate as an uncontrolled autonomous agent.
No. Think-Act is designed around bounded, human-controlled workflows. You define the task, choose which tools are available, and configure whether consequential actions require your confirmation. The agent reports what it did and keeps activity available for review.
A bounded task has a clear goal, optional success criteria describing what done looks like, defined source material, and explicit limits on what the agent may change or access. Think-Act works through the task using only enabled tools and keeps the activity visible so you can verify the result.
Not for every task. Writing assistance, OCR, document review, screen recording, and local skills can work without external connectors. Actions inside another application or external system require the appropriate supported connector to be installed, trusted, enabled, connected, and healthy. If it is unavailable, Think-Act reports the limitation instead of inventing the outcome.
A skill provides reusable instructions for how to approach a task. A tool provides an actual capability. A connector exposes tools to Think-Act. Skills cannot bypass missing tools, and local MCP connectors can run code on your device, so install and enable only packages you trust.
Security policy determines whether an action may proceed automatically (Allow), must pause for your confirmation (Ask), or is blocked entirely (Block). Write, delete, and network actions can be placed behind an Ask gate so the workflow waits for your decision before proceeding. Review Think-Act's permission model for the full detail.
Yes. PixLab provides APIs for LLM-ready document parsing, OCR, document segmentation, chunking, embeddings, structured extraction, and vision-language analysis. These can be used independently of Think-Act to build custom agentic applications. Start with the VLM API reference or the LLM and parsing APIs.
Your next step
Download Think-Act for controlled desktop work. Use the supporting links to inspect features and security first, or move to PixLab's APIs when the workflow belongs inside your application.