Get Started on Cloud
BasicsAI AgentsPipelinesActions & ServicesEnvironmentsIntegrationsTargetsTestsDomainsSandboxesTerraformTunnelsYAMLBuddy GitCLIAPIFAQ

bdy integration exec logs

View as Markdown
$bdy integration exec logs [options] <integration> <exec-id>

Show execution logs Required scopes: INTEGRATION_READ

ARGUMENTS
integration
Integration identifier (required)
exec-id
Execution ID (required)
OPTIONS
--context <name>
Connection and scope context: default, git, link or a saved name. Overrides the globally active context for this invocation.
--examples
Show only examples; with this flag --format accepts text, json or jsonl
--verbose
Show REST API requests, responses, timing and retries on stderr
-w, --workspace <domain>
Workspace URL handle. Can be set via variable: BUDDY_WORKSPACE
-p, --project <name>
Project name. Can be set via variable: BUDDY_PROJECT
--scope <scope>
Force scope (WORKSPACE, PROJECT, ENVIRONMENT). By default calculated by provided options and environmental variables (--project, --environment, BUDDY_PROJECT, linked project)
--environment <identifier>
Environment identifier to scope the integration to. Resolves a workspace environment; add
--project
to point at a project environment
--offset <n>
Log line offset. Default: 0
--limit <n>
Maximum number of log lines. Default: all lines
--format <text|json>
Output format: json, text. JSON CLI errors: {error:{code,message,hint}}, exit 1. Default: text (choices: "text", "json")
-h, --help
display help for command

Documentation for bdy v1.25.34

Last modified on Nov 3, 2026

Previous pagelistNext pagestatus

Examples

Show the log (the MCP result) of an execution
bdy int exec logs integration-identifier exec-id$