agent-bios
v0.19.2
Published
A thin, low-level instruction layer for LLM CLI agents: one set of principles and behavior whichever model you run. Stores private, editable instructions for explicitly activated sessions.
Maintainers
Readme
agent-bios
A personal instruction layer for Claude Code and Codex.
Build an instruction library you can inspect, edit, and reuse. Choose what each CLI session or Codex app task uses, while preserving your existing global instruction files.
Purpose
agent-bios exists to let workers compose, share, and inherit team work environments from Instructions, Domain knowledge, and Decision memory, so they can perform their roles within the standards and context of their team, industry, and organization.
A team is the basic unit for selecting, adopting, and sharing a work environment.
Workers should be able to select an environment appropriate to their role and team, collaborate from shared standards and decision context, and continue the work when a worker, model, session, or device changes. Shared context does not require identical outputs or erase personal, team, and organizational boundaries.
The current service provides the Instructions library and host launch/delivery integration. Shared environment editions, Domain knowledge, and Decision memory are the design direction; this purpose statement does not claim they are shipped.
Quick start · Instructions Studio · How it works · Understand! · Documentation · 한국어
Actual 0.18.0 UI, captured with Textual enabled and the bundled instructions in an isolated test environment. This earlier capture retains its Corpus Studio title; the current UI is named Instructions Studio.
Make your instructions your own
agent-bios ships Instructions: rules, guides, and procedures for how you work.
You decide which parts belong in your working environment. The CLI command is
instructions, and the library UI is named Instructions Studio.
These names apply to this source revision. If your installed version does not
recognize agent-bios instructions, use agent-bios corpus; this revision also
accepts that older command name. See compatibility.
| What you want to do | What agent-bios provides | | --- | --- | | See what your instructions say | Browse and search documents in Instructions Studio; follow a rule's links to its guides. | | Adapt them to your work | Edit supplied items, create personal ones, and choose their delivery method. | | Choose what a session uses | Switch individual items on or off without deleting their content or edits. | | Recover the starting point | Restore supplied content, recover personal items, or preview a full reset. |
This is an instruction and launch layer, not a replacement for either host CLI. It does not train the model or guarantee that the model follows every instruction.
Quick start
Use the terminal installer or set up through a Codex app conversation. Both offer language, dependency, instructions and optional app/import choices. See setup and prerequisites.
In a terminal
You need macOS or Linux, Bash, Python 3.11+, and Node.js 18+ with npm for package installation. Run:
npm install -g [email protected]
agent-bios installThe installer opens a guided terminal UI with English, Korean and Japanese. Its verified Textual bundle is included; a separate UI installation is unnecessary. Choose only the dependencies and instructions you want. Full setup options →
To launch a CLI session, install and authenticate that host CLI, then run this from your project:
"$HOME/.local/bin/agent-launch" claudeUse codex instead of claude for a Codex CLI session.
- Choose a Builder preset or Custom.
- Review the model, review setup, and permissions. Some presets request permission bypass; select settings appropriate for your project.
- Start the session. Choose Software Engineer / Vanilla to use the host's native setup without an agent-bios instructions snapshot.
Open Instructions Studio from the launcher or run agent-bios instructions to inspect the
library. agent-bios status shows the installed private release and its location.
Use this repository's Code menu to copy its clone command or download its source. From the obtained repository folder, run:
bash install.sh installThis route needs Bash and Python 3.11+; Node/npm are not acquisition prerequisites.
Keep using bash install.sh <command> from that source for management. A global
agent-bios command can belong to a different npm version.
Ordinary claude and codex commands do not automatically receive agent-bios
content. An optional zsh shell connection
can route bare interactive commands through the launcher. If you have an older
global installation, read migration
before changing it.
In the Codex app
Open a local task on the machine you want to configure and send:
Install https://github.com/kangminlee-maker/agent-biosThe agent follows INSTALL.md, obtains a fixed source revision, and asks for English, 한국어 or 日本語. Choose dependencies, no active instructions or specific instructions, and optional app connection or instruction-file capture. Review the effects before Apply. You do not need to supply a local path or install Codex CLI.
Once the registered command appears in the app, use $agent-bios for setup or management.
To add instructions to a task, explicitly ask it to use your chosen instructions there.
Installation and opening Instructions Studio do not activate task context.
App use, off, and personal instruction import →
Your instruction library
Open Instructions Studio in the launcher, or run agent-bios instructions.
In the app, $agent-bios can manage the same library through conversation.
- Read as you navigate. Arrow keys move between reading controls and update the document as the library cursor moves; Enter is not required to read an item.
- Recognize guide pointers. Rules with explicit guide references show → GUIDE and link to the guide, its delivery method, and its current state.
- Switch items on or off. Press Space in the library.
[x]is on,[ ]is off, and*means the choice is not yet applied. - Apply deliberately. Stage several choices, then use Preview on/off → Apply. Ordinary edits also use a revision-checked preview.
An item's use and its delivery method are separate. A selected rule may
be always, a guide relevant, or a procedure requested. Native hooks and
agents use separate opt-in adapters. Putting a guide next to its trigger does
not change either one's delivery.
Individual on/off choices take precedence over default domain/core selections. Off is not deletion: content and edits remain available, including for learning. Updates retain those choices; a full reset returns to installed defaults.
Instructions controls, keyboard navigation, delivery methods, and included guides →
How sessions work
Library → your selection and edits → fixed snapshot → configured session
Installation stores a release and its baseline in agent-bios-owned locations. A configured launch compiles the selected content for its host. Later edits affect future snapshots; managed CLI resume resolves the session's recorded snapshot. App tasks use a separately selected snapshot returned through their tool/context path. Turning app delivery off cannot erase text already present in the conversation.
Your own global instructions are also loaded by default in activated sessions. Not overwriting them is different from excluding them. Supported Claude versions offer selective global-document exclusion; the current Codex adapter does not. Project instructions and prior conversation content are separate.
Storage, session pins, and verification limits →
Understand the reasoning
Choose Understand! in the launcher to explore why the instructions are written the way they are. Select a coherent learning bundle rather than memorizing separate files.
The tutor chooses a small set of core learning points and tracks questions by their source bullet. No bullet receives more than ten questions, including follow-ups. It explains purposes, background, tradeoffs and limits, then summarizes and finishes when the core points are covered. An explanation or closing summary needs no further question. The tutor distinguishes documented reasons from inference and respects pause or stop requests.
For example, a discussion of clarification might ask: “What would change in your next action if this ambiguity were resolved?”
The aim is understanding when a rule helps—and where it stops helping. This is learning for the person, not model training. Saving a personal discovery requires your confirmation.
Learning sessions and personal discoveries →
Stay in control
- No default global rewrite. Private installation leaves native instruction files, discovery directories, and hook settings alone. Explicit legacy migration is a separate operation.
- Separate selection from permission. Turning an item on does not bypass native hook/agent opt-in, host trust, or execution permissions.
- Know what is verified.
agent-bios verifychecks stored content and owned projections.activation: unverifiedis deliberate; it does not certify model consumption. Authenticated resume and some native integrations remain incompletely verified. - Inspect recovery before applying it. Migration and reset have previews. Conflicting user-owned paths are reported, not permission to delete them.
Documentation
| When you need more detail | Read | | --- | --- | | Install, connect the app, or import existing instructions | Setup | | Author, enable, restore, or inspect instructions items | Instructions | | Understand snapshots, storage, and session evidence | Session model | | Migrate, reset, or resolve installation conflicts | Recovery | | Configure presets, globals, shell connection, native hooks, or review | Advanced launch | | Learn the instructions and preserve a discovery | Understand! | | Check prerequisites and optional tools | Dependencies | | Develop this repository | Contributing — requires a checkout |
Use agent-bios help and agent-bios instructions --help for command discovery.
Source references: delivery surfaces, network contract,
and terminology.
Adopting elsewhere
Review the (private) bindings and environment-specific dependencies before
adopting the defaults. Keep personal adjustments in Instructions Studio, or follow
the source-authoring workflow when changing
what the package ships.
Scope
The package contains instruction sources and runtime machinery, not your personal instructions state, learning events, session pins, credentials, or native settings.
License
MIT.
