This week’s read
Four changes to make before your next agent run
Google gave no-code agents identities, audit trails, and a stop button. Gemini 3.7 Flash launched with a temporary half-price rate. Grok Bot put persistent AI teammates on a shared cloud computer. Codex reached GitLab.
The question is whether you can identify an agent, limit it, stop it, and reconstruct what it did.
No-code agent controls
Google gave no-code agents identities, stops, and logs
DVx control map based on Google’s August 17 Workspace Studio announcement.
- What changed
New Workspace Studio flows can run under least-privileged identities. Admins can attribute actions, revoke OAuth scopes, suspend flows, gate external sharing, and apply DLP on eligible plans.
- Why you should care
A no-code flow can now look more like a managed service account. Existing flows do not inherit the controls yet.
- What to do next
Create one low-risk flow. Remove a permission, suspend it, and save the visible events in
workspace-flow-control-record.md.
The control plane
The new-flow boundary is the decision
The controls matter because they can stop one workflow without revoking a person’s whole account.
- Identity
- Least-privileged identity for newly created flows first.
- Attribution
- Unique ID and flow context in audit events during the beta rollout.
- Stop
- Revoke a selected OAuth scope or suspend the flow.
- Data
- Approval gates and DLP on eligible higher-control plans.
The decision: test the identity, stop mechanism, and log together before using the flow on production data.
Primary source: Google Workspace. Verified August 23, 2026. Controls apply to newly created flows first. DLP availability varies by plan.
Primary sourceGoogle Workspace Studio security controls.
Model economics
Gemini 3.7 Flash launched with a price-expiry date
DVx cost comparison using Google’s published API rates and one fixed workload.
- What changed
Gemini 3.7 Flash became generally available on August 13. Standard API rates are $0.75 per million input tokens and $3.75 per million output tokens through December 31. Both double on January 1, 2027.
- Why you should care
A cheap December pilot can have a different January budget.
- What to do next
Compare one task with your current model. Record success, tokens, latency, and cost in
model-cost-and-quality.csv.
Same workload · 100k input + 20k output
The standard rate doubles on January 1
The decision: use the January rate in a recurring forecast unless the workload ends first.
Primary sources: Google and Anthropic pricing. Verified August 23, 2026. Output includes thinking tokens. Holds token counts constant. Excludes quality, caching, tools, grounding, regions, subscriptions, and discounts.
Primary sourcesGemini API changelog; Gemini pricing; Anthropic pricing.
Persistent agents
Grok Bot made the agent desktop persistent
DVx boundary map based on xAI and Cursor’s Grok Bot documentation.
- What changed
Grok Bot launched August 11. Named agents get a persistent cloud computer, browser, terminal, app sessions, memory, and routines. They coordinate and keep working after your laptop closes. Access expanded August 21 across eligible Grok and Cursor plans.
- Why you should care
Every Bot owned by one user shares its computer, files, browser sessions, logins, and local permissions. Separate Bots are not security boundaries.
- What to do next
Pilot one read-only job with a new account and no local access. Record sessions, approvals, routing, data settings, spend, and cleanup in
grok-bot-boundary-record.md.
The actual security boundary
One user gets one shared computer
Named teammates are separate working contexts, not separate credential zones.
- Storage
- Cloud storage is required. Legacy Privacy Mode is unsupported.
- Actions
- Approval rules and Auto Review exist. Least privilege still matters.
- Models
- Product-managed routing and failover. No admin model picker.
- Oversight
- Action audit view and Bot-specific spend cap are still coming.
The decision: scope credentials to the user’s whole Bot roster, then keep consequential actions behind approval.
Primary sources: xAI and Cursor. Verified August 23, 2026. The August 11 launch was missed in Issue 003. The August 21 access expansion falls after this issue’s core research window.
Primary sourcesGrok Bot launch; access expansion; security and privacy; team controls.
Agentic engineering
Codex reached GitLab
DVx workflow map based on OpenAI’s August 19 GitLab beta announcement.
- What changed
The August 19 beta lets every ChatGPT plan connect GitLab to Codex cloud.
@codexcan start from an issue or merge request and review the result.- Why you should care
GitLab teams get an issue-to-agent-to-MR loop without moving repositories. Self-Managed installations need admin setup and GitLab 19.0 for webhooks. Reviews can fail when GitLab omits oversized diffs.
- What to do next
On one small repository, record cloud execution, webhook permissions, branch rules, diff coverage, and reviewer in
codex-gitlab-pilot.md.
Primary sourcesOpenAI product release notes; Codex plan guide.
One workflow to try · 30 minutes
Run a Grok Bot boundary test
- TaskGive one Bot a read-only, reversible research task.
- ApprovalStop sending, publishing, deleting, and local commands.
- InspectCheck cloud files, browser session, actions, and usage.
- Clean upRemove files, sign out, and revoke the connector.
Keep the task, evidence, approval, and cleanup record.
Portfolio watchlist
Three checks before the next run
Engineering
GPT-5.6 Sol Ultrafast reports up to 750 output tokens per second. Access is limited and price is missing.
Data
OpenAI previewed cross-session safety processing for ZDR customers. Keep today’s endpoint matrix until the September paper arrives.
Education
ChatGPT for Teens adds safeguards and parent links. Test classification and escalation.
Term of the week
Agent identity
A distinct identity used by an automated workflow, with its own permissions and audit trail. It lets you stop the workflow without revoking a person’s entire account.
Field Manual impact
Manual 02 changes
The Overnight Build should add the Grok Bot shared-computer boundary, cloud-storage requirement, approval rules, cleanup procedure, and missing action audit and spend cap.
Source ledger
| Development | Announced | Available or effective |
|---|---|---|
| Workspace Studio controls | August 17 | New admin controls from August 17. End-user actions from August 20. Existing flows later. |
| Gemini 3.7 Flash | August 13 | Generally available August 13. New price January 1, 2027. |
| Grok Bot | August 11 | Early beta August 11. Access expanded August 21. |
| Codex for GitLab | August 19 | Beta August 19. |
Verification notes
- Core research covered August 13 through August 19. Selected links were checked August 23.
- Announcement, availability, rollout, and scheduled-price dates are separate.
- Workspace Studio controls cover newly created flows first.
- Gemini’s January rate is scheduled. The chart compares APIs, not seats or subscriptions.
- Grok Bot requires cloud storage. All Bots owned by one user share one cloud computer and its files, sessions, and logins.
- Grok Bot’s August 11 launch was missed in Issue 003. The August 21 access expansion is outside the core window.
- Codex runs in its cloud. GitLab setup and diff limits are explicit.
- No confidential portfolio information is included. The published copy contains no em dashes.