Handoffs & environments
Move the work forward. Keep the environments separate.
Let an engineer and their agent investigate where the access exists. Give a development agent the findings it needs to continue somewhere else.
A familiar situation
The work crosses a boundary.
A customer reports a problem that needs investigation against production data. An SRE oversees a trusted agent on a machine with VPN access. Once the cause is understood, implementation can happen on a separate machine that has no production access.
Operations and development can work together without giving every stage the same access or level of supervision.
Investigate together
Operations engineer + trusted agent
Production access
Human oversight
Shared in Markbase
Customer issue → development brief
- Findings and decisions
- Relevant code reference
- Clear next steps
Prepared and reviewed for handoff
Continue independently
Development agent + shared brief
Isolated environment
No production access
The workflow
How the work moves forward.
01
Investigate together
An engineer supervises an agent in the environment with production access. They establish the facts, test explanations, and decide what needs to change.
02
Prepare the handoff
Ask the agent to save findings, decisions, open questions, and the relevant code reference in Markbase. Review the material selected for sharing.
03
Continue in isolation
On the development machine, ask another agent to read the handoff and use the referenced code. Implementation can proceed with the autonomy your team has chosen.
04
Bring the result back
Save implementation notes, test results, and remaining questions so the responsible engineer can review the work with the original investigation in view.
What this makes possible
A better way to divide the work.
- Access fits the task
- The development environment can work from the findings without receiving production credentials or a production connection.
- Oversight where it matters
- Keep a person involved in the sensitive investigation and choose a different level of autonomy for implementation.
- A useful bridge between teams
- The next engineer and agent can follow the reasoning instead of asking operations to reconstruct it.
How responsibilities are shared
Your infrastructure provides the isolation and access controls. Markbase carries the context you choose to share; it does not sanitize findings, transfer permissions, or enforce an approval workflow.
Keep exploring
More ways to work together.
Shared team knowledge01
Make one person’s learning useful to the whole team.
Keep decisions, lessons, and project context available to the next person and their agent.
Explore the workflow
Onboarding & standards02
Give every new project a better starting point.
Use workspace templates to share useful structure, guidance, and established practices.
Explore the workflow