Skip to content

[Update / Cleanup] Context Engineering > Culture #274

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 17, 2025
Merged

[Update / Cleanup] Context Engineering > Culture #274

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 3 additions & 10 deletions concepts/culture/overview.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,9 +8,8 @@ keywords: [culture, culture management, culture sharing, cultural knowledge]
Imagine agents that learn from every interaction and share those learnings with each other.
A support agent discovers that customers prefer step-by-step solutions with code examples.
A technical writer agent learns that "Operational Thinking" produces better documentation.
These insights shouldn't be lost—they should become part of a shared culture that benefits all agents, forever.
These insights shouldn't be lost—they should become part of a shared culture that benefits all agents, forever. Culture turns these patterns into reusable rules your agents can follow from day one.

This is the power of Culture in Agno.

## How Culture Works

Expand Down Expand Up @@ -166,11 +165,8 @@ culture_manager.add_cultural_knowledge(response_format)

Cultural knowledge is stored in the database you connect to your agent. Agno supports all major database systems: Postgres, SQLite, MongoDB, and more. Check the [Storage documentation](/concepts/storage/overview) for the full list.

By default, cultural knowledge is stored in the `agno_cultural_knowledge` table (or collection for document databases). If this table doesn't exist, Agno creates it automatically.
By default, cultural knowledge is stored in the `agno_cultural_knowledge` table (or collection for document databases). A custom table name can also be configured. If this table doesn't exist, Agno creates it automatically.

### Custom Table Names

You can specify a custom table name for storing cultural knowledge:

```python
from agno.agent import Agent
Expand Down Expand Up @@ -227,13 +223,10 @@ Each cultural knowledge entry in your database contains the following fields:
| `agent_id` | `str` | ID of the agent that created it |
| `team_id` | `str` | ID of the team associated with it |

<Tip>
View and manage all your cultural knowledge visually through the [Culture page in AgentOS](https://os.agno.com/culture)
</Tip>

## Best Practices

1. **Start with Manual Seeding:** Define your core organizational principles, communication standards, and best practices upfront
1. **Start with Manual Seeding:** Define core organizational principles, communication standards, and best practices upfront
2. **Use Automatic Updates in Production:** Let `update_cultural_knowledge=True` handle the evolution naturally
3. **Review Periodically:** Check what cultural knowledge has accumulated and refine as needed
4. **Keep Culture Focused:** Culture should contain universal principles, not task-specific details
Expand Down