PLOWSHARE
Conversations, specialist agents, files and knowledge belong to a durable project. Return through the interface that fits your day, with the server keeping the work and its history.
A project groups definitions, conversations, knowledge, permissions and optional files. Use one for a research collection, a codebase, an integration or an ongoing responsibility.
Every human account has a private Personal project. Start with questions, notes and plans, then develop an evolving knowledge collection. Its files and history remain separate from other accounts and ordinary shared projects.
Explore Personal →Registered server projects have explicit members and roles. Creating a project does not make everyone a member. Server workspaces can be managed by Plowshare or independently maintained with declared writable areas.
Projects and workspaces ↗Attach a local checkout through a fenced client file channel, or use a registered server workspace. A client path and a server path name different files. Git-backed synchronization is a separate choice; attaching a folder does not enable it.
A bot is an assistant you talk to. An agent is a specialist the system or another agent can invoke. Their definitions select prompts, models, tools, delegates and execution limits.
Markdown and YAML frontmatter describe behavior. Start from the shipped conversation, coding, review or research roles and adapt them to your project. Inspect the effective roster to see which definitions are served and why others are disabled.
A skill combines instructions with optional supporting resources. Invoke it under explicit grants and a chosen context mode. Hidden, granted skills can remain available to people through bound slash commands.
Account, project and workspace rules guide work through the existing resolution tiers. More specific definitions can override earlier ones. An invalid authoritative override is refused rather than replaced silently.
Skills do not automatically dispatch by description matching. Model discovery and caller grants are explicit configuration, and skill instructions cannot add tools the executor lacks.
Agents, bots and permissions ↗Clients reach the same server-owned work. Their presentation and capability coverage differ; select the surface that supports the operation you need.
| Interface | Useful for |
|---|---|
| Desktop | Conversations, project navigation, Library reading, reports, approvals and work inspection. |
| Terminal / TUI | Conversation beside your tools, slash commands, project attachment and live run inspection. |
| CLI | Explicit operations, scripting, offline payload validation and durable job status. |
| Web console | Browser access to the implemented conversation and management surfaces. |
| MCP | Expose Plowshare operations to another tool-using host while Plowshare owns submitted work. |
| SDKs | Build an application or protocol adapter using the public operation contracts. |
Membership, tool grants, file boundaries, command policy, hooks and approvals all apply to the work. A prompt or a human approval does not replace the other access checks.
Viewers read. Contributors can also start and update work. Managers additionally manage definitions and membership. Private conversations and information audiences keep their own ownership checks.
Declared roots, exclusions, scopes and writable areas constrain file tools. Commands have separate local and server policies. Projects with restricted writable areas refuse server commands that cannot honor those restrictions.
Approvals identify a particular pending operation. Answer the current request, then follow its actual outcome. Hooks and authorization can still refuse the action; a prior approval is not a general-purpose permission.
Scoped service tokens have expiry and fixed project-role ceilings. Effective access also depends on current grants. They have no password login or Personal space; a background adapter needs an explicit permitted project.
Long-running work returns a durable handle. Accepted means the server admitted it; completion, refusal, interruption and cancellation are separate outcomes.
Retain the job, conversation or workflow identity and any request receipt.
Read or follow the existing work rather than repeating a mutation after a lost reply. Work requiring a disconnected local file channel can fail even when the server remains available.
Inspect tool effects, terminal outcome and partial output. Cooperative cancellation stops future work and does not undo committed effects.
Authenticated WebSocket operations carry supported client/server work. Authentication, readiness, binary uploads, Git transfers and external protocols retain their documented HTTP boundaries. The runtime uses Java 21, Spring Boot, PostgreSQL and pgvector, with persistent disk state.
Architecture and concepts ↗