Build, edit, or debug backend AI agents with eve, a framework that represents agents as directories of files. Work on instructions, tools, connections, schedules, and related components using documentation bundled with the installed version.
Build durable backend AI agents with the eve framework. Use when creating, editing, or debugging an eve project — agent instructions, skills, tools, connections, channels, sandboxes, subagents, schedules, or evals.
Review the instructions the agent will receive before you install.
eve is a filesystem-first framework for durable backend AI agents. An agent is a directory on disk — instructions, skills, tools, connections, channels, subagents, and schedules are all files — and eve compiles and runs it.
The complete documentation ships inside the eve package. Do not rely on this
skill for guidance — always read the bundled docs, which match the installed
version exactly:
node_modules/eve/docs/
Start with node_modules/eve/docs/README.md. It contains the full
index and recommended reading order. Before writing any eve code, read the
relevant guide there first.
If eve is not installed yet, install it (npm install eve) or scaffold a new
agent with npx eve init <agent-name>, then read the bundled docs.
See references/source-of-truth.md for the repo-local handoff boundary.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Fix defects in Composio SDK through focused reproduction, root-cause analysis, regression tests that check for recurrence, and targeted verification. Use it for reported bugs, failing tests, CI regressions, runtime errors, or incorrect SDK behavior.
Design, implement, and review Composio CLI commands, including user interactions, output, errors, and configuration. It guides command wiring and service changes using Effect and effect/cli, with references for implementation patterns.
Create, update, and debug Docker-based end-to-end tests for the Composio CLI. Covers running the executable, keeping test data separate, checking command output, and maintaining package manifests within the CLI test suite.
Build beta versions of the Composio CLI, promote a tested beta to a stable release, and investigate failed releases. Guides verification of published binaries and installation tests through the Build CLI Binaries workflow.
Set up and use Composio to connect AI agents with apps such as Gmail, Slack, and Notion. Selects guidance for personal accounts or product integrations, covering setup, app operations, troubleshooting, and migration.
Keep TypeScript and Python SDKs consistent when shared behavior or backend APIs change. Aligns public API names, use of generated clients, and documentation examples, including updates to the fixed versions of generated clients.