Skip to content

History / Home

Revisions

  • [Skill-Selection-and-Routing] first-match docs catch up with fail-loud routing (#3087) Strategy 3 rewritten as single-candidate direct routing with the 0.7.21 migration note; priority chain + decision table updated; ambiguity now documented as SkillRoutingException, matching SkillResolver. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

    @fareporterjenkins fareporterjenkins committed Jun 11, 2026
  • Merge branch 'master' of https://github.com/Deep-CodeAI/Agents.KT.wiki

    @fareporterjenkins fareporterjenkins committed May 29, 2026
  • docs: update wiki for JSONL audit exporter

    @fareporterjenkins fareporterjenkins committed May 23, 2026
  • docs: align wiki with website

    @fareporterjenkins fareporterjenkins committed May 12, 2026
  • docs: reflect three model providers (Ollama / Anthropic / OpenAI) With the Anthropic (#1644) and OpenAI (#1656) adapters shipped, the wiki was still claiming Ollama-only. Updated: - Home: Installation and Model & Tool Calling links now mention all three providers. - Installation-and-Setup: prerequisites table, new "Model Provider Setup" overview section showing all three model {} forms side by side, Ollama section retitled and re-scoped to local development. - Model-and-Tool-Calling: the "model {}" intro now opens with all three providers and a one-line switching note; ModelConfig data class + DSL table extended with the new fields (apiKey, maxTokens, anthropicBaseUrl, openAiBaseUrl); ModelClient section enumerates OllamaClient / ClaudeClient / OpenAiClient with their wire-mapping one-liners. - Roadmap: Phase 1 lines for both new adapters; status table gains rows for Anthropic and OpenAI integration. Pre-existing local diffs in the same pages (typed-tools section, tool-authorization section) carried along untouched. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @fareporterjenkins fareporterjenkins committed May 10, 2026
  • Add Agent Deployment Modes page Same agent, three ways to ship it. Each mode is one line of glue away from the next — a deliberate progression that lets agents earn their way from embedded function to autonomous entity: - Library — agent<IN, OUT>("...") { } in your JVM, in-process - Hosted — + McpServer.from(agent).start() for an MCP endpoint - Autonomous — fun main(args) = exitProcess(McpRunner.serve(...)) runs as its own process / JAR / Docker / native binary The page covers all three with code, "best for" notes, an ASCII flow diagram, and a 7-row tradeoff table (overhead, type safety, deploy unit, scaling, isolation, language reach, ops cost). Closes with a "progression" section explaining when to advance modes. Sidebar and Home table updated. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @fareporterjenkins fareporterjenkins committed May 2, 2026
  • Reflect shipped MCP work on Roadmap and Home Roadmap was silent about the MCP arc that landed in Phase 2: - Phase 2 Priority: mark MCP client / server / 2025-03-26 conformance / McpRunner as done. Replace the abandoned `Tool<IN, OUT>` + `McpTool<IN, OUT>` line with a note explaining we deliberately took a different path (MCP tools mint as standard ToolDefs). - Phase 2 Secondary: add the still-pending MCP follow-ups (incoming auth on McpServer, OAuth client, Origin header, MCP-Protocol-Version header, custom tool deserializers). - "What You Can Build Today": add three rows for MCP client / server / runner. - "What is Coming Next": replace the now-shipped MCP entry with the remaining Phase 2 items. Home: tighten the MCP Integration row to name McpServer and McpRunner explicitly, since those are the surfaces external clients actually hit. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @fareporterjenkins fareporterjenkins committed May 2, 2026
  • Add MCP Integration page Bidirectional MCP coverage — consuming external MCP servers via the mcp { server() } agent DSL (HTTP/stdio/TCP transports, Bearer auth, tool name namespacing) and exposing agent skills as MCP tools via McpServer.from(agent). Includes how external clients (Claude Code, Cursor, generic MCP libraries) connect to an agent's HTTP endpoint, the lower-level McpClient factories, and the in-process mock servers shipped for hermetic tests. Sidebar and Home table updated to link the new page. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

    @fareporterjenkins fareporterjenkins committed May 2, 2026
  • Initial wiki: 29 educational articles Getting Started, Core Concepts, Composition Operators, LLM Integration, Guided Generation, Agent Memory, and Reference articles with full code examples. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

    @fareporterjenkins fareporterjenkins committed Mar 28, 2026