Repository navigation
[pull] main from firecrawl:main - #88
Merged
Merged
Conversation
The agent service now only calls Alexandria providers whose data terms the
team has accepted, and reports the rest. Let MCP callers choose what
happens ("skip", "ask" or "fail"), forwarded as exchange.onTermsRequired.
Describe exchange.skippedProviders and exchange.requiresAction in the tool
description, and tell calling agents they must get the user's explicit
consent before calling terms/accept. Keep exchange, pendingApproval and
message in firecrawl_agent_status structured content so Codex-style
clients that read structuredContent do not lose them.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Matches the extract-v3#182 scope cut: onTermsRequired is skip or ask, and exchange.error is gone. Describe each requiresAction provider digest as string | null and always present. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…r sends Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ecrawl_agent
firecrawl_agent now takes threadId, mode and an exchange object that mirrors
the gateway's agentExchangeSchema (enabled, toolkits, maxCalls,
requireApproval, approve, decline, onTermsRequired). After an ask-mode terms
offer and the user's explicit consent to terms/accept, a caller continues the
same thread with exchange.approve: {approvalId} (or decline) instead of
starting over.
MCP-side guards: approve/decline need threadId, cannot be sent together, and
the top-level onTermsRequired cannot disagree with exchange.onTermsRequired.
Status structured content also keeps suggestions.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Drop the top-level onTermsRequired shorthand and its merge logic; callers set exchange.onTermsRequired, exactly as the gateway's agentExchangeSchema defines it. Nothing has been released with the shorthand. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- On a follow-up, send `urls: []` and `schema: null` (or `{}`) so they clear
what the thread inherits. POST /v2/agent directly because the SDK's
startAgent drops a null schema; errors are reported the same way.
- `exchange.toolkits` takes at most 5 slugs, the agent service's limit.
- `exchange.requireApproval` needs `mode: "chat"` on the same request: the
agent service checks the request's mode, not the inherited one, and the
gateway turns its 400 into a 500.
- README lists effort, maxCredits (API default 2,500) and
strictConstrainToURLs; the description-length test uses
CLAUDE_CODE_TEXT_CAP.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…clears The SDK drops a null schema, so clearing inherited urls/schema can't go through it. Keep today's behaviour: empty or null values are dropped and the thread's values are inherited. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Move the exchange options, approve/decline checks, terms-flow text and the pendingApproval/exchange status fields to a stacked PR. This PR keeps threadId and mode on firecrawl_agent (forwarded through the SDK), message and suggestions in the status output, the README arguments for effort, maxCredits and strictConstrainToURLs, and the CLAUDE_CODE_TEXT_CAP test fix. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
feat(agent): continue a thread from firecrawl_agent
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )