Repository navigation
MOD-19391: Redis Agent Playbooks developer docs - #4249
Conversation
|
|
🧠 Redis MemoryFound 12 related items from repository history:
Memory updated at 7520513 |
|
This needs the same re-base as the other PR in this stack to get the new nav and look/feel. I've also added Andy and Paolo for their review of the build changes proposed here and anything else they see. In case we can pull off some interactive demo of this component and also to get more eyes on this in the final sprint. |
andy-stark-redis
left a comment
There was a problem hiding this comment.
@tylerhutcherson The language mainly looks OK but I've made a few comments here and there. However, the PR seems to invent a whole new system for supplying the code examples when we already have a really good one available :-)
I've added a new commit to enable three new language variants in the docs for Iris Python, TS, and cURL examples (they are listed as if they were "clients" because that is what we mainly deal with in the docs). We have a Claude skill for adding tabbed code examples (TCEs), so if you ask for the examples to be reworked in this form, it should know what you mean. The example source files should be placed in local_examples/iris.
The TCE boxes on the published page allow you to copy the full text of the example rather than download, so any surrounding body text that refers to downloading example files will need to be removed. Some of the build scripts you've added will also be unnecessary when the examples are redone as TCEs.
If you encounter any problems with this then just let me know and I'll be happy to help out.
Updating to use the existing TCE structure and format! |
c0ef4a2 to
d7293c3
Compare
…amples Adds three TCE pseudo-client keys, "Python (Iris)", "TypeScript (Iris)", and "cURL (Iris)", so Iris examples can use the standard clients-example system instead of multitabs. Each key is the visible tab title and is shared across all Iris products, so names avoid any one SDK package. - config.toml: keys in clientsExamples and clientsConfig, modeled on RedisVL. Own clientId (iris-python/-typescript/-curl), empty quickstartSlug and mappingClientId, so tabs don't carry redis-py or node-redis identity in the code-examples JSON metadata. - build/local_examples.py: .ts/.mts -> typescript, .sh -> bash; a path containing 'iris' selects the Iris client (put sources under local_examples/iris/). .mts keeps top-level await working under tsx. Non-Iris .ts/.sh files resolve to no configured client. - build/components/example.py: comment prefixes for typescript (//) and bash (#); without them Example() rejects the language. Verified with a throwaway three-language set: the build tagged each file with the right client and Hugo rendered the tabs with correct step slices, lexers, full-file templates, and clientId/clientName. The test set was removed; no pages are converted in this commit. Gotcha: get_example_id_from_file reads only line 1, so .sh sources must start with "# EXAMPLE:" and cannot carry a shebang. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Discover turn context through the SDK before running OpenAI Agents SDK or LangGraph. Keep standard MCP clients and tool guidance on the existing MCP page, and suppress drafts while tool failures remain unresolved.
fafb18d to
7520513
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 7520513. Configure here.
| - 'config.toml' | ||
| - 'layouts/partials/process-markdown-content.html' | ||
| - 'layouts/_default/apireference.html' | ||
| - '.github/workflows/check-playbook-docs.yml' |
There was a problem hiding this comment.
CI ignores Playbooks diagram asset changes
Medium Severity
The Playbooks docs workflow path filters omit static/images/ai/context-engine/. test_proposal_diagram_qualifies_default_retention_windows reads agent-playbook-proposals.svg, so a diagram-only edit that drops the default 30-day labels would not run that check.
Additional Locations (1)
Reviewed by Cursor Bugbot for commit 7520513. Configure here.


