Skip to content

docs: capability wording for the Citrix backend and the API step's source - #303

Merged
abrichr merged 1 commit into
mainfrom
claude/capabilities-wording
Oct 28, 2026
Merged

abrichr merged 1 commit into
mainfrom
claude/capabilities-wording

Conversation

@abrichr

@abrichr abrichr commented Oct 28, 2026

Copy link
Copy Markdown
Member

Follow-up to #302. Two corrections to match the monorepo's CAPABILITIES.md (OpenAdapt#1614).

File Before After
reference/capabilities.md, llms.txt Agents can drive the recording on web, native Windows, RDP and Citrix. ...through the web, native Windows, RDP and Citrix backends.
reference/capabilities.md, llms.txt pixels only where nothing else exists, such as RDP and Citrix ...such as a remote desktop
reference/capabilities.md, llms.txt Works across surfaces in one workflow. Web, native Windows and macOS, RDP and Citrix. Backends for web, native Windows and macOS, Linux, RDP and Citrix.
reference/capabilities.md Runs steps as direct API calls through hand-authored bindings. In an OpenEMR benchmark the API step took 0.6 s ... Runs steps as direct API calls (ApiActuator). In an OpenEMR benchmark, an API step compiled from the recording's network traffic took 0.6 s ... (the benchmarked step was compiled from captured traffic, per SCOREBOARD.md, not hand-authored)

@abrichr
abrichr enabled auto-merge (squash) October 28, 2026 23:45
@abrichr
abrichr merged commit 01bc8e7 into main Oct 28, 2026
8 checks passed
@abrichr
abrichr deleted the claude/capabilities-wording branch October 28, 2026 23:55
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