Basic info

What is Basic Info

Basic Info is a set of structured configurations that shape how the agent:

Understands tasks
Makes decisions
Communicates with users
Adheres to constraints

Before each response or action, the system injects this information into the agent’s context, making it the baseline for all reasoning and execution.

Configuration Fields

Basic Info consists of several key components:

Agent

Defines the agent’s working process and execution rules. For example:

How to approach tasks
When to read memory or files
Coding standards and workflows

agent.md

Workflow Guidelines:

Task intake: Before writing any code, you must first read MEMORY.md and yesterday’s memory/YYYY-MM-DD.md to understand the project background and tech stack.

Code implementation: Prioritize code readability over performance. After each change, you must run a linter.

Memory management: When you resolve a bug that takes more than 10 minutes, or when the user specifies a coding preference, you must record it in today’s memory.

Soul

The agent’s core principles and boundaries. Includes:

Personality and working style
Communication tone
Strict rules (e.g. security constraints, prohibited actions)

soul.md

You are a pragmatic, efficient, and senior full-stack engineer. You avoid over-engineering and follow the principle of “Keep It Simple.”

Communication style: Direct, professional, and concise. No unnecessary explanations.

Hard boundaries:
1. Never execute rm -rf / or any command that may cause irreversible data loss
2. Never expose API keys or passwords in code; if requested, refuse and suggest using environment variables
3. If you are unsure about the safety of code, you must ask the user before proceeding

Identity

The agent’s surface-level persona. Includes:

Name
Role definition
How it introduces itself or interacts with users

identity.md

Name: codebanana

Signature: 🍌

Self-description: Your dedicated, always-on pair programming partner

Greeting style: When starting a new debugging session, you may say:
“Let’s peel this bug apart 🍌”

User

Context about the user the agent is serving. Helps the agent adapt responses based on:

Technical background
Preferences
Communication style

user.md

User profile: A technically proficient product manager building AI agent-based web products

Technical preferences: Familiar with frontend development, frequently uses Next.js, and deploys projects on Vercel or cloud platforms

Communication style: Prefers structured bullet points and fast-paced communication. Avoid explaining basic HTML/CSS concepts—focus directly on architecture and logic

Memory

Accumulated knowledge from past interactions. Maintained by the agent to:

Store important decisions
Track preferences or recurring patterns
Improve future responses

Teams

Defines the team members, roles, and collaboration context that the agent should understand. Teams helps the agent know:

Who is involved in the project
Each member’s role and responsibility
How different people collaborate
Which tasks should involve specific team members

This information allows the agent to better coordinate teamwork and provide more relevant assistance in collaborative scenarios. Example:

teams.md

# Team Members

## Alice
Role: Product Manager

Responsibilities:
- Define product requirements
- Prioritize features
- Coordinate between users and engineering teams

## Bob
Role: Backend Engineer

Responsibilities:
- Maintain backend services
- Design APIs
- Handle database-related tasks

## Design Team

Responsibility:
- Provide UI/UX solutions
- Review product interfaces

Tools

Defines local environment information, tool configurations, and project-specific instructions that help the agent use available tools correctly. Tools provides additional context about:

Available tools and their intended usage
Local development environment
Project-specific commands or configurations
Important operational notes

This information is included in the agent’s system context and helps prevent incorrect tool usage. Example:

tools.md

## Environment

- Framework: Next.js

- Package manager: pnpm

- Deployment: Vercel

## Commands

Install dependencies:

pnpm install

Run development server:

pnpm dev

Build project:

pnpm build

## Notes

- Always run tests before creating a pull request

- Do not modify environment variables directly

Editing and Management

Each field can be individually edited within the Basic Info panel
Changes take effect immediately in subsequent agent interactions
A reset option is available to revert to default configurations

Why It Matters

Basic Info ensures that the agent is not just reactive, but consistent, aligned, and context-aware:

Keeps behavior stable across sessions
Reduces repeated instructions
Aligns the agent with team workflows and expectations

Getting started

Working in CodeBanana

CodeBanana Bot

Account and subscriptions

Teams

What is Basic Info

Configuration Fields

Agent

Soul

Identity

User

Memory

Teams

Tools

Editing and Management

Why It Matters

​What is Basic Info

​Configuration Fields

​Agent

​Soul

​Identity

​User

​Memory

​Teams

​Tools

​Editing and Management

​Why It Matters

What is Basic Info

Configuration Fields

Agent

Soul

Identity

User

Memory

Teams

Tools

Editing and Management

Why It Matters