AgentOS: Instructions file for Codex

AGENTS.md

Project Identity

AgentOS is the human operating layer above OpenClaw.

OpenClaw is the backend, runtime, orchestration, agent, tool, model, session, and gateway layer. AgentOS must not clone or replace OpenClaw. AgentOS should provide the operator-facing workspace, control, visibility, policy, and coordination layer on top of OpenClaw.

When in doubt:

• Use OpenClaw as the source of truth.
• Keep AgentOS as the control/UI/application layer.
• Do not duplicate OpenClaw backend functionality inside AgentOS.

Required Project Skill

Before making AgentOS code, UX, OpenClaw integration, security, release, or publishing changes, read:

docs/agentos-codex-skill.md

Keep all changes aligned with that skill.

If the task touches OpenClaw, releases, npm publishing, GitHub releases, auth, accounts, model credentials, API routes, local operator access, browser profiles, or security-sensitive behavior, the skill file is mandatory context, not optional background.

Project Language

• The project’s default language is English.
• Do not add Turkish content to the project unless the user explicitly asks for it.
• Keep user-facing copy in English, including UI text, placeholders, examples, documentation, seeded content, errors, empty states, release notes, and CLI output.
• Internal comments should also be English unless there is a strong reason otherwise.

Git

• All git commit messages must be written in English.
• Use concise, imperative commit subjects.
• Prefer Conventional Commits format, for example: feat(auth): add session refresh.
• Keep the subject line short, ideally under 72 characters.
• Default to a single-line commit message.
• Only add a commit body when extra context is genuinely necessary.
• If a body is needed, keep it brief and focused on why the change was made.
• Do not generate long commit messages or file-by-file summaries by default.
• Do not write commit messages in Turkish unless the user explicitly asks for it.

OpenClaw Integration Rules