Skip to main content
Open Settings › Context in the project sidebar to manage the information DevTune uses about your company. This is the same company context that agents, prompt generation and suggestions read, and that API and MCP clients read and update as the Knowledge Profile. Project members can read context and proposals. You need project management permission to edit context or review proposals.

​
Company context and agent preferences

  • Company context describes your business, audience, and offerings. Agents, prompt generation, relevance checks, and recommendations use this same saved description.
  • Tone guides the voice and style of agent writing.
  • Instructions for agents sets project-specific preferences for recommendations, writing, and sources.
Company context replaces Brand Context in General and the separate Positioning and Products / services fields. Where previous descriptions differ, review the consolidation suggestion and resolve conflicting claims before saving. Previous descriptions remain in the suggestion’s provenance. Changes apply to future tasks. They do not rewrite existing outputs. Instructions guide model responses; they are not enforced controls. 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.

​
Memory

Memory items in the Library are notes you asked Dex to keep. Dex offers a memory in conversation, and it is saved only when a project member confirms it. Each memory:
  • records the conversation, run and saving member as provenance
  • expires 90 days after it is saved
  • starts with Available to agents turned on
Agent runs do not write memory. A run that finds the saved company context or agent preferences out of date proposes a change for review instead, as a Pending proposal.

​
API and MCP access

  • GET /projects/{projectId}/knowledge returns companyContext, agent preferences in profile, and paginated Pending, Approved, and Dismissed proposals. It requires library.read.
  • PATCH /projects/{projectId}/knowledge applies a deliberate edit to company_context, tone, or saved_instructions. The former positioning and products_services write fields are retired; legacy values remain readable for compatibility. 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