Crewai integration by staru09 · Pull Request #77 · usemoss/moss

staru09 · 2026-03-27T19:19:36Z

Pull Request Checklist

Please ensure that your PR meets the following requirements:

I have read the CONTRIBUTING guide.
I have updated the documentation (if applicable).
My code follows the style guidelines of this project.
I have performed a self-review of my own code.
I have added tests that prove my fix is effective or that my feature works.
New and existing unit tests pass locally with my changes.

Description

Add CrewAI integration for Moss semantic search.

Tested with Gemini (gemini-3.1-flash-lite-preview) as the LLM, using FAQ data from the existing examples.
All tools verified against the live Moss platform.

Fixes #76

Type of Change

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
This change requires a documentation update

vercel · 2026-03-27T19:19:40Z

@staru09 is attempting to deploy a commit to the Moss Team Team on Vercel.

A member of the Team first needs to authorize it.

HarshaNalluru · 2026-03-29T00:19:56Z

@@ -0,0 +1,40 @@
+from __future__ import annotations


Per #76, let's keep this cookbook-only - please drop packages/crewai-moss/

Copilot

Pull request overview

Adds a new crewai-moss integration package so CrewAI agents can use Moss for semantic search and basic index/document management, plus a cookbook example and top-level docs update to surface the integration.

Changes:

Introduces crewai-moss Python package with 8 CrewAI BaseTool wrappers and a moss_tools() factory.
Adds demo/cookbook example scripts and documentation for using CrewAI + Moss together.
Updates the repo root README to include the new CrewAI cookbook entry.

Reviewed changes

Copilot reviewed 11 out of 13 changed files in this pull request and generated 9 comments.

Show a summary per file

File	Description
packages/crewai-moss/tests/test.py	Adds live (credentialed) test script for the CrewAI tool wrappers.
packages/crewai-moss/tests/init.py	Initializes the tests package (empty).
packages/crewai-moss/src/crewai_moss/tools.py	Implements CrewAI `BaseTool` wrappers for Moss search, docs, and index operations.
packages/crewai-moss/src/crewai_moss/init.py	Exposes the tools and selected Moss SDK types from the package root.
packages/crewai-moss/pyproject.toml	Defines package metadata, dependencies, and ruff config for `crewai-moss`.
packages/crewai-moss/examples/demo.py	Provides an example CrewAI + Moss script using FAQ data.
packages/crewai-moss/README.md	Documents installation, available tools, and usage patterns.
packages/crewai-moss/LICENSE	Adds a license file for the new package.
packages/crewai-moss/.gitignore	Adds Python/package build ignores for the new package.
examples/cookbook/crewai/example_usage.py	Adds a cookbook example script demonstrating CrewAI + Moss.
examples/cookbook/crewai/README.md	Adds cookbook documentation for setup and running the CrewAI example.
README.md	Updates root docs to list the CrewAI cookbook integration and adjusts formatting.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-03-29T00:22:35Z

+    faqs_path = os.path.join(
+        os.path.dirname(__file__), "..", "..", "python", "faqs.json"
+    )


faqs_path resolves to packages/python/faqs.json from this file location, but the FAQ data lives at examples/python/faqs.json in this repo. As written, the demo will raise FileNotFoundError unless a different file layout exists. Update the path calculation to point at the repo’s examples/python/faqs.json (or accept a path via env/CLI to avoid brittle relative paths).

Suggested change

faqs_path = os.path.join(

os.path.dirname(__file__), "..", "..", "python", "faqs.json"

)

faqs_path = os.getenv("MOSS_FAQ_PATH")

if not faqs_path:

faqs_path = os.path.join(

os.path.dirname(__file__),

"..",

"..",

"..",

"examples",

"python",

"faqs.json",

)

Copilot · 2026-03-29T00:22:35Z

