Skip to content

Harden agent protocol and platform integration workflows - #2

Draft
ecxwxz wants to merge 2 commits into
PureStream108:mainfrom
ecxwxz:agent/ipc-action-agent-runtime
Draft

ecxwxz wants to merge 2 commits into
PureStream108:mainfrom
ecxwxz:agent/ipc-action-agent-runtime

Conversation

@ecxwxz

@ecxwxz ecxwxz commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

What changed

  • Added a bounded compatibility layer for agent JSON/tool-action responses, including fenced or wrapped JSON, provider-specific argument shapes, conservative repair, and clearer protocol failures.
  • Hardened orchestration and member tool loops against malformed actions, repeated calls, ambiguous final responses, and oversized protocol payloads.
  • Expanded platform challenge and attachment mapping compatibility while adding response-size, attachment-count, path, URL, header, secret, and cleanup safeguards.
  • Prevented challenge API credentials from leaking to cross-origin attachment hosts; cross-origin attachment authentication now requires separately confirmed attachment_headers.
  • Added the project-local integrate-ctf-platform skill, workflow reference, and offline payload/workflow validation scripts.

Why

Agents and providers do not always emit perfectly strict JSON even when prompted, which caused otherwise recoverable actions to fail or created inconsistent tool-loop behavior. Platform integrations also shared authentication headers too broadly and did not consistently bound or clean up network responses and partial downloads.

The compatibility path remains bounded and schema-driven: it accepts known real-world variants, but rejects ambiguous or unsafe output. Platform workflows continue to require explicit human confirmation and now isolate cross-origin credentials by default.

Impact

  • More reliable agent-to-agent and agent-to-tool interoperability across supported providers.
  • Safer platform preview/import/submit workflows with fewer partial-state failures.
  • No implicit API-token forwarding to a separate attachment CDN.
  • A reusable, validated workflow for connecting CTFd and custom CTF platform APIs.

Validation

  • python -m pytest -q: 138 passed, 166 skipped
  • Skill quick_validate.py: passed
  • Offline payload inspection and workflow validation scripts: passed with camelCase attachments and separate API/CDN secrets
  • python -m compileall: passed
  • git diff --check: passed

The skipped tests are existing environment-gated integration suites.

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