Skip to main content
The Knowledge tab controls durable company context for the project. It separates reviewed profile facts from retrieved Library material and short-lived workflow memory.

​
Open Knowledge

  1. Open a project and select Library
  2. Select the Knowledge tab
Project members can read the profile, proposals, and memory. You need project management permission to edit the profile or review proposals.

​
Company profile

The Knowledge Profile has four fields:
  • Positioning
  • Products / services
  • Tone
  • Saved instructions
DevTune injects these fields verbatim into every managed-agent brief. The profile is not selected by semantic relevance, so keep each field current and project-specific. Project managers can select Edit on a field and save a direct change. Direct manager edits apply immediately; they do not enter the proposal queue.

​
Review proposed changes

Crawl differences and managed-agent run learnings can propose a profile change. They cannot update the profile silently. Each proposal identifies its source, target field, proposed value, date, and available provenance such as a page URL or agent workflow. A project manager can:
  • Approve a Pending proposal to apply its value to the target profile field.
  • Dismiss it without changing the profile.
  • Restore a Dismissed proposal to Pending review.
Approved and Dismissed proposals remain under Reviewed proposals. An Approved proposal cannot be restored; restoration is the reverse action for a Dismissed proposal.

​
Workflow memory

A managed-agent run can write a concise, project-specific learning back to the Library. Workflow memory:
  • records the originating run and workflow as provenance
  • is created as a Library Memory item
  • expires 90 days after it is written
  • follows the same Current/Superseded version and Available to agents controls as other Library items
The Knowledge tab shows each memory’s creation and expiry dates. Find the same Memory item in the Library tab to inspect its content and run provenance. Turn Available to agents off when the memory should remain visible to people but must not enter future agent prompts. Expired memory is excluded from retrieval.

​
API and MCP access

  • GET /projects/{projectId}/knowledge returns the profile and paginated Pending, Approved, and Dismissed proposals. It requires library.read.
  • PATCH /projects/{projectId}/knowledge applies a deliberate edit to one profile field. It requires library.write.
  • POST /projects/{projectId}/knowledge/proposals/{proposalId} accepts approve, dismiss, or restore. It requires library.write.
  • devtune_get_knowledge_profile, devtune_update_knowledge_profile, and devtune_review_knowledge_proposal expose the same operations through MCP.
Use the direct update operation only for a deliberate, human-authored change. System observations and agent learnings still belong in the proposal review flow. See the REST API endpoint list and MCP server guide.

​
Next steps