MOD-19391 — Redis Agent Playbooks developer documentation.
Adds eleven developer pages for publishing and retrieving approved FAQs, managing reusable skills, reviewing proposals and evidence, and supplying playbook knowledge before and during an agent turn. Examples focus on the published unified Python SDK, HTTP, and the real Iris CLI. TypeScript examples are withheld until a comparable unified SDK is available; the quickstart links separately to the generated package on npm.
Scope
redis-iris==0.1.0a4, uses unified discovery/skill helpers, and exposes management operations through the public.clientproperty. Python requires 3.11+. The published unified package depends onredis-agent-playbook==0.1.0a3.iris agent-playbookoriris --json agent-playbookdirectly, retain JSON/file preparation, reconcile keyed entries without automatic publication, and publish explicit reviewed versions. Proposal examples preserve source/evidence files and pass the reviewed revision.e883781f69bf9e4ae426b2dd33bcf6fa159c8d32during the October 21 audit. Pins describe the tested examples rather than claiming every generated package is the newest release.Rebase and review readiness
mainat115a3c5ec1fb12e2aebd1da80e93bcd8ace25fd3without conflicts. Range comparison confirms that the Playbooks content and programs are preserved while retaining main's navigation updates.7520513f6102b62bdce8a655b6de93745c0f5d78removes the five heading-number prefixes and adds a regression check. Example programs are unchanged, and no repository links targeted the former numbered anchors.Validation
Post-rebase validation on October 22:
python -m pytest build/agent_playbook_docs -q: 139 passed on the rebased content. After the heading-only correction and new regression test,python -m pytest build/agent_playbook_docs/test_reference.py -q: 8 passed. Together these cover all 140 current suite tests; the executable programs are unchanged by the follow-up.python -m pytest build/test_cli_parser.py build/test_command_lists.py -q: 19 passed for the shared example-parser and command-list helpers.git diff --checkpass. Dependencies were installed in a fresh Python 3.12 environment and with the checked-in npm lockfile.#create-an-faqwithout application errors.e883781f69bf9e4ae426b2dd33bcf6fa159c8d32. Cases cover core SDK/cURL/CLI workflows, reader-only retrieval, MCP, async Python, and complete-program copies; each provisions and removes its own playbook and scoped keys. Rebase and presentation changes do not alter those programs.Validation boundaries and follow-ups:
npm auditreports one existing low-severity transitive esbuild advisory concerning its development server on Windows (GHSA-g7r4-m6w7-qqqr). The rebase does not change that dependency lockfile; no dependency update is bundled into this docs review.Latest developer commit:
7520513f6102b62bdce8a655b6de93745c0f5d78—docs: fix Playbooks quickstart navigation. Rebased cleanup:428b113da; direct Iris CLI commands:12bd46903; Proposals editorial pass:c51fa409f; unified Python/CLI migration:05a9897e5.Stack and publication
MOD-19391-playbook-developer-docs→main(this PR), ready for review.main.Neither PR is merged. Merging into
mainpublishes the documentation; repository and staging previews are public. Review readiness is not launch publication approval.Note
Low Risk
Changes are documentation, example sources, and CI validation tooling; they do not alter production services, though incorrect SDK pins or contract drift would fail checks rather than ship silently.
Overview
Adds the Redis Agent Playbooks developer section under Context Engine: overview, concepts, quickstart, FAQ/skill/proposal guides, retrieval, MCP, agent integration (OpenAI Agents / LangGraph), limits, and a Redoc-backed data-plane API reference tied to a checked-in OpenAPI contract.
Introduces
build/agent_playbook_docs, which locks the published contract to iris-sdks (source-lock.json,check_sdk_source.py), assembles tabbed examples fromlocal_examples/iris/playbooksandclients-examplemarkup (examples.py), and runs a large pytest suite against schema-checked HTTP fixtures plus controlled agent/MCP/CLI runs;live_examples.pysupports optional end-to-end runs against a local stack. A path-filtered GitHub Actioncheck-playbook-docs.ymlruns lock checks, example generation, TypeScript compile of generated fixtures, and the suite on relevant PRs.Extends the docs example pipeline for Iris: Python (Iris), cURL, CLI, and internal TypeScript/bash handling in
local_examples.py,example.py,clients.tsv, andconfig.toml, while the guides emphasize unified Python SDK, HTTP, andiris agent-playbookCLI (TypeScript tabs withheld from published pages). Updates the Context Engine landing page to surface Playbooks and softens deployment wording.Reviewed by Cursor Bugbot for commit 7520513. Bugbot is set up for automated code reviews on this repo. Configure here.