Tatami

Tatami is a generic OpenClaw plugin that appends extra workspace context to the agent system prompt on every before_prompt_build run.

It replaces two legacy workspace hooks:

• inject-context for context/*.md
• session-context for per-session docs in docs/<project>/

What It Injects

Tatami loads two context sources in this order:

1. All *.md files from workspace/context/ (or the configured contextDir)
2. Project docs for the current session, resolved from context/session-settings.json into workspace/docs/<project>/

The plugin appends content through appendSystemContext, so it extends the core OpenClaw workspace context instead of replacing it.

Install

# Standard install from npm
openclaw plugins install @darkdepot/tatami

# Update later from npm
openclaw plugins update tatami

# Local development link
openclaw plugins install -l ./path/to/tatami

# Local tarball or release artifact
openclaw plugins install ./darkdepot-tatami-0.1.1.tgz

Verify installation:

openclaw plugins list
openclaw plugins doctor

Configuration

Configure Tatami in openclaw.json:

{
  plugins: {
    entries: {
      tatami: {
        enabled: true,
        config: {
          contextDir: "context",
          docsDir: "docs",
          maxCharsPerFile: 20000,
          maxCharsTotal: 100000
        }
      }
    }
  }
}

Configuration keys:

• contextDir: workspace-relative directory for shared markdown context files
• docsDir: workspace-relative directory for project documentation
• maxCharsPerFile: truncates each loaded file to this many characters
• maxCharsTotal: stops appending more files after this total content budget

Session Settings Contract

Tatami reads context/session-settings.json and resolves the current project by exact sessionKey.

{
  "agent:iris:s-42a532b8": {
    "projectId": "session-context",
    "projectName": "Session Context"
  }
}

• projectId is the directory name under docs/
• _project.md is loaded first, then the remaining markdown files are sorted alphabetically
• project paths are checked so a projectId cannot escape the configured docsDir

For long-lived installs, prefer the npm package. Local -l installs are best for development.

Development Notes

• Node.js 22+
• TypeScript is loaded directly by OpenClaw via jiti
• No build step is required
• Local validation: npm install && npm run ship:preflight
• Ship report: npm run ship:report:check
• Release sanity check: npm pack --dry-run