Skip to content

feat(agent): expose native app affordances to Code Mode - #6544

Merged
benjaminshafii merged 1 commit into
devfrom
fix/native-affordances-codemode
Oct 27, 2026
Merged

benjaminshafii merged 1 commit into
devfrom
fix/native-affordances-codemode

Conversation

@benjaminshafii

Copy link
Copy Markdown
Member

What is this about?

Let assistants combine OpenWork reads and sidebar-group changes in one Code Mode script.

What problem does it solve?

Organizing many conversations currently requires a separate tool call for every move instead of one checked loop.

What was the situation before?

The native app tools worked directly but did not appear in Code Mode discovery, so scripts could not call them.

How is this implemented?

  • Behind nativeAffordanceCodeMode (cloud and self-hosted, off), project the resolved rollout into the V2 context plugin.
  • Publish the existing openwork_context, openwork_query and openwork_execute tools to Code Mode, reusing the restricted session-group routes and validation.
  • Mark captured Code Mode requests and recheck the rollout before writes. Disabling it blocks subsequent marked writes; existing direct commands remain available.
  • Fail closed on stale offline rollout grants; retain cancellation and direct-only browser, computer and file-transfer tools.

What else changed?

  • Add rollout documentation, regression fixtures and verification notes.

Release note

Assistants can organize conversations through a single Code Mode script while preserving excluded sessions and checking the result.

Evidence

apps/server/test/openwork-context-codemode-native.test.ts — before: discovery omits both native tools; after: the real V2 engine discovers them and runs query → moves → verification while preserving an exception. No UI E2E; this is a native-engine integration change with host-route validation tests.

@vercel

vercel Bot commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
openwork-app Ready Ready Preview Oct 27, 2026 5:08am UTC
openwork-den Ready Ready Preview Oct 27, 2026 5:08am UTC
openwork-diagnostics Ready Ready Preview Oct 27, 2026 5:08am UTC
openwork-landing Ready Ready Preview, v0 Oct 27, 2026 5:08am UTC

Request Review

@benjaminshafii
benjaminshafii deployed to pr-internal-specs October 27, 2026 05:07 — with GitHub Actions Active
@github-actions

github-actions Bot commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor

OpenWork evidence

Status Commit Preview Updated
🟡 Updating evidence 35615c4 View run 2026-10-27 05:08:10 UTC

A preview for this commit is being prepared.

@diff-warden diff-warden Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Warden clearance. Complete security and confidentiality review of 35615c476068edf3809038f34a4fe001bdf5d087 found no high or medium security findings and no confidentiality findings. Any new push dismisses this approval. Analysis run

@diff-warden

diff-warden Bot commented Oct 27, 2026

Copy link
Copy Markdown
Contributor

Warden: approved

No high or medium security findings and no confidentiality findings.

Reviewed 35615c476068 · Warden run · Updates after every Warden run.

@benjaminshafii
benjaminshafii merged commit b9f53ce into dev Oct 27, 2026
37 of 39 checks passed

This branch was successfully deployed

5 active deployments
Preview – openwork-den — 35615c47 Deployed Oct 27, 2026 by vercel[bot]
Preview – openwork-app — 35615c47 Deployed Oct 27, 2026 by vercel[bot]
Preview – openwork-landing — 35615c47 Deployed Oct 27, 2026 by vercel[bot]
Preview – openwork-diagnostics — 35615c47 Deployed Oct 27, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant