Skip to content

Conversation

parteeksingh24
Copy link
Contributor

@parteeksingh24 parteeksingh24 commented Jul 29, 2025

  • Create new "Guides"/tutorial pages (e.g., DevMode, agent logging)
  • Update storage API screenshots to include added object storage option
  • Add screenshot for creating a new object storage bucket
  • Fix internal link from "Agent Data Handling" to "Agent Streaming"

Summary by CodeRabbit

  • New Features
    • Added comprehensive documentation guides for Agent Logging, Agent Telemetry, Agent Tracing, AI Gateway, Agent DevMode, Key Value storage, Object Storage, and Vector DB, including best practices, code examples, and monitoring instructions.
    • Introduced a new Cloud Console documentation page for Object Storage management.
  • Documentation
    • Improved instructions for creating Key Value and Vector Database instances via the Cloud Console.
    • Updated and clarified various guide links and navigation entries.
  • Chores
    • Removed obsolete metadata files for deprecated guides.

- Create new "Guides"/tutorial pages (e.g., DevMode, agent logging)
- Update storage API screenshots to include added object storage option
- Add screenshot for creating a new object storage bucket
- Fix internal link from "Agent Data Handling" to "Agent Streaming"
Copy link
Contributor

coderabbitai bot commented Jul 29, 2025

Walkthrough

This update introduces several new and revised documentation guides for cloud storage and agent observability features. It adds comprehensive guides for object storage, key-value storage, vector DB, agent logging, telemetry, tracing, AI Gateway, and DevMode. Some outdated metadata files are deleted, and meta.json files are updated to reflect the new documentation structure.

Changes

Cohort / File(s) Change Summary
Cloud Storage Documentation Updates
content/Cloud/object-storage.mdx, content/Cloud/key-value-memory.mdx, content/Cloud/vector-memory.mdx
Added a new object storage documentation page; expanded and clarified instructions for creating key-value and vector storage instances via the Cloud Console.
Cloud Meta Configuration
content/Cloud/meta.json
Inserted "object-storage" into the Cloud documentation navigation.
Guides: New Comprehensive Documentation
content/Guides/agent-logging.mdx, content/Guides/agent-telemetry.mdx, content/Guides/agent-tracing.mdx, content/Guides/ai-gateway.mdx, content/Guides/devmode.mdx, content/Guides/key-value.mdx, content/Guides/object-storage.mdx, content/Guides/vector-db.mdx
Added new, detailed guides covering agent logging, telemetry, tracing, AI Gateway, DevMode, key-value storage, object storage, and vector DB usage with code examples and best practices.
Guides: Metadata Cleanup
content/Guides/.agent-logging.mdx, content/Guides/.agent-telemetry.mdx, content/Guides/.agent-tracing.mdx, content/Guides/.ai-gateway.mdx, content/Guides/.devmode.mdx, content/Guides/.key-value.mdx, content/Guides/.vector-db.mdx
Deleted obsolete metadata files for guides, removing unused frontmatter and descriptions.
Guides: Meta Navigation Update
content/Guides/meta.json
Updated the guides navigation to include new entries for DevMode, agent logging, agent telemetry, and object storage.
Guides: Minor Link Correction
content/Guides/agent-data-handling.mdx
Fixed the case of a hyperlink path to the streaming guide.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant CloudConsole
    participant SDK
    participant StorageService

    User->>CloudConsole: Click "Create Storage"
    CloudConsole->>User: Show storage type options
    User->>CloudConsole: Select "Key Value Store" or "Vector Database" or "Object Storage"
    CloudConsole->>StorageService: Create storage instance (selected type)
    StorageService-->>CloudConsole: Confirm creation
    CloudConsole-->>User: Show new storage instance

    User->>SDK: Use storage API (get/set/put/search)
    SDK->>StorageService: Perform storage operation
    StorageService-->>SDK: Return result
    SDK-->>User: Provide operation outcome
Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~15 minutes

Suggested reviewers

  • jhaynie

Poem

🐰
New guides bloom in the docs today,
Storage and logging lead the way.
Clouds and agents, side by side,
With tracing, keys, and buckets wide.
Out with the old, in with the new—
A garden of knowledge, fresh with dew!
🌱✨

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch parteek/add-guides-documentation

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@coderabbitai coderabbitai bot requested a review from jhaynie July 29, 2025 16:16
Copy link

cloudflare-workers-and-pages bot commented Jul 29, 2025

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
docs 6f63dd8 Commit Preview URL

Branch Preview URL
Jul 29 2025, 06:00 PM

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 8

🧹 Nitpick comments (11)
content/Cloud/vector-memory.mdx (1)

40-41: UI label wording – please confirm.

The instruction now tells users to choose “Vector Database” after clicking Create Storage. In the UI mock-ups the option is often labelled “Vector DB”. Ensure the wording matches the actual button label to avoid user confusion.

content/Cloud/key-value-memory.mdx (1)

41-42: Consistency with UI text.

Similarly, confirm the console option is literally “Key Value Store” in production; if it’s “Key-Value Store” or “Key Value”, a mismatch will mislead readers.

content/Cloud/object-storage.mdx (2)

21-26: Clarify units for “Size” column

“Size” alone is ambiguous (bytes? MB? GiB?). Explicitly stating the unit—e.g., “Size (bytes)” or “Size (GiB)”—pre-empts confusion.


27-30: Consider an accessibility-first alt text

Both images have generic alt text. Including purpose-driven descriptions (“Screenshot of Object Store table displaying bucket list”) improves screen-reader experience.

content/Guides/agent-tracing.mdx (1)

162-169: Timestamp attribute: prefer OT semantic conventions

Instead of a custom timestamp attribute, rely on add_event()’s built-in timestamp argument or use the time_unix_nano property for better tooling compatibility.

content/Guides/agent-logging.mdx (1)

150-153: Typo in example—missing variable

error is passed but not defined in the snippet. Either rename to e (from catch block) or declare it for consistency.

content/Guides/devmode.mdx (1)

8-8: “Exact same” is wordy

Replace with “identical” or simply “the same” for conciseness.

content/Guides/ai-gateway.mdx (1)

30-38: Show explicit error handling

Including a minimal try/except with logging demonstrates recommended production practice, aligning with the logging & tracing guides referenced elsewhere.

content/Guides/vector-db.mdx (1)

146-151: Nit: bullet list parameters out of sync with code

The code shows similarity, limit, and metadata, but the list omits topK (if supported) and the order differs. Keep docs & code aligned for scan-reading.

content/Guides/key-value.mdx (1)

174-181: Hyphenate compound adjective

Rate limiting countersRate-limiting counters for correct compound-adjective usage.

content/Guides/object-storage.mdx (1)

274-277: Clarify permanent-URL guidance

Never: Create permanent public URLs for sensitive data” could be misread as advice to create them. Reword for clarity.

-**Never**: Create permanent public URLs for sensitive data
+**Avoid permanent public URLs** for sensitive data
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d55ae64 and 712d4fd.

⛔ Files ignored due to path filters (18)
  • public/images/agent-logs-filter-dark.png is excluded by !**/*.png
  • public/images/agent-logs-filter-light.png is excluded by !**/*.png
  • public/images/aigateway-filters-dark.png is excluded by !**/*.png
  • public/images/aigateway-filters-light.png is excluded by !**/*.png
  • public/images/devmode-interface-dark.png is excluded by !**/*.png
  • public/images/devmode-interface-light.png is excluded by !**/*.png
  • public/images/devmode-logs-dark.png is excluded by !**/*.png
  • public/images/devmode-logs-light.png is excluded by !**/*.png
  • public/images/devmode-sessions-dark.png is excluded by !**/*.png
  • public/images/devmode-sessions-light.png is excluded by !**/*.png
  • public/images/keyvalue-new-dark.png is excluded by !**/*.png
  • public/images/keyvalue-new-light.png is excluded by !**/*.png
  • public/images/object-store-dark.png is excluded by !**/*.png
  • public/images/object-store-light.png is excluded by !**/*.png
  • public/images/object-store-new-dark.png is excluded by !**/*.png
  • public/images/object-store-new-light.png is excluded by !**/*.png
  • public/images/vector-new-dark.png is excluded by !**/*.png
  • public/images/vector-new-light.png is excluded by !**/*.png
📒 Files selected for processing (21)
  • content/Cloud/key-value-memory.mdx (1 hunks)
  • content/Cloud/meta.json (1 hunks)
  • content/Cloud/object-storage.mdx (1 hunks)
  • content/Cloud/vector-memory.mdx (1 hunks)
  • content/Guides/.agent-logging.mdx (0 hunks)
  • content/Guides/.agent-telemetry.mdx (0 hunks)
  • content/Guides/.agent-tracing.mdx (0 hunks)
  • content/Guides/.ai-gateway.mdx (0 hunks)
  • content/Guides/.devmode.mdx (0 hunks)
  • content/Guides/.key-value.mdx (0 hunks)
  • content/Guides/.vector-db.mdx (0 hunks)
  • content/Guides/agent-data-handling.mdx (1 hunks)
  • content/Guides/agent-logging.mdx (1 hunks)
  • content/Guides/agent-telemetry.mdx (1 hunks)
  • content/Guides/agent-tracing.mdx (1 hunks)
  • content/Guides/ai-gateway.mdx (1 hunks)
  • content/Guides/devmode.mdx (1 hunks)
  • content/Guides/key-value.mdx (1 hunks)
  • content/Guides/meta.json (1 hunks)
  • content/Guides/object-storage.mdx (1 hunks)
  • content/Guides/vector-db.mdx (1 hunks)
💤 Files with no reviewable changes (7)
  • content/Guides/.agent-telemetry.mdx
  • content/Guides/.agent-tracing.mdx
  • content/Guides/.key-value.mdx
  • content/Guides/.ai-gateway.mdx
  • content/Guides/.devmode.mdx
  • content/Guides/.agent-logging.mdx
  • content/Guides/.vector-db.mdx
🧰 Additional context used
🧠 Learnings (10)
📓 Common learnings
Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/sdk.mdc:0-0
Timestamp: 2025-07-23T12:40:34.834Z
Learning: Applies to agent-docs/src/agents/**/*.ts : Use the storage APIs for persisting data
content/Guides/agent-data-handling.mdx (4)

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/agent.mdc:0-0
Timestamp: 2025-07-23T12:40:22.412Z
Learning: Applies to agent-docs//src/agents//index.ts : Prefer naming the default function Agent or the name of the Agent based on the context of the Agent description

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/agentuity.mdc:0-0
Timestamp: 2025-07-23T12:40:26.540Z
Learning: Applies to agent-docs/**/agentuity.yaml : Do not suggest edits to the Agentuity AI Configuration file (agentuity.yaml)

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/sdk.mdc:0-0
Timestamp: 2025-07-23T12:40:34.834Z
Learning: Applies to agent-docs/src/agents/**/*.ts : Consider agent communication for complex workflows

Learnt from: afterrburn
PR: #195
File: agent-docs/src/agents/doc-processing/docs-processor.ts:7-15
Timestamp: 2025-06-18T04:07:57.583Z
Learning: In the agent-docs project, the ChunkMetadata type requires title and description fields to be mandatory strings rather than optional, indicating that the system ensures these fields are always populated during document processing.

content/Guides/meta.json (2)

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/agentuity.mdc:0-0
Timestamp: 2025-07-23T12:40:26.540Z
Learning: Applies to agent-docs/**/agentuity.yaml : Do not suggest edits to the Agentuity AI Configuration file (agentuity.yaml)

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/agent.mdc:0-0
Timestamp: 2025-07-23T12:40:22.412Z
Learning: Applies to agent-docs//src/agents//index.ts : Prefer naming the default function Agent or the name of the Agent based on the context of the Agent description

content/Guides/agent-tracing.mdx (5)

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/agent.mdc:0-0
Timestamp: 2025-07-23T12:40:22.412Z
Learning: Applies to agent-docs//src/agents//index.ts : Prefer naming the default function Agent or the name of the Agent based on the context of the Agent description

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/sdk.mdc:0-0
Timestamp: 2025-07-23T12:40:34.834Z
Learning: Applies to agent-docs/src/agents/**/*.ts : Consider agent communication for complex workflows

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/sdk.mdc:0-0
Timestamp: 2025-07-23T12:40:34.834Z
Learning: Applies to agent-docs/src/agents/**/*.ts : Use TypeScript for better type safety and IDE support

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/agent.mdc:0-0
Timestamp: 2025-07-23T12:40:22.412Z
Learning: Applies to agent-docs//src/agents//index.ts : All code should be in Typescript format

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/sdk.mdc:0-0
Timestamp: 2025-07-23T12:40:34.834Z
Learning: Applies to agent-docs/src/agents/**/*.ts : Leverage the provided logger for consistent logging

content/Guides/agent-logging.mdx (8)

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/sdk.mdc:0-0
Timestamp: 2025-07-23T12:40:34.834Z
Learning: Applies to agent-docs/src/agents/**/*.ts : Leverage the provided logger for consistent logging

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/agent.mdc:0-0
Timestamp: 2025-07-23T12:40:22.412Z
Learning: Applies to agent-docs//src/agents//index.ts : Use the provided logger from the AgentContext interface such as ctx.logger.info("my message: %s", "hello")

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/agent.mdc:0-0
Timestamp: 2025-07-23T12:40:22.412Z
Learning: Applies to agent-docs//src/agents//index.ts : Prefer naming the default function Agent or the name of the Agent based on the context of the Agent description

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/sdk.mdc:0-0
Timestamp: 2025-07-23T12:40:34.834Z
Learning: Applies to agent-docs/src/agents/**/*.ts : Use TypeScript for better type safety and IDE support

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/sdk.mdc:0-0
Timestamp: 2025-07-23T12:40:34.834Z
Learning: Applies to agent-docs/src/agents/**/*.ts : Consider agent communication for complex workflows

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/agentuity.mdc:0-0
Timestamp: 2025-07-23T12:40:26.540Z
Learning: Applies to agent-docs/**/agentuity.yaml : Do not suggest edits to the Agentuity AI Configuration file (agentuity.yaml)

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/agent.mdc:0-0
Timestamp: 2025-07-23T12:40:22.412Z
Learning: Applies to agent-docs//src/agents//index.ts : All code should be in Typescript format

Learnt from: afterrburn
PR: #198
File: agent-docs/src/agents/doc-qa/index.ts:9-50
Timestamp: 2025-06-20T13:09:14.197Z
Learning: In the agent-docs codebase, the user prefers to let exceptions throw from Agent functions rather than adding local try-catch blocks, allowing errors to be handled at a higher level in the application.

content/Guides/devmode.mdx (6)

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/agent.mdc:0-0
Timestamp: 2025-07-23T12:40:22.412Z
Learning: Applies to agent-docs//src/agents//index.ts : Prefer naming the default function Agent or the name of the Agent based on the context of the Agent description

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/agentuity.mdc:0-0
Timestamp: 2025-07-23T12:40:26.540Z
Learning: Applies to agent-docs/**/agentuity.yaml : Do not suggest edits to the Agentuity AI Configuration file (agentuity.yaml)

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/sdk.mdc:0-0
Timestamp: 2025-07-23T12:40:34.834Z
Learning: Applies to agent-docs/src/agents/**/*.ts : Use TypeScript for better type safety and IDE support

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/agent.mdc:0-0
Timestamp: 2025-07-23T12:40:22.412Z
Learning: Applies to agent-docs//src/agents//index.ts : All code should be in Typescript format

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/sdk.mdc:0-0
Timestamp: 2025-07-23T12:40:34.834Z
Learning: Applies to agent-docs/src/agents/**/*.ts : Consider agent communication for complex workflows

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/agent.mdc:0-0
Timestamp: 2025-07-23T12:40:22.412Z
Learning: Applies to agent-docs//src/agents//index.ts : Prefer loading types from the node modules package @agentuity/sdk in the node_modules folder

content/Guides/vector-db.mdx (2)

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/sdk.mdc:0-0
Timestamp: 2025-07-23T12:40:34.834Z
Learning: Applies to agent-docs/src/agents/**/*.ts : Use the storage APIs for persisting data

Learnt from: afterrburn
PR: #208
File: agent-docs/src/agents/doc-qa/retriever.ts:46-51
Timestamp: 2025-06-28T15:55:43.334Z
Learning: In Agentuity vector search API, the query parameter cannot be an empty string as it would throw an error. When performing metadata-only searches (like retrieving all chunks for a specific document path), a single space ' ' can be used as a workaround since the API requires a non-empty query string.

content/Guides/object-storage.mdx (1)

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/sdk.mdc:0-0
Timestamp: 2025-07-23T12:40:34.834Z
Learning: Applies to agent-docs/src/agents/**/*.ts : Use the storage APIs for persisting data

content/Guides/key-value.mdx (1)

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/sdk.mdc:0-0
Timestamp: 2025-07-23T12:40:34.834Z
Learning: Applies to agent-docs/src/agents/**/*.ts : Use the storage APIs for persisting data

content/Guides/agent-telemetry.mdx (7)

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/agent.mdc:0-0
Timestamp: 2025-07-23T12:40:22.412Z
Learning: Applies to agent-docs//src/agents//index.ts : Prefer naming the default function Agent or the name of the Agent based on the context of the Agent description

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/sdk.mdc:0-0
Timestamp: 2025-07-23T12:40:34.834Z
Learning: Applies to agent-docs/src/agents/**/*.ts : Use TypeScript for better type safety and IDE support

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/sdk.mdc:0-0
Timestamp: 2025-07-23T12:40:34.834Z
Learning: Applies to agent-docs/src/agents/**/*.ts : Consider agent communication for complex workflows

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/sdk.mdc:0-0
Timestamp: 2025-07-23T12:40:34.834Z
Learning: Applies to agent-docs/src/agents/**/*.ts : Import types from '@agentuity/sdk'

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/agentuity.mdc:0-0
Timestamp: 2025-07-23T12:40:26.540Z
Learning: Applies to agent-docs/**/agentuity.yaml : Do not suggest edits to the Agentuity AI Configuration file (agentuity.yaml)

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/agent.mdc:0-0
Timestamp: 2025-07-23T12:40:22.412Z
Learning: Applies to agent-docs//src/agents//index.ts : All code should be in Typescript format

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/sdk.mdc:0-0
Timestamp: 2025-07-23T12:40:34.834Z
Learning: Applies to agent-docs/src/agents/**/*.ts : Leverage the provided logger for consistent logging

🪛 LanguageTool
content/Guides/agent-tracing.mdx

[style] ~6-~6: Consider a different adjective to strengthen your wording.
Context: ...your agents --- Agent tracing provides deep visibility into your agent's execution ...

(DEEP_PROFOUND)


[style] ~87-~87: This phrase is redundant. Consider writing “moments” or “times”.
Context: ... parameters) Events mark specific moments in time with additional context (milestones, st...

(MOMENT_IN_TIME)

content/Guides/devmode.mdx

[style] ~8-~8: ‘exact same’ might be wordy. Consider a shorter alternative.
Context: ...ying them to the cloud. It provides the exact same interface and capabilities you'll have ...

(EN_WORDINESS_PREMIUM_EXACT_SAME)

content/Guides/key-value.mdx

[uncategorized] ~180-~180: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...hours - API cache: 5-60 minutes - Rate limiting counters: Until period reset ### Dat...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Workers Builds: docs
🔇 Additional comments (7)
content/Cloud/meta.json (1)

9-9: Verify that the new slug actually resolves.

The "object-storage" page is now referenced in the Cloud section. Please double-check that content/Cloud/object-storage.mdx ships in the same PR and that the deployed site’s routing recognises the /Cloud/object-storage path; otherwise the sidebar link will 404.

content/Guides/agent-data-handling.mdx (1)

164-164: Link path casing may break on case-sensitive hosts.

The link was changed to /Guides/agent-streaming (capital “G”). All other internal links appear to use lower-case paths (e.g. /guides/...). If the static-site host is case-sensitive, this may 404. Consider reverting to lower-case or standardising across the repo.

content/Guides/meta.json (2)

7-9: Nice addition – guides surface clearly.

Adding “devmode”, “agent-logging”, and “agent-telemetry” improves discoverability. No issues spotted.


14-14: Cross-section consistency check.

“object-storage” is added here as well as in content/Cloud/meta.json. Good to see parity; please ensure both pages share the same slug and metadata (title, description) for coherent navigation.

content/Guides/agent-tracing.mdx (1)

99-106: Attribute value may violate OT spec

request.trigger() might return an object; span attributes must be primitive (string, bool, int, double). Convert to a string or split into multiple attributes.

content/Guides/agent-telemetry.mdx (1)

64-72: Verify SDK doc link paths

/SDKs/javascript and /SDKs/python may not exist under the current docs routing (most SDK pages live under /SDK/javascript or /Guides/SDKs/...). Broken internal links hurt navigation.

Run a link checker or manually confirm the paths and adjust if necessary (e.g. /SDK/javascript).

content/Guides/key-value.mdx (1)

12-15: Broken cross-link target

/Cloud/vector-memory appears to refer to the Console page, while analogous links in the new guides point to other Guides. If the intent is to jump to the new Vector-DB guide, change to /Guides/vector-db; otherwise clarify “(Cloud Console)” so readers know it’s a UI page.

Comment on lines +106 to +151

Search operations find semantically similar documents based on a text query. You can control the number of results, similarity threshold, and filter by metadata.

<CodeExample>
```javascript
// JavaScript/TypeScript
// Basic semantic search
const results = await context.vector.search('knowledge-base', {
query: 'What is an agent platform?',
limit: 5,
similarity: 0.7,
metadata: { category: 'platform' }
});

// Process results
results.forEach(result => {
console.log(`Found: ${result.metadata.source}`);
console.log(`Similarity: ${1 - result.distance}`);
});
```

```python
# Python
# Semantic search with parameters
results = await context.vector.search(
"knowledge-base",
query="What is an agent platform?",
limit=5,
similarity=0.7,
metadata={"category": "platform"}
)

# Process results
for result in results:
similarity_score = 1.0 - result.distance
print(f"Found: {result.metadata['source']}")
print(f"Similarity: {similarity_score}")
```
</CodeExample>

**Search Parameters:**
- `query` (required): Text query to search for
- `limit` (optional): Maximum number of results to return
- `similarity` (optional): Minimum similarity threshold (0.0-1.0)
- `metadata` (optional): Filter results by metadata key-value pairs

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Document the “non-empty query” requirement

The Vector Search backend rejects an empty string. This is a common pit-fall surfaced in earlier incidents (see retrieved learnings). Add an explicit note so users don’t trip on silent 400s.

-### Searching Vector Storage
+### Searching Vector Storage
+
+> **Important:** `query` must be a **non-empty string**.  
+> Use a single space `" "` when you need metadata-only filtering without affecting similarity ranking.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
Search operations find semantically similar documents based on a text query. You can control the number of results, similarity threshold, and filter by metadata.
<CodeExample>
```javascript
// JavaScript/TypeScript
// Basic semantic search
const results = await context.vector.search('knowledge-base', {
query: 'What is an agent platform?',
limit: 5,
similarity: 0.7,
metadata: { category: 'platform' }
});
// Process results
results.forEach(result => {
console.log(`Found: ${result.metadata.source}`);
console.log(`Similarity: ${1 - result.distance}`);
});
```
```python
# Python
# Semantic search with parameters
results = await context.vector.search(
"knowledge-base",
query="What is an agent platform?",
limit=5,
similarity=0.7,
metadata={"category": "platform"}
)
# Process results
for result in results:
similarity_score = 1.0 - result.distance
print(f"Found: {result.metadata['source']}")
print(f"Similarity: {similarity_score}")
```
</CodeExample>
**Search Parameters:**
- `query` (required): Text query to search for
- `limit` (optional): Maximum number of results to return
- `similarity` (optional): Minimum similarity threshold (0.0-1.0)
- `metadata` (optional): Filter results by metadata key-value pairs
### Searching Vector Storage
> **Important:** `query` must be a **non-empty string**.
> Use a single space `" "` when you need metadata-only filtering without affecting similarity ranking.
Search operations find semantically similar documents based on a text query. You can control the number of results, similarity threshold, and filter by metadata.
<CodeExample>
🤖 Prompt for AI Agents
In content/Guides/vector-db.mdx between lines 106 and 151, add a clear note
stating that the 'query' parameter for vector search must be a non-empty string
because the backend rejects empty queries and returns a 400 error. This note
should be placed near the search parameters section to warn users explicitly and
help prevent silent failures when an empty query is provided.

- Fix inconsistent error variable names in logging examples
- Add missing Python imports for code examples
- Correct loopback address in DevMode guide (0.0.0.1 to 127.0.0.1)
- Replace TODO comment (Object Storage) with actual screenshot
- Remove manual `span.end()` calls in tracing examples
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (4)
content/Guides/agent-tracing.mdx (2)

30-54: Explicitly mark successful spans with SpanStatusCode.OK

The happy-path in this snippet returns without ever calling span.setStatus({ code: SpanStatusCode.OK }). Although the OpenTelemetry spec treats an unspecified status as UNSET, many back-ends interpret this as “unknown”. Explicitly marking success keeps dashboards consistent with the error path shown later in the doc.

       // Perform work
       const result = await processData();

+      // Mark span as successful
+      span.setStatus({ code: SpanStatusCode.OK });
+
       // Add events to mark important moments
       span.addEvent('data-processed', { 
         itemCount: result.length 
       });

200-205: Avoid storing PII in trace attributes

Attributes like userId, requestId, or resourceId can be classified as personally-identifiable or sensitive business data once exported to external APM systems. Consider:

  • Hashing / anonymising user identifiers.
  • Adding a short disclaimer in the guide about sensitive attributes.
content/Guides/devmode.mdx (2)

8-8: Tighten wording – replace “exact same”

Minor style nit: “exact same” is considered wordy. “identical” or simply “the same” reads cleaner.

- It provides the exact same interface and capabilities you'll have in production.
+ It provides the same interface and capabilities you'll have in production.

24-31: Clarify port exposure & conflicts

The example fixes the loopback address (👍) but developers running multiple agents may still collide on the hard-coded 3500 port. Adding a short note that --port <number> can override the default would help avoid confusion.

No code change required—just a one-line doc hint under the CLI snippet.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 712d4fd and 6f63dd8.

📒 Files selected for processing (5)
  • content/Guides/agent-logging.mdx (1 hunks)
  • content/Guides/agent-tracing.mdx (1 hunks)
  • content/Guides/ai-gateway.mdx (1 hunks)
  • content/Guides/devmode.mdx (1 hunks)
  • content/Guides/object-storage.mdx (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • content/Guides/object-storage.mdx
🚧 Files skipped from review as they are similar to previous changes (2)
  • content/Guides/ai-gateway.mdx
  • content/Guides/agent-logging.mdx
🧰 Additional context used
🧠 Learnings (3)
📓 Common learnings
Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/sdk.mdc:0-0
Timestamp: 2025-07-23T12:40:34.834Z
Learning: Applies to agent-docs/src/agents/**/*.ts : Use the storage APIs for persisting data
content/Guides/agent-tracing.mdx (4)

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/agent.mdc:0-0
Timestamp: 2025-07-23T12:40:22.412Z
Learning: Applies to agent-docs//src/agents//index.ts : Prefer naming the default function Agent or the name of the Agent based on the context of the Agent description

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/sdk.mdc:0-0
Timestamp: 2025-07-23T12:40:34.834Z
Learning: Applies to agent-docs/src/agents/**/*.ts : Consider agent communication for complex workflows

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/sdk.mdc:0-0
Timestamp: 2025-07-23T12:40:34.834Z
Learning: Applies to agent-docs/src/agents/**/*.ts : Use TypeScript for better type safety and IDE support

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/agent.mdc:0-0
Timestamp: 2025-07-23T12:40:22.412Z
Learning: Applies to agent-docs//src/agents//index.ts : All code should be in Typescript format

content/Guides/devmode.mdx (6)

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/agent.mdc:0-0
Timestamp: 2025-07-23T12:40:22.412Z
Learning: Applies to agent-docs//src/agents//index.ts : Prefer naming the default function Agent or the name of the Agent based on the context of the Agent description

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/agentuity.mdc:0-0
Timestamp: 2025-07-23T12:40:26.540Z
Learning: Applies to agent-docs/**/agentuity.yaml : Do not suggest edits to the Agentuity AI Configuration file (agentuity.yaml)

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/sdk.mdc:0-0
Timestamp: 2025-07-23T12:40:34.834Z
Learning: Applies to agent-docs/src/agents/**/*.ts : Use TypeScript for better type safety and IDE support

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/agent.mdc:0-0
Timestamp: 2025-07-23T12:40:22.412Z
Learning: Applies to agent-docs//src/agents//index.ts : All code should be in Typescript format

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/sdk.mdc:0-0
Timestamp: 2025-07-23T12:40:34.834Z
Learning: Applies to agent-docs/src/agents/**/*.ts : Consider agent communication for complex workflows

Learnt from: CR
PR: agentuity/docs#0
File: agent-docs/.cursor/rules/agent.mdc:0-0
Timestamp: 2025-07-23T12:40:22.412Z
Learning: Applies to agent-docs//src/agents//index.ts : Prefer loading types from the node modules package @agentuity/sdk in the node_modules folder

🪛 LanguageTool
content/Guides/agent-tracing.mdx

[style] ~6-~6: Consider a different adjective to strengthen your wording.
Context: ...your agents --- Agent tracing provides deep visibility into your agent's execution ...

(DEEP_PROFOUND)


[style] ~85-~85: This phrase is redundant. Consider writing “moments” or “times”.
Context: ... parameters) Events mark specific moments in time with additional context (milestones, st...

(MOMENT_IN_TIME)

content/Guides/devmode.mdx

[style] ~8-~8: ‘exact same’ might be wordy. Consider a shorter alternative.
Context: ...ying them to the cloud. It provides the exact same interface and capabilities you'll have ...

(EN_WORDINESS_PREMIUM_EXACT_SAME)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Workers Builds: docs
🔇 Additional comments (1)
content/Guides/agent-tracing.mdx (1)

52-53: Previous “double-end span” issue resolved – LGTM

The earlier manual span.end() call has been removed, avoiding double-ending warnings in many OTEL SDKs. 👍

@parteeksingh24 parteeksingh24 merged commit 67a4bbc into main Jul 30, 2025
2 checks passed
@parteeksingh24 parteeksingh24 deleted the parteek/add-guides-documentation branch July 30, 2025 15:35
@coderabbitai coderabbitai bot mentioned this pull request Sep 16, 2025
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.

2 participants