+    client = MossClient(os.getenv("MOSS_PROJECT_ID"), os.getenv("MOSS_PROJECT_KEY"))
+
+    faqs_path = os.path.join(
+        os.path.dirname(__file__), "..", "..", "python", "faqs.json"


faqs_path is computed by going up only two directories, which targets examples/cookbook/python/faqs.json. In this repo the file is examples/python/faqs.json, so the example will fail with FileNotFoundError. Adjust the relative path (or make it configurable) so it consistently finds examples/python/faqs.json.

Suggested change

os.path.dirname(__file__), "..", "..", "python", "faqs.json"

os.path.dirname(__file__), "..", "..", "..", "python", "faqs.json"

Copilot · 2026-03-29T00:22:35Z

+| [Next.js](https://nextjs.org) | Available | [`apps/next-js/`](apps/next-js/) |
+| [VitePress](https://vitepress.dev) | Available | [`packages/vitepress-plugin-moss/`](packages/vitepress-plugin-moss/) |
+| [Vercel AI SDK](https://sdk.vercel.ai) | Coming soon | — |
+| [CrewAI](https://github.com/crewAIInc/crewAI) | Coming soon | — |


The integration table lists CrewAI twice (one row says Available and another says Coming soon). This is contradictory and will confuse users; remove the outdated entry so CrewAI appears only once with the correct status.

Suggested change

| [CrewAI](https://github.com/crewAIInc/crewAI) | Coming soon | — |

Copilot · 2026-03-29T00:22:36Z

+python -m pytest tests/test_tools.py -v
+
+# Live platform tests (needs MOSS_PROJECT_ID & MOSS_PROJECT_KEY in .env)
+python tests/test_live.py


This package README instructs running tests/test_tools.py and tests/test_live.py, but neither file exists in this package (only tests/test.py is present). Update the README commands to match the actual filenames and/or rename the test files to match the documented commands.

Suggested change

python -m pytest tests/test_tools.py -v

# Live platform tests (needs MOSS_PROJECT_ID & MOSS_PROJECT_KEY in .env)

python tests/test_live.py

python -m pytest tests/test.py -v

# Live platform tests (needs MOSS_PROJECT_ID & MOSS_PROJECT_KEY in .env)

python tests/test.py

Copilot · 2026-03-29T00:22:36Z

+    _client: Any = None
+    _index_loaded: bool = False


_client and _index_loaded are declared as normal model fields. In this repo’s LangChain integration, these are marked as PrivateAttr to avoid leaking into the tool schema/serialization. Consider switching these to PrivateAttr here as well (and similarly for _client in the other tool classes in this file).

Copilot · 2026-03-29T00:22:36Z

+    project_id: str = Field(description="Moss project ID")
+    project_key: str = Field(description="Moss project key")
+    index_name: str = Field(description="Name of the Moss index")
+
+    _client: Any = None
+


_client is defined as a standard field; per existing integrations in this repo, internal clients are modeled as PrivateAttr so they don’t become part of the pydantic schema/tool args. Update _client in this class (and the other tool classes below) to use PrivateAttr.

Copilot · 2026-03-29T00:22:36Z

@@ -0,0 +1,26 @@
+BSD 2-Clause License
+
+Copyright (c) 2024–2025, Daily


The copyright holder in this LICENSE file is Daily, but pyproject.toml lists InferEdge Inc. as the author and the repo root license is Moss Team. Please confirm the intended copyright holder for this package and update the header to match, to avoid licensing ambiguity.

Suggested change

Copyright (c) 2024–2025, Daily

Copyright (c) 2024–2025, Moss Team

Copilot · 2026-03-29T00:22:36Z

+examples/.env
+__pycache__/
+*.pyc
+src/pipecat_moss.egg-info/


This .gitignore entry appears copy/pasted from pipecat-moss and ignores src/pipecat_moss.egg-info/. For this package it should ignore the egg-info directory for crewai_moss instead, otherwise local build artifacts won’t be ignored.

Suggested change

src/pipecat_moss.egg-info/

src/crewai_moss.egg-info/

Copilot · 2026-03-29T00:22:37Z

+async def run_tests():
+    if not PROJECT_ID or not PROJECT_KEY:
+        print("ERROR: MOSS_PROJECT_ID and MOSS_PROJECT_KEY must be set.")
+        sys.exit(1)
+
+    print("Running live tests against Moss platform...\n")


This file is a live/integration test that requires real Moss credentials, but it’s named generically (test.py) and sits under tests/. Consider renaming it to test_live.py (matching the README) and/or marking it clearly so it’s not mistaken for a unit test suite.

CLAassistant · 2026-03-29T08:05:27Z

All committers have signed the CLA.

yatharthk2 · 2026-03-30T16:49:22Z

Hi @staru09 , can you please properly resolve the comments from co-pilot ?

staru09 · 2026-03-30T16:53:14Z

Hi @staru09 , can you please properly resolve the comments from co-pilot ?

I think most of these were for the package that I had added, the recent changes has all these addressed

yatharthk2 · 2026-04-01T15:21:19Z

Can you please remove quick start and changes made to main read me ?

yatharthk2 · 2026-04-01T22:20:07Z

please add .env.example

yatharthk2 · 2026-04-01T18:40:33Z

+    """Create a Moss index with the first 10 FAQ documents."""
+    client = MossClient(os.getenv("MOSS_PROJECT_ID"), os.getenv("MOSS_PROJECT_KEY"))
+
+    faqs_path = os.path.join(


the directory has changed a lot, this path wont work

yatharthk2 · 2026-04-01T19:53:40Z

+    docs = [
+        DocumentInfo(
+            id=faq["id"],
+            text=faq["text"],


Simple FAQ.json example does not seem to be the best integration showcase between the Moss and Crew.

Please try adding more agents which handle multiple index from moss and they are inter collaborating to reach final conclusion.

umm, let me add a different usecase then

yatharthk2 · 2026-04-01T22:00:26Z

+            self._index_loaded = True
+
+    def _run(self, query: str) -> str:
+        """Synchronous search -- wraps the async implementation."""


why sync ? what is the use ?

The sync _run() is there because CrewAI's BaseTool marks it as abstractmethod, so I had to implement sync and async both for it.

yatharthk2 · 2026-04-01T22:01:23Z

+    index_name: str = Field(description="Name of the Moss index to search")
+    top_k: int = Field(default=5, description="Number of results to return")
+    alpha: float = Field(
+        default=0.5,


change to 0.8

yatharthk2 · 2026-04-01T22:04:23Z

+
+    def model_post_init(self, __context: Any) -> None:
+        """Initialize the MossClient after model construction."""
+        self._client = MossClient(self.project_id, self.project_key)


every class instantiates its own mossclient, this is too redundunt

yes, fixed this one

yatharthk2 · 2026-04-02T21:53:46Z

please let me know when this is ready to review

devin-ai-integration

Devin Review found 1 new potential issue.

View 5 additional findings in Devin Review.

devin-ai-integration · 2026-04-07T09:49:33Z

🚩 test_live.py is a credentials-required script, not a pytest-compatible test suite

Unlike the langchain cookbook which has test_integration.py using unittest.IsolatedAsyncioTestCase with mocked clients (no credentials needed), the crewai cookbook's test_live.py is a standalone script using global state (passed/failed counters) and sys.exit(1). It requires real API credentials and cannot run as part of pytest tests/. This means the tool logic in moss_crewai.py has no offline-runnable unit tests. The langchain example (examples/cookbook/langchain/test_integration.py) provides a better pattern to follow here — mocking MossClient to verify tool behavior without hitting the real API.

Was this helpful? React with 👍 or 👎 to provide feedback.

yatharthk2

Over all looks good, will approve after these fixes

yatharthk2 · 2026-04-08T22:20:16Z

+        crew = Crew(
+            agents=specialists + [writer],
+            tasks=search_tasks + [write_task],
+            verbose=True,


please do verbose=False,

yatharthk2 · 2026-04-08T22:21:07Z

+MOSS_PROJECT_ID=your-project-id
+MOSS_PROJECT_KEY=your-project-key
+GEMINI_API_KEY=your-gemini-key


Please add CREWAI_TRACING_ENABLED=false

yatharthk2 · 2026-04-08T22:31:46Z

+class MossListIndexesInput(BaseModel):
+    """Input schema for MossListIndexesTool."""
+
+    pass  # No input needed


can we remove ?

It's there to match the schema required by crewai for tools even if it doesn't need any params
We need it cause the BaseTool needs an args_schema and without this, it'll fallback to default and the code can break

yatharthk2 · 2026-04-08T22:42:05Z

@@ -0,0 +1,3 @@
+MOSS_PROJECT_ID=your-project-id


can you also please add pyproject.toml file

I dont see pyproject.toml

It got ignored by the git, please check now

yatharthk2 · 2026-04-10T17:20:26Z

+    "crewai",
+    "moss>=1.0.0",
+    "pydantic",
+    "python-dotenv",


can you please add "crewai[google-genai]"

Should we keep it vendor neutral add let user add any vendor uv add 'vendor_package' directly?

for your example to run there should be as less friction as possible

devin-ai-integration

Devin Review found 1 new potential issue.

View 9 additional findings in Devin Review.

devin-ai-integration · 2026-04-10T17:28:33Z

+from moss_crewai import (
+    MossAddDocsTool,
+    MossCreateIndexTool,
+    MossDeleteDocsTool,
+    MossDeleteIndexTool,
+    MossGetDocsTool,
+    MossListIndexesTool,
+    MossSearchTool,
+)


🟡 MossGetIndexTool has no test coverage in test_live.py

MossGetIndexTool is one of 8 tool classes defined in moss_crewai.py:187, documented in README.md:134, and returned by the moss_tools() factory at moss_crewai.py:313. However, test_live.py imports only 7 of the 8 tools (lines 8–16) and has no test scenario for MossGetIndexTool. Every other tool class has at least one test. This violates the CONTRIBUTING.md guideline: "If you've added code that should be tested, add tests." The existing langchain cookbook example (examples/cookbook/langchain/test_integration.py) demonstrates the expected practice of testing all added tool classes.

Prompt for agents

MossGetIndexTool is missing from test_live.py. It is one of 8 tool classes defined in moss_crewai.py, but the test file imports and tests only 7 of them. Add an import of MossGetIndexTool to the import block at lines 8-16 of test_live.py, and add a test section (e.g. between the list_indexes test and the add_docs test) that creates a MossGetIndexTool instance and calls _arun(index_name=TEST_INDEX), verifying the returned string contains the index name. Follow the same pattern as the other tests in the file (try/except with report() calls).

Was this helpful? React with 👍 or 👎 to provide feedback.

yatharthk2 · 2026-04-10T17:44:31Z

+version = "0.1.0"
+description = "CrewAI integration for Moss semantic search"
+readme = "README.md"
+requires-python = ">=3.11"


your dependency dont build for python 3.14 , please cap it here

yatharthk2 · 2026-04-10T17:51:01Z

Approved and Thanks for the PR :)

## Pull Request Checklist Please ensure that your PR meets the following requirements: - [x] I have read the [CONTRIBUTING](CONTRIBUTING.md) guide. - [x] I have updated the documentation (if applicable). - [x] My code follows the style guidelines of this project. - [x] I have performed a self-review of my own code. - [x] I have added tests that prove my fix is effective or that my feature works. - [x] New and existing unit tests pass locally with my changes. ## Description Add CrewAI integration for Moss semantic search. Tested with Gemini (gemini-3.1-flash-lite-preview) as the LLM, using FAQ data from the existing examples. All tools verified against the live Moss platform. Fixes usemoss#76 ## Type of Change - [ ] Bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] This change requires a documentation update  --- <a href="https://app.devin.ai/review/usemoss/moss/pull/77" target="_blank"> <picture> <source media="(prefers-color-scheme: dark)" srcset="https://static.devin.ai/assets/gh-open-in-devin-review-dark.svg?v=1"> <img src="https://static.devin.ai/assets/gh-open-in-devin-review-light.svg?v=1" alt="Open with Devin"> </picture> </a>

staru09 requested review from CoderOMaster, HarshaNalluru, r4ghu and yatharthk2 as code owners March 27, 2026 19:19

staru09 force-pushed the crewai_integration branch from 41a1d5c to 84d042a Compare March 28, 2026 04:39

HarshaNalluru requested a review from Copilot March 29, 2026 00:18

Copilot started reviewing on behalf of HarshaNalluru March 29, 2026 00:18 View session

HarshaNalluru reviewed Mar 29, 2026

View reviewed changes

Copilot AI reviewed Mar 29, 2026

View reviewed changes

staru09 force-pushed the crewai_integration branch from 84d042a to 0ec391f Compare March 29, 2026 15:02

yatharthk2 requested changes Apr 1, 2026

View reviewed changes

staru09 force-pushed the crewai_integration branch from f6dff4a to 622f75b Compare April 2, 2026 05:57

staru09 force-pushed the crewai_integration branch from a06995e to 0f49947 Compare April 5, 2026 06:29

staru09 requested a review from yatharthk2 April 5, 2026 06:33

This comment was marked as resolved.

Sign in to view

devin-ai-integration Bot reviewed Apr 7, 2026

View reviewed changes

This comment was marked as resolved.

Sign in to view

staru09 force-pushed the crewai_integration branch from 7265b3f to 3d517ba Compare April 8, 2026 08:18

This comment was marked as resolved.

Sign in to view

yatharthk2 requested changes Apr 8, 2026

View reviewed changes

staru09 added 2 commits April 9, 2026 14:13

added crewai_integration

1c45cae

added example agents

49d083c

updated for linters

023cb98

staru09 force-pushed the crewai_integration branch from 3d517ba to 21cecc1 Compare April 9, 2026 09:02

This comment was marked as resolved.

Sign in to view

staru09 force-pushed the crewai_integration branch from 21cecc1 to 67bca81 Compare April 9, 2026 09:15

This comment was marked as resolved.

Sign in to view

staru09 requested a review from yatharthk2 April 9, 2026 09:35

This comment was marked as resolved.

Sign in to view

staru09 added 2 commits April 10, 2026 22:49

add pyproject.toml file

0129c79

fixed readme

3a8accb

yatharthk2 reviewed Apr 10, 2026

View reviewed changes

staru09 force-pushed the crewai_integration branch from 178947d to 7111f96 Compare April 10, 2026 17:21

devin-ai-integration Bot reviewed Apr 10, 2026

View reviewed changes

yatharthk2 reviewed Apr 10, 2026

View reviewed changes

add pyproject file

d41edc2

staru09 force-pushed the crewai_integration branch from 6e4c9f8 to d41edc2 Compare April 10, 2026 17:49

yatharthk2 approved these changes Apr 10, 2026

View reviewed changes

yatharthk2 merged commit 8cfa9da into usemoss:main Apr 10, 2026
12 of 14 checks passed

	os.path.dirname(__file__), "..", "..", "python", "faqs.json"
	os.path.dirname(__file__), "..", "..", "..", "python", "faqs.json"

		@@ -0,0 +1,26 @@
		BSD 2-Clause License

		Copyright (c) 2024–2025, Daily

	Copyright (c) 2024–2025, Daily
	Copyright (c) 2024–2025, Moss Team

Conversation

staru09 commented Mar 27, 2026 • edited by devin-ai-integration Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Pull Request Checklist

Description

Type of Change

Uh oh!

vercel Bot commented Mar 27, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Mar 29, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 29, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 29, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 29, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 29, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 29, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 29, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 29, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 29, 2026

Choose a reason for hiding this comment

Uh oh!

CLAassistant commented Mar 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

yatharthk2 commented Mar 30, 2026

Uh oh!

staru09 commented Mar 30, 2026

Uh oh!

yatharthk2 commented Apr 1, 2026

Uh oh!

yatharthk2 commented Apr 1, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

yatharthk2 commented Apr 2, 2026

Uh oh!

This comment was marked as resolved.

Uh oh!

devin-ai-integration Bot left a comment

Choose a reason for hiding this comment

staru09 commented Mar 27, 2026 •

edited by devin-ai-integration Bot

Loading

CLAassistant commented Mar 29, 2026 •

edited

Loading