The home-repo pattern, connected to your projects

One home for knowledge.
Context for every repo.

Give your agents a shared place for product decisions, architecture, and working conventions. Mindslice connects that homebase to your application repos—so you can plan across the system and build with the right context in each project.

Local CLI + service. Works with your existing agent.

A common thread.

A shared field of fine lines opens into three flowing ribbons: shared knowledge taking different forms.Reduced motion

Plan from home.
Build in the right repo.

A home repo gives your agents a shared starting point. Add each project’s purpose, responsibilities, and boundaries so your agent can compare where work belongs—then verify in the relevant repositories. Mindslice also makes the right shared knowledge available inside each connected project.

See the system from your homebase

Keep shared docs and coordination outside any single application. List the homebase’s known projects and resolve their local checkouts before deciding where a change belongs.

Plan with your agent
Read the shared architecture and project responsibilities. Which repositories own this feature? Verify against their instructions and code, then propose a plan before changing anything.

Keep context close to implementation

Build in the application repo, with its own instructions and tools. Selected local Markdown brings shared decisions into reach without another set of docs to maintain.

Build with your agent
Read this project’s shared context and local instructions. Implement the agreed change here, then propose any shared documentation updates for review.
Use the home-repo workflow

Shared at the source. Specific to the project.

A web app and an API can use the same homebase without receiving the same documents. Switch projects to see how one source supports different work.

About project context
Illustrative example
Show context for

Your homebase

knowledge/
  • product/overview.md

    Who the product is for and what it should do.

  • architecture/system.md

    System boundaries and the decisions behind them.

  • conventions/development.md

    The development practices both projects follow.

One source of truth, separate from your application code.

Available to the web app

web-app/

The agent can read these selected pages locally:

  • product/overview.md
  • conventions/development.md

The web app gets product context and shared conventions. The architecture page stays out of this project’s view.

2 of 3 documents selected

Available to the API

api/

The agent can read these selected pages locally:

  • architecture/system.md
  • conventions/development.md

The API gets architecture context and the same shared conventions. The product page stays out of this project’s view.

2 of 3 documents selected

Selection keeps context relevant. It is not an access-control boundary.

Connect your first project.

Start with your existing home repo or a new Markdown folder. Connect one application, then add others as you need them.

Full setup guide
  1. Install Mindslice

    On macOS or Linux, use Homebrew. For other installations, download an archive.

    Terminal
    brew install mindsliceai/tap/mindslice
  2. Start the local service

    This manages your homebases and project connections. It keeps running after you close the terminal.

    Terminal
    mindslice service start
  3. Register your homebase

    Use your existing home repo or a separate knowledge folder. Replace the example path and choose Home / homebase in setup.

    Terminal
    mindslice init /path/to/knowledge
  4. Connect an application

    From your application folder, choose Application project, select the homebase, and review which pages to include.

    Terminal
    cd /path/to/your-project
    mindslice init .
    mindslice knowledge tree

Once connected, try asking your agent to read your product overview before its next task. Need help organizing a homebase?

A few practical details.

Mindslice is currently an experimental CLI and local service. These are the boundaries of the product you can use today.

View releases
Is Mindslice another coding agent?

No. Your existing agent does the thinking and building. Mindslice makes the relevant knowledge available as local Markdown and offers optional guidance to help the agent use it.

What does Mindslice add to a home repo?

The pattern works with plain Git and Markdown. Mindslice adds discovery of registered local projects, selected context views inside connected repos, and optional agent guidance. Your agent still plans and implements the work; Mindslice doesn’t clone projects or orchestrate agents for you.

Do I have to move my docs or use Git?

You can register an existing knowledge folder as a homebase. It can be a plain directory or a Git repository; keep it separate from application code. The files remain yours to read and edit.

Does my knowledge need to go to a cloud service?

The core local workflow doesn’t require a hosted retrieval service. The homebase lives on your machine, and connected agents read selected Markdown locally. Your agent’s own data-handling settings still apply.

Will Mindslice sync or publish changes for me?

Not in the current implementation. Ongoing remote sync, publishing, cloud accounts, and team administration are not implemented. Use your normal Git workflow for remote collaboration and publishing.