# Internal Ops Agent
Use the local Markdown instructions
as the source of truth.In development. Not on npm yet.
Write your agent as a folder of Markdown and TypeScript. Plico will run it, with the whole harness around it already built.
# Support agentHelp the team triage support requests.Follow the triage skill.Create a ticket when action is needed.# Triage a request1. Read the issue.2. Identify what needs to happen.3. Create a clear, actionable ticket.export default { name: "create_ticket", description: "Create a support ticket.", capabilities: ["ticket:write"], approval: { required: false }, handler: async (input) => createTicket(input),};Your files become its behaviour.
The team can’t connect to the VPN. Can you open a ticket?
"Team VPN connection issue"Created ticket TCK-104 for the VPN issue, with the details your team needs.
Waiting for your files—Plain Markdown gives your agent a job. Your instructions stay readable, reviewable and yours.
A model on its own can only answer. To do real work it needs a harness: a loop, tools, approvals, logs, memory and tests. Most teams build all of that by hand. Plico will do that work for you.
Readable, reviewable and kept in Git like the rest of your code. These come from the example project in the repository.
# Internal Ops Agent
Use the local Markdown instructions
as the source of truth.# Triage
Review incoming work items, identify
the smallest safe next step, and
record the outcome.export default {
name: "create_ticket",
description: "Create a support ticket.",
capabilities: ["ticket:write"],
approval: { required: false },
};The plan is that nothing about the folder changes as the agent grows.
Plico is early. Here is what is real and what is not yet.