Skip to content

context.md

Latest commit

 

History

History
21 lines (16 loc) · 1.96 KB

context.md

File metadata and controls

21 lines (16 loc) · 1.96 KB

★ Insight ───────────────────────────────────── I've completed my investigation of pi's configuration system. Here are the key findings:

  1. Pi has two-level settings: Global (~/.pi/agent/settings.json) and project-specific (.pi/settings.json), but these only control core pi behavior (models, theme, compaction) - NOT tool parameter defaults.

  2. Extension-specific config is optional: Some extensions like antigravity-image-gen implement their own config files (~/.pi/agent/extensions/antigravity-image-gen.json), but this is not required or standardized by pi's core.

  3. Subagent has no config mechanism: The subagent tool uses hardcoded defaults (agentScope: "user", confirmProjectAgents: true) and doesn't support configuration files. To add this, you'd need to modify the extension source code. ─────────────────────────────────────────────────

★ Lessons ─────────────────────────────────────

  • Configuration in pi is layered: core settings (global/project) vs. extension-specific (optional, extension-implemented)
  • Extension config patterns are not enforced - each extension decides whether to support configuration files
  • Tool parameter defaults are typically hardcoded in extension code, not configurable via settings.json unless explicitly implemented ─────────────────────────────────────────────────

I've written comprehensive findings to /Users/nejo/src/github/vedang/agents/context.md including:

  • All relevant file paths and line numbers
  • How configuration loading works
  • The extension-specific config pattern (with code examples)
  • Why the subagent tool doesn't currently support default configuration