Skip to main content
In most AI tools, every conversation lives in the browser tab of the person who started it. When that person is on vacation, rolls off the matter, or simply closes the tab, the context is gone — and the next person has to rebuild the same reasoning from scratch. In professional services, where client work spans weeks or months and teams shift constantly, this is not just inconvenient: it is a hidden cost that compounds across every engagement. Parlé solves this by attaching context to the project, not the individual.

​
How shared context works in Parlé

Every conversation you have inside a project is stored at the project level and is immediately visible to every project member. When you send a message, your colleagues see it. When the AI responds, everyone on the team can read that response, quote from it, and build on it in the same thread or a new one. There is no “sync” step, no export, and no copy-paste into a shared document. The thread is the shared artifact. This means that the accumulated reasoning, the documents the AI surfaced, the drafts the team iterated on, and the conclusions reached all live in one searchable place for the life of the engagement.
The context belongs to the project, not the person. Leaving a project does not delete your messages — they remain part of the project record, attributed to you by name.

​
Standing instructions: agent.md

Thread history is context the team accumulates. agent.md is context you write down once, deliberately, and it is the single highest-leverage thing to set up on a new project. agent.md holds standing instructions for the agent — the equivalent of a project brief. Its contents are injected at the start of every conversation in the project, so nobody has to re-explain the client, the house style, or the ground rules each time.
1

Open Project Details

Scroll to the agent.md section.
2

Write the project's standing instructions

Useful things to include:
  • What the project is, who the client or stakeholder is, and what “done” looks like.
  • Conventions to follow — tone, terminology, document structure, file naming.
  • Where things live in the project’s files, and what to read before answering.
  • Anything the agent must never do, for example: do not share figures outside the approved deck.
3

Save

Each save creates a new version. The panel shows the current version number and when it was last updated.
Editing project details, storage, and agent.md requires Project Admin on this project, or Org Admin. Everyone else sees it read-only. Every edit is written to the audit log.
agent.md is project-scoped. Documents that are true for your whole firm — an expenses policy, a methodology, a staff handbook — belong in organization knowledge instead, where they reach every conversation in the organization and are quoted with a citation.

​
Onboarding to a project

When you join a project mid-engagement — whether you are a new hire, a lateral joining the matter, or a senior reviewer stepping in for the first time — you do not have to schedule a call to get up to speed. Open the project, scan the conversation list, and read the threads most relevant to your work. The threads show you:
  • What questions the team already asked and how the AI answered them, so you do not re-derive the same analysis.
  • Which documents the AI read and which sections it drew from, so you know what has been reviewed and what has not.
  • Where the team disagreed or iterated, because branches and edit history are preserved in full.
If you still have a question after reading, use semantic search to check whether it was addressed in a conversation you have not found yet before opening a new thread.

​
Continuity across team changes

Professional services engagements rarely end with the same team that started them. Associates cycle off, partners step in for closing, contractors join for a specific workstream. In a private-chat model, each departure takes a piece of the context with it. In Parlé, the thread stays. When a team member rolls off the matter:
  • Their messages remain in the thread, attributed to them by name and timestamp.
  • The AI responses they generated are still searchable and quotable.
  • Any files they uploaded or referenced stay in the project’s file store.
  • Their branches and drafts are preserved exactly where they left them.
The incoming team member reads the thread, gets current, and continues — without a knowledge-transfer meeting and without the risk that something important was only in someone’s personal chat history.

​
Best practices

Use a personal chat for exploratory or speculative work — rough drafts, quick experiments, ideas you are not sure will go anywhere. Personal chats are private by design and do not count against the project’s budget or conversation history.Promote a conversation to a project the moment it produces something the broader team needs: a research summary, a draft clause, a risk analysis, a recommendation. Once it matters to the engagement, it belongs in the project where everyone can see and build on it.
Open the project and use the Search bar on the Conversations tab. Type a keyword or describe what you are looking for in plain language — Parlé’s semantic search will surface relevant messages even if the exact words do not match.If you know roughly which conversation it was in, open that thread and use your browser’s Find (Ctrl+F / Cmd+F) to scan the visible messages quickly. For deeper searches across dozens of conversations, semantic search is faster.
Yes. Every message in a shared project thread shows the author’s name and avatar alongside the timestamp and the AI model used for that response. You can see at a glance whether a message came from a colleague or was the AI’s reply, which model generated it, and exactly when it was sent.This attribution is permanent and cannot be edited. It is part of the engagement record.