GovTribe

Tune GovTribe AI

Use the composer Tune drawer to manage global Intelligence and response length preferences, custom instructions, memories, conversation recall, and GovTribe data access.

The Tune drawer brings GovTribe AI's model, reasoning, response length, custom instructions, and context controls into the composer. These are personal preferences for future GovTribe AI responses, so you can open the same drawer from a new or existing conversation.

Open Tune GovTribe AI

Open GovTribe AI. Start a new chat or open an existing conversation.

Select Tune GovTribe AI. Use the sliders icon in the composer toolbar.

Choose a Tune row. Each row shows the current selection before you open its detailed view.

Open Tune from the composer, then choose the preference you want to review or change.
Tune rowWhat it opens
IntelligenceYour model and reasoning defaults. The row summarizes both selections.
Response lengthHow concise or expansive future responses should be.
Custom InstructionsStable information about you and instructions for how GovTribe AI should respond.
Memory & contextMemories, Full Conversation Recall, and Access GovTribe Data controls.

Connected tools stay under the plug button in the composer. See Manage connected tools.

Choose Intelligence and response length

Use Intelligence to choose GPT-5.6 Sol, GPT-5.6 Terra, or GPT-5.6 Luna and a None, Low, Medium, or High reasoning level. Use Response length to choose Low, Medium, or High.

Intelligence combines the default model and reasoning controls in one Tune view.

Intelligence and Response length changes are global preferences. The latest selections apply to the next ordinary message you send in new and existing chats. If GovTribe AI is already responding, that active response, its reconnects, and its recovery attempts keep the settings they started with.

A conversation started from a GovTribe record or routed workflow can use launch-provided settings for its first response. Later ordinary messages use your current Tune defaults. See Create a conversation and Manage conversations.

An automation has its own reasoning level for its runs, including Run now tests. That saved level takes precedence while the automation and its tools are running. If you open the generated conversation and send a follow-up message yourself, that ordinary turn uses your current Tune Intelligence and Response length preferences. See Automations.

Choose memory and context settings

The Memory & context view controls how GovTribe AI can use durable personal context.

SettingWhat it does
MemoriesAllows GovTribe AI to save and reuse durable preferences, facts, and work context. Turning this off deletes previously saved memories and prevents new memories from being created. See GovTribe AI memories for review and editing guidance.
Full Conversation RecallAllows GovTribe AI to search prior AI conversations when useful. New conversations do not automatically include old conversation snippets.
Access GovTribe DataAllows GovTribe AI to use permitted GovTribe activity and profile context for personalization.

Use custom instructions

Custom instructions are stable guidance GovTribe AI can include in each conversation.

FieldWhat to include
What would you like GovTribe AI to know about you?Stable facts about your role, company, pursuits, agencies, vendors, terminology, or responsibilities that are useful for GovTribe AI.
How would you like GovTribe AI to respond?Preferences for tone, length, structure, formatting, language, or working style.

Each custom-instruction field is limited to 1,000 characters. GovTribe AI follows your response-style instructions unless they conflict with system behavior, safety requirements, or the specific prompt you send.

Select Save to keep changes and return to the main Tune view. Back, Cancel, or closing the drawer discards edits that you have not saved.

Examples for what GovTribe AI should know

Use the first field for stable context you want GovTribe AI to remember across conversations. Good instructions describe your role, market focus, company capabilities, preferred record types, pursuit posture, and recurring constraints.

Use the copy button on any example, then adjust the wording for your company, markets, and responsibilities.

Capture manager

I manage capture for a mid-sized federal IT services firm. We focus on cloud migration, cybersecurity, help desk, and data modernization work for civilian agencies. Prioritize recompetes, incumbent context, contract vehicles, set-aside posture, likely competitors, and near-term next actions.

Business development lead

I lead business development for a small business contractor with strong past performance in professional services and program support. We prefer prime opportunities under $50M and teaming opportunities on larger IDIQs. Highlight agency fit, relationship signals, and partner angles.

Proposal manager

I support proposal planning and compliance. When I ask about an opportunity, help me find evaluation factors, instructions, submission deadlines, required attachments, compliance risks, and draft outline sections that map to the solicitation language.

Pricing analyst

I work on pricing strategy. I care about labor categories, place of performance, wage geography, ceiling rates, awarded line-item evidence, incumbent pricing clues, and assumptions that should be reviewed before leadership sees the estimate.

Agency account lead

I manage our account strategy for selected federal buyers. Prioritize buying patterns, expiring awards, active vehicles, key offices, likely recompetes, and how new opportunities relate to our existing agency plan.

State and local seller

I focus on state and local technology opportunities. Give extra attention to jurisdiction context, buyer history, related awards, line-item pricing evidence, incumbent vendors, and whether the opportunity looks realistic for a vendor like us.

Do not use custom instructions for one-time details that only apply to the current prompt, such as a single opportunity, a temporary deadline, or a specific document you only need once. Put those details in the conversation prompt or project instead.

Examples for how GovTribe AI should respond

Use the response field for answer structure, tone, length, and formatting preferences.

Executive summary first

Start with the recommendation and the top three reasons. Put supporting evidence in a table after the summary.

Capture scoring

When reviewing opportunities, organize the answer by Fit, Competition, Timing, Vehicle or Set-Aside, Risks, and Recommended Next Action.

Evidence discipline

Separate confirmed GovTribe evidence from assumptions. If evidence is missing, say what is missing and how to verify it.

Proposal-ready output

Use proposal and capture language. Avoid generic sales copy. When drafting win themes, tie each theme to a customer need, proof point, and likely evaluation factor.

Team handoff

End with action items for BD, capture, proposal, and pricing teams when those roles are relevant.

Concise research notes

Use short bullets and tables. Avoid long narrative unless I ask for a memo or briefing.

How custom instructions shape responses

Custom instructions work best when they name the structure you want GovTribe AI to use repeatedly. These examples show how a reusable instruction can change the shape of future answers.

Capture decision reviews

Instruction:

When reviewing opportunities, start with a pursue / watch / no-bid recommendation, then show Fit, Timing, Competition, Vehicle or Set-Aside, Risks, and Next Action.

Example response shape:

Recommendation: Watch

Top reasons:
- Fit is strong for cloud and help desk work.
- Timing is early, with no solicitation package yet.
- Competition risk is unclear because incumbent evidence is incomplete.

Evidence table:
| Area | What GovTribe found | What it means |
| Fit | The requirement includes cloud operations support. | Strong alignment with our delivery history. |
| Timing | The notice is pre-solicitation. | Start capture research, but wait for full requirements before a bid decision. |
| Competition | Incumbent evidence is incomplete. | Confirm predecessor award and likely competitors. |

Evidence-first research

Instruction:

Separate confirmed GovTribe evidence from assumptions. If the record does not support a claim, put it under Open questions instead of stating it as fact.

Example response shape:

Confirmed evidence:
- The buyer is the Department of Veterans Affairs.
- The notice is tied to facilities support.
- The due date is listed in the opportunity record.

Assumptions:
- This may connect to prior sustainment work, but the record does not confirm the incumbent.

Open questions:
- Confirm whether the current incumbent is still performing the predecessor work.
- Check whether the buyer has released attachments that change the scope or evaluation criteria.

Proposal team handoffs

Instruction:

When I ask about a solicitation, organize the answer for a proposal team: compliance items, evaluation factors, submission controls, pricing items, attachments, risks, and writer actions.

Example response shape:

Proposal handoff:
| Area | Action | Owner |
| Compliance | Confirm page limits and required forms. | Proposal manager |
| Pricing | Check labor categories and place of performance. | Pricing lead |
| Technical | Map requirements to draft sections. | Technical lead |
| Attachments | Review all amendments and file changes. | Proposal coordinator |

Risks:
- Submission instructions may differ between the notice text and attached files.
- Pricing assumptions need review before leadership approval.

Manage memories

When memories are enabled, you can ask GovTribe AI to save stable facts, preferences, and long-term working context for future conversations. Use direct wording such as remember that..., save this as a memory..., or do not forget that....

When Memories is active, open Memory & context and select View and manage memories →. Tune closes and the existing Memories drawer opens, where you can review a Summary (Beta) when credits are enabled, inspect the List of active memories, open memory details, and forget individual memories. The management action is hidden while Memories is disabled. See GovTribe AI memories for examples, strength labels, correction actions, and guidance on what should or should not be remembered.

Use uploaded user files

GovTribe AI can work with User Files that are available to your workspace and visible to your account. These can include files your team uploaded, files associated with pursuits, and files generated or saved from prior GovTribe AI work.

This lets you reuse past work instead of starting every prompt from scratch. For example, you can ask GovTribe AI to find a past capability statement, proposal outline, debrief, pricing note, market analysis, or pursuit document, then adapt that material for a current opportunity.

File sourceHow GovTribe AI can use it
Uploaded workspace filesSearch file names, descriptions, summaries, and extracted text when available.
Pursuit-linked filesBring prior pursuit context into a new opportunity review, bid / no-bid discussion, or proposal workflow.
Generated AI filesReuse documents, spreadsheets, charts, or summaries created in earlier GovTribe AI conversations.
Saved research filesCompare older market research, customer notes, or capture material against a new record.

Strong prompts include:

Find our past capability statements for cybersecurity work and adapt the strongest language for this opportunity.
Use prior pursuit documents about this agency to identify likely win themes for the current solicitation.
Compare this opportunity against our uploaded past-performance files and flag the best matching examples.
Find the proposal outline we created last quarter and update it for this new requirement.

User-file access follows GovTribe workspace permissions. If a file is in another workspace, hidden from user-file discovery, deleted, not indexed, or not accessible to your account, GovTribe AI may not be able to find or use it. For direct file management, use User files.

Upload company assets for AI reuse

Upload the asset. Add the file from User Files, or save a generated GovTribe AI file to the workspace when that option is available.

Add useful context. Use clear file names, descriptions, tags, pursuit links, or project context so the asset is easier to find later.

Ask GovTribe AI to use it. Name the file type, topic, pursuit, agency, or tag in the prompt, then ask for the specific output you need.

Review the source. Check the uploaded file and the generated answer before reusing language in a proposal, customer communication, or internal decision.

For the file-management side of this workflow, see User files. For capability boundaries and verification guidance, see GovTribe AI capabilities and limits.

How Tune preferences affect GovTribe AI

Tune preferences can affect multiple parts of GovTribe AI.

AreaPossible effect
New and existing conversationsFuture ordinary turns can use your current Intelligence, Response length, allowed memories, custom instructions, user files, and GovTribe activity context. When Full Conversation Recall is enabled, GovTribe AI can search prior AI conversations on demand when useful.
Recommended promptsStarter prompt cards can be generated from user and workspace context.
Daily BriefingThe briefing depends on opt-in personalization and can use allowed user, workspace, capture, and opportunity context.
AutomationsAutomation responses can reflect the selected prompt, skill, connected-tool configuration, project context, relevant user files, and available context settings. Automatic runs use the reasoning level saved on the automation; later ordinary messages you send use your current Tune Intelligence and Response length preferences.

Tune preferences do not remove the need to verify important information. Review AI output against the underlying GovTribe records before acting on critical details.