0 Fork 0

mirror of https://github.com/JackChen-me/open-multi-agent.git synced 2026-10-21 18:42:50 -05:00

Files

T

Jack Chen 1a6021b9a5 feat(sandbox): narrow default root to .agent-workspace subdir

Sandbox default root narrows from `process.cwd()` to `<cwd>/.agent-workspace`, an auto-created subdirectory. Built-in filesystem tools (`file_read`, `file_write`, `file_edit`, `grep`, `glob`) enforce this root and require absolute paths. `bash` is intentionally out of scope; full caveat and the three-config knob (default / `process.cwd()` / `null`) live in `docs/tool-configuration.md`.

`defaultWorkspaceDir()` centralises the fallback; `OrchestratorConfig.defaultCwd`, `AgentConfig.cwd`, `RunnerOptions.cwd`, and the tool-layer fallbacks in `path-safety`, `grep`, and `glob` all route through it. Only `file_write` auto-creates the root via `resolvePathWithinCwd`'s new `ensureRoot` option; read-only tools error on a missing root.

22 examples switched from `/tmp/` to `<cwd>/.agent-workspace/<sub>` (basics x 3, providers x 18, integrations x 1). `mcp-bilig-workpaper` routes its existing tmpdir workDir into the Agent's `cwd`.

`README.md`, `README_zh.md`, `docs/tool-configuration.md`, `docs/cli.md`, `docs/providers/minimax.md` updated. JSDoc on the four `cwd` fields aligned with the new default. `.gitignore` ignores `.agent-workspace/`.

`v1.4.2` is current on npm; no released version is affected. Consumers wanting the prior `process.cwd()` default can set `defaultCwd: process.cwd()` explicitly.

2026-05-28 19:34:18 +08:00

express-customer-support

Add example: Express customer support pipeline (closes #133 ) (#191 )

2026-04-29 11:19:44 +08:00

with-engram

feat(deepseek): migrate defaults to V4 model names (#250 )

2026-05-26 15:03:16 +08:00

with-vercel-ai-sdk

feat(deepseek): migrate defaults to V4 model names (#250 )

2026-05-26 15:03:16 +08:00

mcp-bilig-workpaper.ts

feat(sandbox): narrow default root to .agent-workspace subdir

2026-05-28 19:34:18 +08:00

mcp-github.ts

fix: redact secrets in traces, bash env, and dashboard payloads (#263 )

2026-05-28 00:53:34 +08:00

README.md

docs: integrations governance README + retire stale DECISIONS.md (#248 )

2026-05-25 11:28:21 +08:00

trace-observability.ts

feat(trace): include tool input/output in ToolCallTrace (closes #124 )

2026-05-01 18:06:43 +08:00

README.md

examples/integrations/

OMA wired to external systems: MCP servers, observability backends, other frameworks, app shells. Runnable starting points, not product docs.

Two categories live here.

Reference integrations demonstrate wiring against widely used protocols or frameworks. The OMA team maintains these once merged, regardless of who contributed them. Current:

mcp-github.ts: MCP servers via connectMCPTools().
trace-observability.ts: the onTrace API.
with-vercel-ai-sdk/: Next.js + AI SDK + runTeam().
express-customer-support/: Express REST API + runTasks(). Contributed by @CodingBangboo via #191.

Vendor integrations show OMA paired with a specific third-party commercial product. They live under with-<product>/ and stay credited to the contributor. Current:

with-engram/: Engram memory backend. Contributed by @Agentscreator via #160.

Submitting a reference integration

Open a PR following the conventions in examples/README.md. For widely used protocols or frameworks, no prior discussion needed. For niche ones, open a discussion first so we can confirm the wiring is worth maintaining long-term.

Submitting a vendor integration

One condition: the integration is reciprocal. Your product's repo or docs should reference OMA as a supported integration. No payment involved, this is a signal filter for who has actually shipped against OMA.

Flow:

Open a discussion with the link to OMA in your product's docs and a sketch of the example.
Wait for a maintainer reply confirming the example is in scope.
PR it. Follow the conventions in examples/README.md.

If your product doesn't reference OMA yet, open a discussion to get listed in the Ecosystem section.

The Featured Partner program is separate and paid, for prominent README placement. Eligibility is an active OMA integration; reciprocal listing isn't required.

Out of scope here

Marketing copy for a third-party product.
Examples gated behind paid-only APIs with no free or trial tier.
Thin connectMCPTools() wrappers whose only difference from mcp-github.ts is the server name and prefix. Those belong in your own docs.