11 Commits

Author	SHA1	Message	Date
chenshiyang	265697b6f8	docs: refresh retired Gemini model ids (#7003) ... Co-authored-by: Vidit Ostwal <110953813+Vidit-Ostwal@users.noreply.github.com>	2026-08-31 10:43:31 -03:00
João Moura	9652af6ae0	fix(agents): keep message roles when Agent.kickoff gets a conversation (#7065) ... * fix(agents): keep message roles when Agent.kickoff gets a conversation `Agent.kickoff` accepts `str | list[LLMMessage]`, but `_prepare_kickoff` joined every message's content into one string. Measured with a recording LLM, a three-turn conversation reached the provider as two messages: system | You are Support... user | Current Task: my order id is 42\nthanks, checking\nwhere is it? So the agent's own previous reply was presented as something the user said, and the model could not tell who said what. `LiteAgent.kickoff` already did this correctly, which is why the same list gave four messages with roles intact there. The last message is now this turn's request and the ones before it travel as `inputs["history"]` -- the way `inputs["files"]` already does -- which both executors splice in after the system prompt and before the user prompt. Memory recall still runs over the whole conversation text, not just the last turn. A plain string and a single-message list are byte-identical to before, which is what every existing caller passes. Also widens `LiteAgentExecutionStartedEvent.messages` from `list[dict[str, str]]` to `list[LLMMessage]`: it raised a ValidationError for a message whose content was `None` or a content-part list, both of which are valid `LLMMessage` shapes that `Agent.kickoff` already accepts. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * fix(agents): carry history without a system prompt, tool calls, or dup files Three review findings on the message-role work, all real. History was spliced only in the branch that builds a system prompt. With `use_system_prompt=False` or a custom template there is one combined prompt, so history went nowhere and only the last turn reached the model -- worse than the flattening this PR replaced, which at least included the text. Both executors now splice in either branch, via one `_append_history` helper each. Filtering on truthy content dropped an assistant turn that only requests tool calls, leaving a `tool` message with no preceding `tool_calls` message -- a sequence providers reject. A message now counts when it has content, tool calls, or a tool_call_id. And `files` were unioned from every message onto the current request while history messages kept their own, so prior attachments were sent twice. Only the current request's attachments travel in `inputs["files"]` now. Found by Cursor and CodeRabbit on #7065. * fix(agents): treat an attachment as message payload _carries_payload counted text, tool calls and tool results, but not files. A final message whose only payload was an attachment was filtered out, so the previous message became this turn request and the attachment never reached inputs["files"]. Found independently by Cursor and CodeRabbit on #7065. * fix(agents): promote the last user message, not the last message build_agent_context() appends an agent private thread after the current user turn, so on a later turn the trailing message is an assistant scratch. That scratch became Current Task while the real question was demoted to history -- reproduced: the request came back as "internal note: checked warehouse". The request is now the last user message, with everything else kept as history in order; with no user message the last one stands in, which is what a single-message caller has always got. Documented on kickoff and kickoff_async. The old cross-check against LiteAgent only compared roles on a fixture already ending in a user message, so it could not catch this. It now asserts what holds for both -- nothing dropped, nothing duplicated -- since Agent has a task slot in its prompt and LiteAgent does not. Reported by Vidit-Ostwal on #7065. * test(agents): cover history placement on the deprecated executor too `CrewAgentExecutor` carries its own `_setup_messages`, and `Agent.kickoff` builds an `AgentExecutor` unconditionally, so nothing reached the twin's two `_append_history` sites. This drives that executor directly with the real `SystemPromptResult` / `StandardPromptResult` shapes, so both its branches are pinned. Verified by mutation: removing either `_append_history` call in either executor now fails the matching test. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VwxiogL9mQg9q8cx4qLfYJ * fix(agents): keep turns that follow the request after it `_prepare_kickoff` packed every non-request message into one `history` list, and both executors spliced that list before the current user prompt. A conversation ending on a tool result therefore reached the provider as `assistant tool_calls -> tool -> user`, hoisting the tool pair above the question it answers. `LiteAgent` sends the same list as `user -> assistant -> tool`. Splits the carried messages at the request instead: what came before stays `history`, what came after travels as `trailing` and is appended after the user prompt. Promoting the last user message to `{input}` is unchanged. `test_a_tool_call_sequence_survives` missed this because it ends on a follow-up user line, so the tool pair was already before the request. Reported by lorenzejay, who also confirmed gpt-4o-mini and gpt-5.6-sol accept the reordered payload -- an order bug, not a provider 400. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VwxiogL9mQg9q8cx4qLfYJ * test(agents): assert the ordering through kickoff_async too `kickoff_async` shares `_prepare_kickoff`, and the async executor entry points reach the same `_setup_messages`, but sharing a code path is not the same as covering it. Pins the tool-result ordering through the async path, and lifts the tool conversation to a module-level fixture so the sync and async assertions cannot drift. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VwxiogL9mQg9q8cx4qLfYJ * docs(agents): state where a kickoff conversation's turns land `concepts/agents.mdx` documents the multi-message form but not which message becomes the request or what happens to the turns around it -- the contract this branch changed. Corrects the `kickoff` / `kickoff_async` docstrings to match. en and ko only: the ar and pt-BR pages do not carry the "Multiple Messages" section at all, which is a pre-existing translation gap rather than one this change introduces. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VwxiogL9mQg9q8cx4qLfYJ * feat(flow): let a declarative agent action receive the conversation (#7066) * feat(flow): let a declarative agent action receive the conversation A chat handler could only hand its agent a single string, so a declarative conversational flow's `agent` action never saw prior turns. Both ends blocked it: `AgentDefinition.input` was `str` with a validator rejecting anything else, and `AgentAction.run` raised "agent input must render to a string" once a CEL template rendered to a list. `input` now takes a string or a list of messages, and the action normalizes rather than rejecting. A whole-string `${...}` template keeps its evaluated type, so `state.messages.map(m, {'role': m.role, 'content': m.content})` renders the exact shape the agent wants -- no new CEL function needed. Serialized messages carry `name: None` and `metadata` that the agent event schema rejects, and `message_to_llm_dict` only drops `None` for a model input, not the plain dicts a CEL render produces. The normalizer drops them, keeping `content: None` since that is a valid message shape. Declarative crews are unaffected: they use `CrewAgentDefinition`, which has no `input` field at all. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * test(flows): pin content=None survival through agent input normalization A filter-all-None change would silently drop the assistant turn that only requests tool calls, and no test covered that key. Found by CodeRabbit on #7066. * test(flows): cover the agent action through kickoff, not the helper The existing tests called _normalize_agent_input directly, so nothing pinned that Expression.render_template -> normalization -> Agent.kickoff_async keeps a message list intact. Removing the normalization call now fails this test. Found by CodeRabbit on #7066. --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com> Co-authored-by: Lorenze Jay <63378463+lorenzejay@users.noreply.github.com>	2026-08-24 21:09:36 +00:00
Lorenze Jay	6c19669d63	refactor: update date injection functionality in agents (#6850) ... * refactor: update date injection functionality in agents - Changed the description of the parameter to clarify that it injects the current date into the agent's prompt instead of tasks. - Removed the method as it was no longer needed. - Implemented a new method in the class to handle date injection directly into the prompt. - Updated tests to ensure the date is correctly injected into the system prompt and user messages based on the flag. * translations * nit	2026-08-11 14:36:47 -03:00
Vidit Ostwal	11890e6701	Standardize CLI flags to kebab-case (#6880) ... * Standardize CLI flags to kebab-case with deprecated snake_case aliases. Unify active long-option naming across create, train, test, and replay while keeping hidden backward-compatible aliases and documenting the migration in edge docs and AGENTS.md. * Emit deprecation warnings when snake_case CLI flag aliases are used. Route hidden legacy flags through separate internal params so warnings fire only when the alias is supplied, and extend CLI tests for create, replay, and --help coverage. * Merge CLI deprecation warn helpers into warn_deprecated(kind=...). Replace warn_deprecated_command and warn_deprecated_flag with one helper that accepts kind="command" or kind="flag".	2026-08-11 22:17:24 +05:30
Vidit Ostwal	988f060c93	Fix Anthropic cache token usage underreporting (#6844) ... * Fix Anthropic native provider to include cache tokens in input totals. Anthropic reports cache read and cache creation separately from input_tokens; fold them into input_tokens and total_tokens so billed usage is not underreported on cached workloads. * Reconcile unreconciled Anthropic cache tokens in UsageMetrics. LiteLLM and flow event paths can pass raw Anthropic usage where input_tokens excludes cache counters; fold them into prompt and total tokens without double-counting native provider payloads. Co-authored-by: Cursor <cursoragent@cursor.com> * Document UsageMetrics token field semantics for flows and crews. Clarify that total_tokens is prompt plus completion, breakdown fields are not additive, and Anthropic cache counters are folded into prompt_tokens. Co-authored-by: Cursor <cursoragent@cursor.com> * Document Anthropic cache token accounting in LLM provider docs. Explain how split Anthropic input counters map to UsageMetrics and link to the flows field semantics section. Co-authored-by: Cursor <cursoragent@cursor.com> * Restore cache_creation_tokens breakdown in UsageMetrics normalization. Keep cache writes as a separate breakdown field while they remain folded into prompt_tokens for billed totals. * Replace cross-page doc links with plain-text section references. Avoid internal hyperlinks between concept pages for SEO; point readers to section names in prose instead. * Apply ruff formatting to usage metrics helpers. * Sync ar, ko, and pt-BR docs for Anthropic usage metrics updates. Translate UsageMetrics semantics and Anthropic cache token accounting changes in crews, flows, and llms concept pages. --------- Co-authored-by: Cursor <cursoragent@cursor.com>	2026-08-07 17:07:02 +05:30
Gui Vieira	3266932f00	[COR-636] Remove migrated AMP documentation (#6730)	2026-07-30 13:14:34 -03:00
Lucas Gomide	d52d0a1628	feat: emit FlowFailedEvent when a flow execution fails (#6718) ... * feat: emit FlowFailedEvent when a flow execution fails A failed flow never emitted a terminal lifecycle event, so the `flow_started` scope stayed open and consumers such as tracing closed the root span with a generic orphaned message instead of the real error. `kickoff_async` and the resume path now emit `FlowFailedEvent`, paired with `flow_started` and carrying the exception, after draining pending handlers and background memory writes. The resume path also emits the `MethodExecutionStartedEvent` it was missing for the method being resumed, so its finished or failed event pairs with its own scope instead of popping the flow's. * fix: skip FlowFailedEvent when the run never opened a scope The `kickoff_async` try block starts before `FlowStartedEvent` is emitted, so an abort in the execution-start hooks, in input handling or in state restore emitted a `flow_failed` with no opener, which pops an unrelated scope and warns about an empty scope stack. The failure event is now gated on the flow scope actually being open, either from this kickoff's `flow_started` or from a restored deferred session scope.	2026-07-29 14:44:55 -04:00
Ossama Alami	daa7019898	docs(llms): refresh model availability guidance (#6676) ... * docs(llms): refresh model availability guidance * docs: clarify structured output support * docs: address LLM guide review feedback * docs: refresh streaming model examples	2026-07-26 16:13:36 -07:00
João Moura	f0704ebb22	feat(skills)!: promote Skills Repository out of experimental (#6579) ... * feat(skills)!: promote Skills Repository out of experimental The registry-backed Skills Repository (crewai skill create/publish/ install/list, @org/name refs, global cache) is now mainline: - CLI: `crewai skill ...` is a top-level group; the CREWAI_EXPERIMENTAL gate and the now-empty `crewai experimental` group are removed. - Runtime: registry.py, cache.py, and events.py move from crewai.experimental.skills into crewai.skills next to the loader; the require_experimental_skills() gate is gone. crewai.experimental.skills remains as a deprecated re-export shim. - Docs: concepts/skills now leads with the CLI workflow and documents the create -> publish -> install lifecycle. Linear: n/a (requested promotion) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * feat(skills): org-scoped publish only + docs in all languages Skills are always scoped to the publishing organization, like tools: drop the --public/--private flags from `crewai skill publish` and always send is_public=False to the registry. CLI tests assert the flag is rejected and the API never receives a public publish. Translate the new CLI-first Quick Start and the create -> publish -> install lifecycle section into ar, pt-BR, and ko concepts/skills docs. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * fix(skills): address review comments on the promotion PR - Back-compat shim now aliases the old submodules in sys.modules so `crewai.experimental.skills.registry/cache/events` imports (and patch targets) resolve to the real crewai.skills modules, not just the package-root re-exports. - `crewai skill publish` actually enforces the git-state check that --force claims to skip: unsynced repos block publishing (mirroring tool publish); standalone skill dirs outside any git repo publish without a check. - Explicit UTF-8 encoding on SKILL.md and cache-metadata reads/writes. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * fix(skills): fail closed when git state cannot be validated on publish Follow deploy's pattern: construct git.Repository(fetch=False) and only treat "not a Git repository" as skippable — any other git error (fetch/auth/misconfiguration) now blocks publish with a --force escape hatch instead of silently bypassing the sync check. Also single-style imports in the shim test (CodeQL) with the dotted shim import covered via importlib. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * fix(skills): fetch before sync check on publish; bump mcp past advisories Publish now refreshes remote-tracking refs (repository.fetch()) before is_synced(), so ahead/behind is judged against the actual remote rather than stale local refs; a failing fetch blocks publish with the --force escape hatch. Adds a fail-closed test for fetch errors. Raise mcp to >=1.28.1,<2 (locks 1.28.1): the ~=1.26.0 pin blocked GHSA-hvrp-rf83-w775 / GHSA-jpw9-pfvf-9f58 (fixed 1.27.2) and GHSA-vj7q-gjh5-988w (fixed 1.28.1), which were failing pip-audit on this PR. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com> Co-authored-by: Vinicius Brasil <vini@hey.com>	2026-07-17 14:21:15 +00:00
Vinicius Brasil	221dfdb08e	Consolidate crewai run and crewai flow kickoff (#6296) ... Make `crewai run` the single execution path for crews and flows, with `crewai flow kickoff` kept as a deprecated compatibility alias.	2026-06-22 20:44:08 -07:00
Lucas Gomide	a237ebabba	feat: adopt directory-based docs versioning with Edge channel (#6202) ... * feat: adopt directory-based docs versioning with Edge channel Switch docs.crewai.com from navigation-only versioning (every version selector entry rendered the same docs/<lang>/* source files) to Mintlify's directory-based versioning so each version selector entry renders its own snapshot. Add an "Edge" channel under docs/edge/<lang>/* that always reflects main HEAD for unreleased work, eliminating pre-release leakage onto frozen release labels. External links to canonical /<lang>/* URLs are preserved via wildcard redirects that always land on the current default version. Layout: - docs/edge/<lang>/* rolling source (you edit here) - docs/edge/enterprise-api.*.yaml - docs/v<X.Y.Z>/<lang>/* frozen, immutable snapshots - docs/v<X.Y.Z>/enterprise-api.*.yaml - docs/images/ shared, append-only - docs/docs.json nav + redirects URLs follow the Mintlify-idiomatic shape: /edge/<lang>/<page> for Edge, /v<X.Y.Z>/<lang>/<page> for every frozen snapshot. The wildcard redirects /<lang>/:slug* -> /<default>/<lang>/:slug* keep stale links working, and every freeze rewrites them (plus all per-section/per-page redirects) so destinations always resolve to the current default without depending on a second redirect hop. Release flow integration (devtools release): - New module crewai_devtools.docs_versioning.freeze() materialises docs/v<X.Y.Z>/ from docs/edge/, rewrites openapi: refs inside the snapshot, inserts the version into every language block in docs.json, and refreshes all redirect destinations. - _update_docs_and_create_pr() in cli.py now calls that freeze during Phase 2 of devtools release. Edge changelogs are updated first (so the snapshot freeze picks them up), then the snapshot is staged alongside docs.json, branched as docs/freeze-v<X.Y.Z>, and the PR is titled [docs-freeze] docs: snapshot and changelog for v<X.Y.Z> — the title prefix the new CI guard reads. - The PR still gates tag, GitHub release, PyPI publish, and the enterprise release as before; no new PRs are added. - Pre-releases (1.X.YaN, 1.X.YbN, ...) skip the snapshot — they ride Edge — and the docs PR title omits the [docs-freeze] prefix. - docs_check (AI-generated docs scaffolding) writes to docs/edge/<lang>/* so newly-generated unreleased docs land in Edge and never accidentally touch a frozen snapshot. Migration scripts (one-shot): - scripts/docs/freeze_historical_versions.py reconstructs all 16 historical snapshots (v1.10.0 .. v1.14.7) from git tags via git archive | tar, rewriting openapi: MDX refs so each snapshot reads its own enterprise-api YAML rather than the live one. - scripts/docs/prefix_version_paths.py one-shot-migrates docs.json: rewrites every page path in 16 versioned blocks to point under docs/v<X.Y.Z>/, inserts a new Edge entry per language, tags v1.14.7 as Latest (default), prunes pages whose target file doesn't exist in the snapshot (e.g. docs/ar/ didn't exist before v1.12.0), and writes the wildcard + per-section redirects. - scripts/docs/freeze_current_edge.py is now a thin CLI wrapper around docs_versioning.freeze for manual one-off freezes (e.g. retroactively snapshotting a forgotten release). CI guards (.github/workflows/docs-snapshots.yml): - Frozen snapshots under docs/v[0-9]*/ are immutable; only PRs whose title contains [docs-freeze] (i.e. release-cut PRs generated by devtools release or the manual wrapper) may modify them. - Images under docs/images/ are append-only since snapshots share a single image directory. Deleting or renaming an image breaks every historical snapshot that still references it. Restored docs/images/crewai-otel-export.png from PR #3673; it was deleted in PR #4908 but v1.10.0 / v1.10.1 snapshots still reference it. Restoring instead of editing the snapshots preserves historical rendering fidelity and validates the new append-only rule retroactively. Tests: - lib/devtools/tests/test_docs_versioning.py covers the freeze: file copy, openapi rewrite, version insertion, default demotion, redirect upserts, per-section redirect rewriting, idempotency, and invalid inputs. Verified locally with mintlify broken-links: 0 broken links across the full site (Edge + 16 frozen versions, 4 locales). AGENTS.md (repo root) is the contributor guide for the new model; RELEASING.md is the release-cut runbook; README's Contribution section links to both. Co-authored-by: Cursor <cursoragent@cursor.com> * style: resolve linter issues --------- Co-authored-by: Cursor <cursoragent@cursor.com>	2026-06-17 11:56:59 -04:00