feat: Return task input verbatim and align task tools with the API - #1293
Open
jirispilka wants to merge 1 commit into
Open
feat: Return task input verbatim and align task tools with the API#1293jirispilka wants to merge 1 commit into
jirispilka wants to merge 1 commit into
Conversation
Return the stored task input under the API's `input` key, matching API, CLI, and apify-client. The platform encrypts input-schema fields declared isSecret server-side on save, so reads only ever see ENCRYPTED_VALUE placeholders (verified empirically); non-secret values are the token owner's own data and are already returned on every other Apify surface. Document the full publish requirements (including seoDescription), declare the SEO title/description length limits (60/160) in the publicConfig schema, steer agents to resolve loose Actor references with search-actors instead of asking, and align descriptions with Apify docs vocabulary and style. Tool errors now append the machine-readable Apify API error type, e.g. "(API error type: actor-task-name-not-unique)", so callers can branch on the exact error instead of parsing messages.
github-actions
Bot
added
t-ai
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Task tools now return the stored task
inputverbatim, under the same key the API, CLI, and apify-client use. Everything in this PR came out of the task-tool workflow evals (#1294): agents could not answer "what input is my task configured with?", could not verify their own updates, and hallucinated values from the field-name list.Not obvious from the code:
isSecret: trueserver-side on save. Verified empirically: a task created via the raw API with a plaintext secret returnsENCRYPTED_VALUE:...from bothGET actor-taskandGET actor-task/input; the plaintext never comes back. Non-secret values are already returned by every other Apify surface.seoDescriptionis required to publish, which no docs state — discovered via API probing after eval agents got stuck. Descriptions now list the full requirements, and the schema declares the SEO length limits (60/160) the API enforces.structuredContentreplacesinputFields(names only) withinput.(API error type: actor-task-name-not-unique).