Skip to content

Configuration reference: every env var on one page #1

Description

@Yunaik

The env vars an agent or a slot reads are spread over .env.example, README.md, docs/agents.md, docs/skills.md, docs/decision-models.md and evals/README.md. A reader who wants to know what LAYA_DEVICE or CUA_DRIVER_BIN does has to grep.

Write docs/configuration.md with one table: variable, who reads it (agent, slot, eval or replay), default, one line on what it does. Then link the page from the Docs list in README.md and cut the per-page repeats down to a pointer.

Where to start:

  • .env.example names 24 variables.
  • git grep -n -E 'environ|getenv' s1a evals scripts lists every reader in code; s1a/config.py reads most of them.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions