Providers and permissions
Farming connects to different coding Agents. Providers continue to own authentication, models, and Session capabilities; Farming supplies a consistent Project, Chat, Terminal, and Files experience.
Supported interactions
Common Providers include Codex, Claude Code, OpenCode, Qoder, Qwen Code, and other discovered coding CLIs. Depending on the Provider, Farming may offer structured Chat, native Terminal, Session resume, model and reasoning controls, and live Chat/Terminal switching.
Farming shows only capabilities actually declared and verified by the current runtime.
Authentication
Provider login happens on the Farming Host. Installing Farming does not sign in to coding Agents.
To diagnose login:
- start the CLI in a normal Host shell;
- complete authentication or repair Provider configuration;
- return to Farming and check capability or start the Agent again.
Do not put Provider Tokens in Project files or public configuration examples.
Permission principles
Higher permissions let an Agent act with fewer interruptions while increasing possible impact.
- Use confirmation-oriented policies in unfamiliar repositories.
- Grant access only to the Workspace required by the task.
- Keep human confirmation for accounts, releases, payments, messages, and deletion.
- Browser and experimental Computer accounts and system permissions are separate security boundaries.
Changing permissions does not change the Agent or Workspace, create another Browser Profile, or transfer a Resource to another Agent. After an ambiguous permission result, inspect the page, files, and Git state before repeating the operation.