Background
Many employees at SkyLabs utilize coding agents (Cursor, GH Copilot, etc...).
Coding agents provide some ways to limit what code is indexed/accessed by agents via configurations (cf. https://cursor.com/docs/context/ignore-files).
However, if we're not careful (or if companies like Anthropic accidentally/intentionally ignore these configurations) we risk leaking proprietary source code, e.g. the SkyLabs FM Automation.
Adopting a best-effort defense against these leaks is a high priority, especially now that we're using a centralized workspace and encouraging more people to build the FM toolchain from source.
Task
- Determine which coding agent(s) & modes of use provide acceptable mechanisms for shielding proprietary code from being indexed
- Set company guidelines for where/how/which coding agents may be employed
- Codify best-effort defense mechanisms within
workspace and other proprietary repositories (e.g. by adding .cursorrules files)
Background
Many employees at SkyLabs utilize coding agents (Cursor, GH Copilot, etc...).
Coding agents provide some ways to limit what code is indexed/accessed by agents via configurations (cf. https://cursor.com/docs/context/ignore-files).
However, if we're not careful (or if companies like Anthropic accidentally/intentionally ignore these configurations) we risk leaking proprietary source code, e.g. the SkyLabs FM Automation.
Adopting a best-effort defense against these leaks is a high priority, especially now that we're using a centralized
workspaceand encouraging more people to build the FM toolchain from source.Task
workspaceand other proprietary repositories (e.g. by adding.cursorrulesfiles)