--source <source>Start from the workspace component you are debugging, such as web, api, worker, queue, or system.
Docs / Workspace logs
Workspace logs should start with a source, level, limit, and time window.
Use envforge logs [workspace] to inspect workspace log lines for a known debugging window. Add --source, --level, --limit, --since, and --until before sharing output in an issue, PR, or agent handoff.
envforge logsbounded query
$envforge logs signed-links --source api --level error --limit 50 --since 2026-06-30T16:00:00Z --until 2026-06-30T17:00:00Z
workspace: signed-links; source: api
filter: level error; limit 50
window: 2026-06-30T16:00:00Z to 2026-06-30T17:00:00Z
Log filters
Bound the stream before turning logs into debugging context.
Logs answer what a workspace emitted during a known window. The default handoff should name the source, severity, row count, and start and stop times instead of dumping the whole runtime stream.
--level <level>Narrow noisy streams to debug, info, warn, or error before copying output into a handoff.
--limit <n>Keep the result bounded so the terminal view stays reviewable and does not turn into a full log export.
--since <time> --until <time>Use an explicit start and stop time when a failure happened during a known review or agent run.
Since and until examples
Use explicit windows for reviews, recent handoffs, and startup checks.
The same command shape works with absolute timestamps or relative windows. Keep --until present so everyone knows where the query stops.
envforge logs signed-links --source api --level error --limit 50 --since 2026-06-30T16:00:00Z --until 2026-06-30T17:00:00ZUse absolute timestamps when a reviewer or agent gives you a precise failing hour.
envforge logs signed-links --source worker --level warn --limit 100 --since 2h --until nowUse a relative window for a current debugging handoff while still bounding the end of the query.
envforge logs signed-links --source web --level info --limit 200 --since 2026-06-30T15:45:00Z --until 2026-06-30T16:10:00ZUse a narrow startup window when readiness changed around deploy, boot, or wake events.
Handoff boundary
Workspace logs are useful after they are filtered and reviewed.
Unlike command receipts, log lines may include application context. Treat filtered logs as debugging material that should be reviewed before it leaves the authenticated workspace context.
filtered log linesSource, level, timestamp, and the bounded message lines needed to understand the workspace behavior.
Debugging starts from the period and component someone can reproduce.source / level / limit / windowApply source, level, limit, since, and until before sharing log output outside the operator context.
Handoffs stay short enough for issues, PRs, and agent prompts.application dataLogs can contain application context, so inspect output before pasting it into a public review thread.
Workspace logs remain useful without widening access to private runtime details.