Dated agent notes

Files in, a usable document back.

Multi-step file and research tasks using the inputs and tools you authorize.

Access & setup

Availability depends on plan, workspace and rollout. Check file/tool access in the chosen task.

Limit to keep in view

Cloud work does not inherit your computer’s files or sessions. Local connected work needs the computer online.

Code, folders and repeatable file work.

Tasks that benefit from inspectable files, code changes and focused checks.

Access & setup

Use an available Codex app, CLI, IDE or cloud task with the right project access.

Limit to keep in view

A goal does not grant extra permissions. Separate chats need their own usable inputs; avoid overlapping file writes.

Coordinate an ongoing responsibility.

Follow-up, context and delegated work across supported connected tools.

Access & setup

Gradual rollout to eligible plans, regions and workspaces; administrator settings can apply.

Limit to keep in view

Connecting a source alone does not monitor it. Confirm any schedule and actual delivery; instructions do not grant access.

Build a small web tool.

A reviewable tracker, dashboard or other website with an explicit storage and audience plan.

Access & setup

Documented public beta for supported plans; workspace settings and permissions apply.

Limit to keep in view

Saving a version differs from deployment. Deployment URLs are production; shared storage and visitor access need configuration.

Use interactive controls inside a conversation.

Tools that benefit from a form, table or other interface on a compatible host.

Access & setup

Requires a supporting host and connected MCP tool; availability and permissions differ.

Limit to keep in view

A widget is not a promise of durable business storage. Tool functionality should also work without the interface.

Files and research outputs for office work.

Multi-step noncoding tasks that produce documents, spreadsheets or presentations.

Access & setup

Paid plan and rollout/workspace settings apply. Check the current surface and connected tools.

Limit to keep in view

Current schedules run remotely using account files/connectors. Required local file/app work runs locally; pre-October-6 Pro/Max computer schedules remain local. Saving and verifying a schedule are separate steps.

Implement and check work in a project.

Advanced file/code tasks where a technical user can inspect commands and changes.

Access & setup

Needs a configured Claude Code environment and suitable file/tool permissions.

Limit to keep in view

Instructions shape behavior; runtime permission rules control access. Cloud routines, local schedules and session loops have different limits.

Run an agent through a self-hosted gateway.

Advanced ongoing work through configured messaging, tools and stored jobs.

Access & setup

An operator must configure hosting, provider credentials, channels and permissions.

Limit to keep in view

One gateway is one trusted boundary. Restrict tools and message delivery explicitly; a stored job is not proof of successful delivery.

Persistent agents working across connected apps.

Ongoing cross-app work on a cloud computer, with routines and coordinated Bots documented by the vendor.

Access & setup

Beta for eligible Grok and Cursor subscriptions; enterprise access is waitlisted. Check current plan and account eligibility.

Limit to keep in view

Vendor demonstrations are not our task trials. Verify authorized source access, saved routine and actual output delivery before relying on it.

Business tasks through connected tools.

Small-business file and app work through supported connectors, with context supplied by the owner.

Access & setup

Official October 8 update describes availability in the US and Canada. Connector access and account settings still need checking.

Limit to keep in view

The vendor documents approval before publishing, sending or spending. This guide has not verified those controls or a delivered task in an account.