redhat-et / redhat-et/docsclaw

feat: contribute DocsClaw as Go-based example to kagenti/agent-examples

Open
#60 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
2
Forks
1
Avg merge
6h 9m
Merged PRs (30d)
1

Description

Summary

Contribute a DocsClaw-based agent example to the
kagenti/agent-examples
repository, demonstrating a Go-based alternative to the Python agents.

Motivation

All current kagenti agent examples use Python with various
frameworks (LangGraph, AG2, CrewAI, Marvin). DocsClaw can
replace 6 of the 10 agents with configuration alone — different
ConfigMaps, same 10 MiB binary. This demonstrates:

  • Single runtime, multiple personalities (vs. framework per agent)
  • 10 MiB per pod vs. 200-500 MiB for Python agents
  • No framework choice paralysis — config-driven behavior

Approach

Start by reproducing the Generic Agent — it's the most
flexible example and shows dynamic tool loading. A DocsClaw
ConfigMap with the same system prompt and MCP tool connections
would produce equivalent behavior.

Depends on

  • #2 (MCP client integration) — needed to connect to the same
    MCP tool servers the Python agents use

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the Generic Agent example in kagenti/agent-examples and the DocsClaw configuration described in this issue. Check issue #2 for MCP client integration and reproduce the Generic Agent's system prompt and MCP tool connections; done means a working Go-based example in the target repository with equivalent behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
ai, backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.