Skip to content

Conversation

@zerone0x
Copy link
Contributor

Summary

Fixes #6489 #8094

When using opencode run --attach <server> --agent <agent>, the CLI crashes with:

instance: No context found for instance
    at use (src/util/context.ts:16:21)
    at directory (src/project/instance.ts:42:20)
    ...

Problem

The Agent.get() function requires Instance context that is established by bootstrap(). In attach mode, bootstrap() is never called since we connect to a remote server. This causes the crash when trying to validate the agent locally.

Solution

Skip local agent validation when in attach mode by adding an early return. The remote server handles agent validation instead.

if (args.attach) return args.agent

What does this PR do?

Adds a check to skip local agent validation when the --attach flag is used, allowing the remote server to handle agent validation.

How did you verify your code works?

Reviewed the code logic and confirmed the fix aligns with the root cause analysis from #6489. The change is minimal and focused - it only adds an early return for the attach mode case.


🤖 Generated with Claude Code

When using `opencode run --attach` with the `--agent` flag, the CLI
would crash with "No context found for instance" because Agent.get()
requires the Instance context that is only available after bootstrap().

In attach mode, bootstrap() is never called since we're connecting to
a remote server. This fix skips local agent validation in attach mode,
allowing the remote server to handle agent validation instead.

Fixes anomalyco#6489 anomalyco#8094

Co-Authored-By: Claude <noreply@anthropic.com>
@github-actions
Copy link
Contributor

The following comment was made by an LLM, it may be inaccurate:

No duplicate PRs found

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Specify an agent when attaching to server fails

1 participant