Skip to content

Set a Zed Agent Montage read boundary before research

Zed Agent can combine project context with remote tools, but the presence of a context server is not permission to mutate research records.

Integrations

How do I set a Zed Agent Montage read boundary before research?

Zed Agent can combine project context with remote tools, but the presence of a context server is not permission to mutate research records. Create an explicit workspace-status checkpoint in the intended conversation without extending that approval to external agents. Name Zed Agent as the caller and signals_status as the allowed effect. A working context server supplies a remote interface, not permission to mutate retained research or certify independently configured agents in the editor.

01 / CONFIGUREOne remote endpointUse this client's documented HTTP setup
02 / AUTHORIZEYour workspace accessUse a supported sign-in or credential flow
03 / VERIFYRun signals_statusCheck a real workspace response
Copyable task-specific request
Help me set a Zed Agent Montage read boundary before research. State that repository context is not approval for retained Montage changes. Report the verified read result or blocking condition, then await a new research instruction. No writes.
01 / Integrations

Separate project and workspace authority

State that repository context is not approval for retained Montage changes. The current conversation should inspect only workspace readiness and leave watchlists or audience operations as proposals. The brief can allow a workspace-status explanation while explicitly excluding saved research changes, preserving a concrete remote effect rather than vague safety language.

02 / Integrations

Check the editor-owned connection

Confirm this conversation is using Zed Agent’s Montage context server. Do not accept an external agent’s tool list or terminal output as proof that the selected editor connection is authorized. If the selected conversation belongs to an external agent, redirect the diagnostic to that agent’s owner instead of editing Zed settings speculatively.

03 / Integrations

Name the permitted read

Ask for signals_status and exclude writes explicitly. If the tool is missing, investigate server availability rather than inviting the agent to test any advertised operation. Use the status definition’s advertised contract and avoid inventing parameters to select a different workspace when consent associated the wrong account.

04 / Integrations

Inspect status evidence

Review the actual workspace and coverage returned by Zed Agent. Keep authorization errors distinct from a model’s interpretation and do not treat missing coverage as permission for additional operations. A returned limitation should remain visible without asking the assistant to fill missing coverage through other operations under the original read-only permission.

05 / Integrations

Stop at the handoff

Report the verified read result or blocking condition, then await a new research instruction. A successful editor-owned check does not certify ACP parity or grant standing approval for workspace writes. The final proposal can name a desired next action while remaining unexecuted; connection readiness and permission for retained-workspace effects are independent decisions.

Keep the boundaries clear.

  • Use the status definition’s advertised contract and avoid inventing parameters to select a different workspace when consent associated the wrong account.
  • The final proposal can name a desired next action while remaining unexecuted; connection readiness and permission for retained-workspace effects are independent decisions.

Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.

Primary references

Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.

Know what social media shows about you.
Start with a question.

Get started
montage