molecule-core/org-templates/molecule-dev/.env.example
Hongming Wang 24fec62d7f initial commit — Molecule AI platform
Forked clean from public hackathon repo (Starfire-AgentTeam, BSL 1.1)
with full rebrand to Molecule AI under github.com/Molecule-AI/molecule-monorepo.

Brand: Starfire → Molecule AI.
Slug: starfire / agent-molecule → molecule.
Env vars: STARFIRE_* → MOLECULE_*.
Go module: github.com/agent-molecule/platform → github.com/Molecule-AI/molecule-monorepo/platform.
Python packages: starfire_plugin → molecule_plugin, starfire_agent → molecule_agent.
DB: agentmolecule → molecule.

History truncated; see public repo for prior commits and contributor
attribution. Verified green: go test -race ./... (platform), pytest
(workspace-template 1129 + sdk 132), vitest (canvas 352), build (mcp).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-13 11:55:37 -07:00

12 lines
452 B
Plaintext

# Place a .env file in each workspace folder to inject secrets.
# These become workspace-level secrets (encrypted, never exposed to browser).
#
# Example for Claude Code workspaces:
# CLAUDE_CODE_OAUTH_TOKEN=sk-ant-oat01-...
#
# Example for OpenAI/LangGraph workspaces:
# OPENAI_API_KEY=sk-proj-...
#
# Each workspace folder can have its own .env with different keys.
# A .env at the org root is shared across all workspaces (workspace overrides win).