Character Interface

Complete reference for the IrisOS Character configuration interface.

Overview

The Character interface is the core configuration structure that defines an agent's identity, personality, capabilities, and behavior in IrisOS.

Schema Reference

Root Properties

Property
Type
Required
Description

name

string

Yes

The agent's display name

bio

string[]

Yes

Array of biographical statements

personality

object

Yes

Personality configuration

knowledge

string[]

No

Areas of expertise and knowledge

goals

string[]

No

Agent's objectives and motivations

actions

Action[]

No

Custom action definitions

clients

string[]

No

Enabled platform integrations

settings

object

No

Platform-specific settings

plugins

Plugin[]

No

Plugin configurations

modelProvider

string

No

AI model provider (default: "openai")

model

string

No

Specific model to use

modelSettings

object

No

Model-specific parameters

Detailed Properties

Name

The display name for your agent.

Example:

Bio

Array of statements that define the agent's background and identity. Written in first person.

Example:

Personality

Defines how the agent communicates and behaves.

Example:

Knowledge

Array of knowledge domains and areas of expertise.

Example:

Goals

The agent's objectives and motivations.

Example:

Actions

Custom actions the agent can perform.

Example:

Clients

Array of platform integrations to enable.

Supported Clients:

  • discord

  • twitter

  • telegram

  • slack

  • whatsapp

Example:

Settings

Platform-specific configuration.

Discord Settings

Example:

Twitter Settings

Example:

Plugins

Plugin configurations.

Example:

Model Settings

AI model parameters.

Example:

Complete Example

Validation

Validate your character file:

Type Definitions

Full TypeScript definitions available at:

Best Practices

  1. Be Specific: Clear, specific definitions lead to consistent behavior

  2. Test Iteratively: Refine based on actual interactions

  3. Version Control: Track changes to character files

  4. Use Comments: Document reasoning for configuration choices

  5. Stay Consistent: Maintain consistency across all properties

Last updated