Example requests
Ask your coding agent to build an agent, the tools it should use, and where people should interact with it.“Build a support agent that answers product questions from our docs, checks customer details, and drafts replies in our support tone.”
“Create an agent that watches for tagged Slack messages, investigates the topic, and replies with a sourced summary.”
“Build a data agent that can query our warehouse and answer questions from a #data Slack channel.”
How agents are defined
In Keystroke, agents live in your project code undersrc/agents/. Each file default-exports a defineAgent() definition, and the runtime discovers it when you run or deploy the project.
What agents can use
Agents are useful when a task needs judgment, language understanding, tool use, or multi-turn context.| Capability | How it works |
|---|---|
| Instructions | systemPrompt tells the model how to behave |
| Models | model is an exact catalog id (vendor/model-id); optional thinkingLevel. See Models. |
| File system | Each session gets a /workspace with a built-in file system and bash (code execution) tools |
| Web search | Built-in web_search and web_fetch tools when a web provider is configured |
| Browser use | Built-in tools for agents to use a personal browser to interact with the web |
| Tools | Attach custom tools, MCP tools, subagents, and workflows as tools |
| Skills and files | Attach project skills from src/skills/ and static files from src/files/ |
| Memory | Sessions and persistent memory are enabled by default unless disabled |
| Sandbox | A built-in sandbox environment for using CLIs and more advanced code execution |
| Self-scheduling | Built-in tools let an agent schedule its own future or recurring runs (ephemeral triggers) |
How to run agents
You can use an agent from the CLI, API, a workflow, another agent, or an external gateway like Slack. You can also run an agent automatically by attaching a trigger (a schedule, webhook, or poll), and agents can even schedule their own runs with ephemeral triggers.Running deployed agents
Deploy your project, then prompt the agent against the deployed project:keystroke dev and the same commands target it instead. The CLI chooses local or cloud based on the active target; see targets: local vs cloud.
Next steps
Build agents
Define agents with tools, models, skills, files, and runtime options.
Run agents
Prompt agents from the CLI and inspect sessions.
Triggers
Run agents on a schedule, webhook, or poll.
Agent runs
Review conversation history, tool calls, traces, and errors.