Magistr stores project records that a connected coding agent can read and update. These records describe planned work, decisions, execution, and evidence. Your source files remain in your repository.
Plan and execution
| Record | What it means |
|---|---|
| Project | The shared identity and settings for the work you are building. |
| Roadmap | Deliverables, their priorities, dependencies, and status. |
| Workstream | A named area of the roadmap, such as account access or reporting. Some command options call this a track. |
| Chunk | One deliverable with acceptance criteria and dependencies. |
| Objective | The result an active work plan is trying to achieve. It can serve a chunk or a direct request. |
| Task | One step in that work plan, such as investigating a failure or implementing a change. |
| Action | A recorded account of work performed on a task. |
A project can have several workstreams. Each contains chunks. When a chunk is implemented, its objective and task plan explain how it will be delivered. Completing one task does not by itself complete the chunk.
Priority expresses importance. A dependency says another chunk must finish first. A pending chunk may therefore be waiting, while a ready chunk has satisfied its prerequisites.
For example, a reporting feature might need a data import before it can generate reports. The import is a dependency. Giving reports a higher priority does not remove that requirement.
Decisions and evidence
Recorded reasoning is an explanation deliberately saved by the agent: a question, findings, sources, alternatives, a decision, and its limits. An investigation may branch from an earlier question and feed into a later conclusion. Revisions preserve the earlier finding and explain what changed.
A pin makes an important finding easy to retrieve. A reasoning checkpoint reviews the reasoning record and open questions; it is not a backup of source files.
A check records verification. An executed command has its command, output, exit status, and observed inputs. A written review records what was inspected. A passing test and a reviewed screen answer different questions.
An artifact links to a result, such as a file, commit, pull request, or deployment. An artifact link alone does not establish that its contents passed verification.
A signal is saved feedback, a question, an idea, or a reported problem. Investigation can lead to a linked roadmap chunk, a dismissal, or a decision to wait.
Sessions and saved work
A session is a conversation with an agent. Magistr’s project records can outlive that conversation and be read by another connected agent.
| Information | What carries over |
|---|---|
| Roadmap, saved reasoning, work plans, checks, feedback | Available through Magistr for the same project. |
| Source files and commits | Available through the repository and working copy. |
| Conversation history | Kept by the host that recorded it; Magistr-managed conversations have their own saved history. |
| Model, authentication, and host permissions | Belong to the agent or to the settings used for a particular launch. |
Connecting a different agent does not translate the previous agent’s full chat transcript or transfer its model settings. Magistr does not automatically copy every chat message or reveal a model’s private internal thinking.
Ask a new session to read the saved work and inspect current source before continuing. Earlier verification can become stale when the relevant source, configuration, or environment changes.
Source tools
Magistr’s source tools search, read, and change files in a working copy. Edits can check that a file still matches the version read. Supported syntax checks reject edits that introduce parse errors. Changes made through these tools are journaled; undo reports conflicts with later edits.
These protections apply to those tools. They do not replace tests, Git, code review, or backups, and they do not sandbox every command an agent can run.
Where the records live
Project setup and the source-change journal are stored under the project’s
.magistr/ directory. Workflow records and Magistr-managed conversation
history also use user-level data directories. Copying only the repository may
leave those records behind. Storage and backups lists the
locations and the limits of moving a project.