Reference
Reference pages provide quick access to stable Jugg terms, command options, tool contracts, configuration meanings, log locations, and runtime boundaries. They are not tutorials and do not explain mechanisms in depth. If you need step-by-step instructions for a run, debugging session, or a common problem, start with the guides and FAQ pages.
Page index
| Page | What to look up |
|---|---|
| Compatibility | Supported IDE, AGP, Gradle, Kotlin, Android device, and product capability ranges. |
| Glossary | Terms such as compile, deploy, fallback, and code swap used in Jugg documentation. |
| CLI commands | jugg subcommands, global options, and common option mappings. |
| MCP tools | MCP tool names, input and output conventions, and error codes for Agents. |
| Configuration | Meanings of Run Configuration, global settings, project caches, and remote configuration. |
| Log files | Jugg log locations, formats, common search terms, and MCP artifact locations. |
| Limits | Boundaries of incremental compilation, deployment, Debug, androidTest, and MCP/CLI features. |
Common entry points
- Need the syntax for a command: See CLI commands.
- Want an Agent to call Jugg: See MCP tools.
- Need to find logs: See Log files.
- Need to decide whether to fall back to Gradle: See Limits.
TIP
Reference pages are kept concise. For complete workflows, they link to the relevant guide, capability, or FAQ page instead of repeating every step.