Use Indra alongside the coding agent and editor you already use. Indra can supply project context, the handbook, and connected capabilities. Your coding host supplies the repository workspace, editor, terminal, and code-execution tools.
This guide does not require a separate Vision IDE. Start by connecting Indra to your agent host.
Complete a coding task
-
Open the right workspace
Open the intended repository and ask the agent to read its applicable instructions, branch state, and existing changes. Preserve unrelated work. A project description in connected records is useful context; it does not replace the current repository contents.
In a terminal, you can inspect Indra's guidance yourself:
Shell indra --root "$indra_root" instruction indra --root "$indra_root" handbookUse your existing Vault path. Through MCP, the corresponding tools are
indra.instruction({})andindra.handbook({}). Read the relevant workflow chapter before changing product behavior. -
State the requested change and delivery stage
For example:
Implement the behavior described in this handbook page for the selected repository. First establish the current user flow, then make the smallest coherent change. Preserve unrelated edits. Verify the affected behavior and return the diff and test results; stop at a local reviewed change.
Other requests have different completion criteria:
Request Expected work Clarify or correct the handbook Update the canonical documentation and record relevant implementation gaps. Implement a handbook workflow Change the product so the requested behavior matches the intended experience. Investigate a mismatch Establish expected and observed behavior and provide the requested diagnosis or repair. Deploy or release an implemented change Follow the repository's release process and verify the delivered destination. A documentation edit alone does not automatically trigger code changes or a release. A product defect should not be hidden by weakening the handbook to describe it as acceptable.
-
Recover context, then inspect the code
Use Indra's search or live actions for relevant decisions and source material. Keep the actual account, project, and period scoped to the task.
Then use the host's repository tools to trace the requested behavior:
- Where the person or agent starts.
- The state and identity carried between steps.
- The operation that changes the state.
- The result the user can inspect.
- The recovery path when a dependency fails.
This trace guides implementation. It is not a replacement product specification.
-
Edit and verify in the coding host
Use the host's available code tools to edit the relevant files and run the repository's applicable checks. Choose checks that exercise the changed behavior. For a visible interface change, inspect the actual flow and rendered state as well as the code.
If a check fails, determine whether it exposes the requested defect, a new regression, or an unrelated baseline problem. Record a blocked check honestly. A build passing does not establish that the user can complete the workflow.
Indra's tools do not make an unavailable editor, terminal, OS permission, or provider operation available. Identify that particular missing capability and continue other useful work where possible.
-
Deliver at the requested stage
Review the diff against the goal, preserve the repository's working agreements, and report what changed and how it was checked. Link the actual diff, artifact, or deployed result that exists.
A local edit is not a commit; a merged change is not a published package. Verify an external delivery at its destination before reporting it complete. If another agent will continue, save the current workspace state and remaining step using Continue work.