Guides
Working with agents
Keep the tools you use. Give them a better starting point.
Mindslice is not a separate coding agent. Your existing agent remains responsible for understanding the task, reading context, and making changes.
Mindslice makes relevant knowledge available locally as Markdown and offers optional integration guidance to help the agent discover it.
Plan from a homebase
For changes that span repositories, start your agent in the homebase. Use it as the shared place to understand the product, compare project responsibilities, and propose a plan—not as a directory for application code.
Read the shared knowledge and inspect the homebase's known projects.
Resolve the local checkouts relevant to this feature.
Propose which repositories should change and why.
Wait for approval before implementation.Use mindslice projects list --json and mindslice projects resolve --json from the registered homebase to inspect known projects and local checkout resolution. See the home-repo workflow for the discovery boundaries.
Move implementation into the chosen application directories using your agent’s normal workflow and permissions. Read each repo’s instructions and use its own build and test commands. Mindslice discovers local paths; it does not launch agents or coordinate their execution.
You can also start a session directly inside an application. Its selected context view provides access to shared knowledge without requiring every session to begin at home.
Read before building
Start a meaningful change by asking your agent to find the relevant shared knowledge:
Read the homebase pages relevant to this feature.
Identify the product constraints and architecture decisions
that should guide the implementation. Flag gaps before guessing.An agent with terminal access can inspect selected knowledge from the application directory:
mindslice knowledge tree
mindslice knowledge search "your topic"Use mindslice knowledge read with a path returned by the tree or search. Long pages and result lists can be paginated; follow the command’s continuation hints instead of assuming the first response is complete.
Install guidance intentionally
Interactive project setup offers optional instructions, skills, and reminder hooks. Review the files and permissions before accepting them.
To review integration updates for an existing project:
mindslice integration updateThis is an explicit update operation, not a read-only command. Preserve your custom instructions and inspect the proposed changes.
Agent environments and integrations vary. Local Markdown is the common foundation; do not assume every agent or platform has been validated.
Keep durable knowledge out of chat
A useful session often produces something worth keeping: a clarified constraint, a decision, or an explanation that will help the next project.
Ask for a focused documentation proposal rather than automatically turning every implementation detail into permanent knowledge:
Summarize what changed and which shared knowledge may now be
out of date. Propose a focused update for review.
Do not edit the homebase until I approve it.After approval, update canonical homebase pages through your chosen maintenance workflow. Don’t turn a generated context view into a competing source of truth.
Treat context as evidence, not certainty
Shared knowledge can be incomplete or stale. Compare claims with the relevant source code, distinguish intent from implementation, and flag contradictions.
Mindslice helps put knowledge within reach. It does not guarantee that an agent reads every page, interprets it correctly, or automatically keeps documentation accurate.
Browse the same knowledge yourself
From a connected project:
mindslice readerThe local read-only browser reader includes a directory tree, Markdown pages, search, and a heading outline. Open the private launch URL printed by the command.
Reader sessions expire after eight hours or a service restart. Run the command again for a new session, and don’t share the launch URL.
